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.
Listing
From the official MCP registry (active).
Recent checks of IntentFence Agent Action Firewall
CheckedResultHandshake
1 hour agoHandshake completed1.37 s
1 day agoHandshake completed1.24 s
2 days agoHandshake completed818 ms
3 days agoHandshake completed797 ms
4 days agoHandshake completed230 ms
5 days agoHandshake completed203 ms
6 days agoHandshake completed375 ms
9 days agoHandshake completed205 ms
11 days agoHandshake completed213 ms
14 days agoHandshake completed629 ms
16 days agoHandshake completed367 ms
18 days agoHandshake completed888 ms
20 days agoHandshake completed1.08 s
22 days agoHandshake completed243 ms
24 days agoHandshake completed512 ms
26 days agoHandshake completed334 ms
28 days agoHandshake completed1.33 s
29 days agoHandshake completed909 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.