Remote MCP · Endpoint
IntentFence Agent Action Firewall MCP server
No. IntentFence Agent Action Firewall answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://agentpass-protocol.rmalka06.chatgpt.site/api/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.razel369/intentfence
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 1.37 s
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Fail-closed action authorization, MCP risk scanning, x402 checks, and signed receipts.
- Repository
- https://github.com/razel369/intentfence
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 1.37 s |
| 1 day ago | Handshake completed | 1.24 s |
| 2 days ago | Handshake completed | 818 ms |
| 3 days ago | Handshake completed | 797 ms |
| 4 days ago | Handshake completed | 230 ms |
| 5 days ago | Handshake completed | 203 ms |
| 6 days ago | Handshake completed | 375 ms |
| 9 days ago | Handshake completed | 205 ms |
| 11 days ago | Handshake completed | 213 ms |
| 14 days ago | Handshake completed | 629 ms |
| 16 days ago | Handshake completed | 367 ms |
| 18 days ago | Handshake completed | 888 ms |
| 20 days ago | Handshake completed | 1.08 s |
| 22 days ago | Handshake completed | 243 ms |
| 24 days ago | Handshake completed | 512 ms |
| 26 days ago | Handshake completed | 334 ms |
| 28 days ago | Handshake completed | 1.33 s |
| 29 days ago | Handshake completed | 909 ms |
The last 18 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 IntentFence Agent Action Firewall and makes no claim about it beyond what these checks measured.