HANRIA agent mandate check
REMOTE · CHECK.HANRIA.AI
Check an agent action against its operator's mandate before acting: permit, deny or escalate.
Available components
Last scanned (17 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability94
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 501 tokens (~71/item across 7 items; 2 tools + 5 resources), lean.Pass
- Tools include usage examples.Pass
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
- Server version: 0.7.1 → 0.7.4 functional
- 10 Oct 26 +3
- Server version: 0.6.1 → 0.7.1 functional
- 3 Oct 26 +1
- Server version: 0.5.0 → 0.6.0 functional
- 2 Oct 26 +1
- Tool “check_action” rewrote its description, which is the text the model reads security
- Tool “validate_mandate” rewrote its description, which is the text the model reads security
- Schema quality: 226 → 412 ▼ functional
- Schema quality: 226 → 191 ▲ functional
- Schema quality: fail → pass ▲ functional
- Tool “check_action” now declares an output schema ▲ functional
- Tool “validate_mandate” now declares an output schema ▲ functional
- The server now declares the “prompts” capability functional
- The server now declares the “resources” capability functional
- First check of Schema quality: 100 functional
- First check of Tool coverage: 100 functional
- Schema quality: excellent → good functional
- New prompt “write_mandate” functional
- New resource “deploy-gate” functional
- New resource “file-sandbox” functional
- New resource “outbound-email” functional
- New resource “payments-ceiling” functional
- New resource “read-only-research” functional
- Server version: 0.4.1 → 0.5.0 functional
- Server version: 0.4.0 → 0.4.1 functional
- Server version: 0.3.0 → 0.4.0 functional
- New tool “validate_mandate” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Probed https://check.hanria.ai/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hanria.ai | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 77d24efb55d0d9970eedaec4f64c32f5 |
| SANs: hanria.ai, check.hanria.ai, *.check.hanria.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of check.hanria.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| hanria.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://check.hanria.ai/v1/mcp | Verified | 200 | |
| http (plaintext) | http://check.hanria.ai/v1/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_action Check an agent action against a mandate ~236
Call this before your agent does something consequential (sends, pays, deletes, publishes, installs or changes access). Pass mandate (the operator's rules; the first matching clause decides) and action (kind, verb, target, optional counterparty and amount). Returns permit, deny or escalate with the governing clause, a reason, an action digest and a signed receipt; treat error as deny. Advisory: it cannot stop an action, and it keeps no request content. To check a new mandate first, call validate_mandate. Examples: inputSchema. Docs: https://hanria.ai/llms.txt
| Name | Type | Req | Description |
|---|---|---|---|
| action | object | yes | A typed description of a proposed operation, submitted by an agent to a local HANRIA runtime. MUST NOT contain credentials, secrets, private keys, or tokens. |
| mandate | object | yes | An operator-authored statement of what an agent may do. Written by a person, read by an agent, evaluated locally. A mandate is advisory: it describes intended authority and supports a local check, bu… |
| Name | Type | Req | Description |
|---|---|---|---|
| action_digest | string | – | SHA-256 of hanria-action-v1 followed by the action's canonical JSON. |
| clause | string | – | The clause that decided, when one did. |
| clause_note | string | – | – |
| mandate_ref | string | – | – |
| outcome | string | yes | Treat error as deny. |
| reason | string | yes | – |
| receipt | object | – | Ed25519-signed receipt binding the outcome to this action and mandate for 15 minutes. Keys and the signed-bytes rule: https://check.hanria.ai/.well-known/hanria-receipt-keys.json |
| schema_version | string | yes | – |
{"action":{"justification":"Read the permitted file.","operation":{"kind":"file","target":"/tmp/example","verb":"read"},"requested_by":{"agent":"example-agent"},"schema_version":"0.1-draft"},"mandate":{"clauses":[{"effect":"permit","id":"permit-file","match":{"kind":["file"]}}],"default":"deny","mandate_id":"minimal-permit","purpose":"Permit one file action.","schema_version":"0.2-draft"}}{"action":{"justification":"Pay the invoiced supplier.","operation":{"amount":{"currency":"USDC","value":"25"},"counterparty":"0x2222222222222222222222222222222222222222","kind":"transaction","target":"eip155:11155111/0x1111111111111111111111111111111111111111/transfer","verb":"transfer"},"requested_by":{"agent":"example-agent"},"schema_version":"0.1-draft"},"mandate":{"clauses":[{"effect":"permit","id":"small-transfers","match":{"counterparty":["0x2222222222222222222222222222222222222222"],"kind":["transaction"],"max_amount":{"currency":"USDC","value":"100"},"target_prefix":["eip155:11155111/0x1111111111111111111111111111111111111111/"],"verb":["transfer"]}}],"default":"escalate","mandate_id":"example-payments","purpose":"Permit small transfers to one named recipient on a test network.","schema_version":"0.2-draft"}}validate_mandate Check a mandate for errors ~176
Call this after writing or editing a mandate, before relying on it. Returns valid true or false with the reason: schema errors, clauses that can never run because an earlier clause already decides them, unbounded prefixes, credential material, and expiry. An invalid mandate makes every check_action call answer error. Once per mandate version is enough; there is no need to call it before every check_action. Free, and it keeps no request content. Docs: https://hanria.ai/llms.txt
| Name | Type | Req | Description |
|---|---|---|---|
| mandate | object | yes | An operator-authored statement of what an agent may do. Written by a person, read by an agent, evaluated locally. A mandate is advisory: it describes intended authority and supports a local check, bu… |
| Name | Type | Req | Description |
|---|---|---|---|
| clauses | integer | – | – |
| expired | boolean | – | True when not_valid_after has passed; check_action then denies everything. |
| mandate_digest | string | – | SHA-256 of the mandate's canonical JSON; receipts carry the same value. |
| mandate_ref | string | – | – |
| reason | string | yes | – |
| schema_version | string | yes | – |
| valid | boolean | yes | – |
{"mandate":{"clauses":[{"effect":"permit","id":"permit-file","match":{"kind":["file"]}}],"default":"deny","mandate_id":"minimal-permit","purpose":"Permit one file action.","schema_version":"0.2-draft"}}How do I install the HANRIA agent mandate check MCP server?
HANRIA agent mandate check is a hosted endpoint at https://check.hanria.ai/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · check.hanria.ai
claude mcp add --transport http ai-hanria-agent-mandate-check 'https://check.hanria.ai/v1/mcp'
What is the HANRIA agent mandate check MCP server?
HANRIA agent mandate check is an MCP server listed in the public MCP registry as ai.hanria/agent-mandate-check. Check an agent action against its operator's mandate before acting: permit, deny or escalate. This page covers its hosted endpoint (https://check.hanria.ai/v1/mcp).
Is the HANRIA agent mandate check MCP server safe to use?
HANRIA agent mandate check scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HANRIA agent mandate check MCP server expose?
HANRIA agent mandate check exposes 2 tools: check_action, validate_mandate. Their descriptions and schemas cost roughly 412 tokens of context every time the server is loaded.
Does the HANRIA agent mandate check MCP server require authentication?
No. We connected to HANRIA agent mandate check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HANRIA agent mandate check MCP server still maintained?
HANRIA agent mandate check is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.