Remote MCP · Endpoint

ActionGuard Protocol Inspector Agent MCP server

No. ActionGuard Protocol Inspector Agent answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://actionguard.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.lsendel/actionguard
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
560 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Diff and poisoning detection for MCP servers: catch schema drift and prompt poisoning.
Listing
From the official MCP registry (active).
Recent checks of ActionGuard Protocol Inspector Agent
CheckedResultHandshake
42 minutes agoHandshake completed560 ms
3 days agoHandshake completed121 ms
12 days agoHandshake completed116 ms
12 days agoHandshake completed65 ms
14 days agoHandshake completed68 ms
15 days agoHandshake completed98 ms
16 days agoHandshake completed69 ms
17 days agoHandshake completed74 ms
18 days agoHandshake completed113 ms
19 days agoHandshake completed265 ms
22 days agoHandshake completed198 ms
25 days agoHandshake completed60 ms
27 days agoHandshake completed476 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

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 ActionGuard Protocol Inspector Agent and makes no claim about it beyond what these checks measured.