Remote MCP · Endpoint

ai.hanria/check MCP server

No. ai.hanria/check answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://check.hanria.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.hanria/check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
230 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Check a proposed agent action against operator's rules: permit, deny or escalate, with the clause.
Listing
From the official MCP registry (deprecated).
Recent checks of ai.hanria/check
CheckedResultHandshake
1 hour agoHandshake completed230 ms
2 days agoHandshake completed800 ms
4 days agoHandshake completed390 ms
6 days agoHandshake completed210 ms
8 days agoHandshake completed198 ms
10 days agoHandshake completed158 ms
12 days agoHandshake completed208 ms
14 days agoHandshake completed158 ms
15 days agoHandshake completed294 ms
16 days agoHandshake completed513 ms
18 days agoHandshake completed391 ms
20 days agoHandshake completed149 ms
22 days agoHandshake completed140 ms
24 days agoHandshake completed203 ms
25 days agoHandshake completed1.09 s

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

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 ai.hanria/check and makes no claim about it beyond what these checks measured.