Remote MCP · Endpoint

MCP Verification Gate: check an MCP server or an A2A agent before you connect or delegate MCP server

No. MCP Verification Gate: check an MCP server or an A2A agent before you connect or delegate answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gate.horizonshield.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.ogasurfproject-jpg/hs-verify-gate
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
62 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Check an A2A agent before you delegate, or an MCP server's measured conduct. Free, no key.
Listing
From the official MCP registry (active).
Recent checks of MCP Verification Gate: check an MCP server or an A2A agent before you connect or delegate
CheckedResultHandshake
2 hours agoHandshake completed62 ms
1 day agoHandshake completed50 ms
2 days agoHandshake completed82 ms
3 days agoHandshake completed64 ms
4 days agoHandshake completed61 ms
5 days agoHandshake completed104 ms
7 days agoHandshake completed139 ms
9 days agoHandshake completed46 ms
12 days agoHandshake completed112 ms
14 days agoHandshake completed82 ms
16 days agoHandshake completed70 ms
18 days agoHandshake completed54 ms
20 days agoHandshake completed51 ms
22 days agoHandshake completed62 ms
25 days agoHandshake completed44 ms
26 days agoHandshake completed57 ms
27 days agoHandshake completed67 ms
29 days agoHandshake completed299 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 MCP Verification Gate: check an MCP server or an A2A agent before you connect or delegate and makes no claim about it beyond what these checks measured.