Remote MCP · Endpoint

CanaryGuard 402 MCP server

No. CanaryGuard 402 answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://canaryguard-402.onrender.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.ak10082247-max/canaryguard-402
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
135 ms
Tools exposed
26 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Deterministic prompt-injection detection & sanitization for AI agents via x402 on Base.
Website
https://canaryguard-402.onrender.com/
Repository
https://github.com/ak10082247-max/canaryguard-402
Listing
From the official MCP registry (active).
Recent checks of CanaryGuard 402
CheckedResultHandshake
1 hour agoHandshake completed135 ms
9 days agoHandshake completed148 ms
9 days agoHandshake completed137 ms
11 days agoHandshake completed166 ms
12 days agoHandshake completed284 ms
13 days agoHandshake completed154 ms
14 days agoHandshake completed135 ms
14 days agoHandshake completed271 ms
16 days agoHandshake completed164 ms
19 days agoHandshake completed289 ms
21 days agoFailed - the server returned an HTTP error—
24 days agoHandshake completed268 ms
26 days agoHandshake completed148 ms
28 days agoHandshake completed325 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with CanaryGuard 402 and makes no claim about it beyond what these checks measured.