Remote MCP · Endpoint
Agent Reserve Protocol Authorization Firewall MCP server
No. Agent Reserve Protocol Authorization Firewall answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://agent-reserve-protocol.super-myna-7255.chatgpt.site/api/mcp
The last check completed an MCP handshake.
- Registry name
- site.chatgpt.super-myna-7255.agent-reserve-protocol/agent-transaction-firewall
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-11-25
- Handshake latency
- 829 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Advisory policy preflight for AI-agent spend requests; never executes payments or accesses wallets.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 829 ms |
| 1 day ago | Handshake completed | 1.16 s |
| 2 days ago | Handshake completed | 839 ms |
| 3 days ago | Handshake completed | 295 ms |
| 4 days ago | Handshake completed | 186 ms |
| 5 days ago | Handshake completed | 846 ms |
| 6 days ago | Handshake completed | 1.03 s |
| 8 days ago | Handshake completed | 909 ms |
| 11 days ago | Handshake completed | 322 ms |
| 13 days ago | Handshake completed | 159 ms |
| 15 days ago | Handshake completed | 1.41 s |
| 18 days ago | Handshake completed | 803 ms |
| 20 days ago | Handshake completed | 795 ms |
| 22 days ago | Handshake completed | 171 ms |
| 24 days ago | Handshake completed | 1.16 s |
| 26 days ago | Handshake completed | 1.20 s |
| 27 days ago | Handshake completed | 640 ms |
| 29 days ago | Handshake completed | 288 ms |
| 29 days ago | Handshake completed | 1.32 s |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with Agent Reserve Protocol Authorization Firewall and makes no claim about it beyond what these checks measured.