Remote MCP · Endpoint

HANRIA agent mandate check MCP server

No. HANRIA agent mandate check answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://check.hanria.ai/v1/mcp

The last check completed an MCP handshake.

Registry name
ai.hanria/agent-mandate-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
250 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check an agent action against its operator's mandate before acting: permit, deny or escalate.
Listing
From the official MCP registry (active).
Recent checks of HANRIA agent mandate check
CheckedResultHandshake
1 hour agoHandshake completed250 ms
2 days agoHandshake completed499 ms
4 days agoHandshake completed141 ms
6 days agoHandshake completed432 ms
8 days agoHandshake completed320 ms
10 days agoHandshake completed126 ms
13 days agoHandshake completed162 ms
14 days agoHandshake completed212 ms
16 days agoHandshake completed378 ms
17 days agoHandshake completed498 ms
18 days agoHandshake completed129 ms
21 days agoHandshake completed239 ms
22 days agoHandshake completed229 ms
24 days agoHandshake completed310 ms

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

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 HANRIA agent mandate check and makes no claim about it beyond what these checks measured.