# ai.hanria/check (remote · check.hanria.ai)

Check a proposed agent action against operator's rules: permit, deny or escalate, with the clause.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: deprecated
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

> **Deprecated**: this server is marked deprecated in the MCP registry. The registry records this reason: "Renamed to ai.hanria/agent-mandate-check."

## Components

- remote · `check.hanria.ai`: 82/100 (this document), [markdown](https://verifymcp.io/servers/ai-hanria-check/check.md), [page](https://verifymcp.io/servers/ai-hanria-check/check)

## Channel facts

- Endpoint: `https://check.hanria.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 94/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 501 tokens (~71/item across 7 items; 2 tools + 5 resources), lean.
  - Tools include usage examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the ai.hanria/check MCP server?

ai.hanria/check is a hosted endpoint at https://check.hanria.ai/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.

### Claude

```bash
claude mcp add --transport http ai-hanria-check 'https://check.hanria.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-hanria-check": {
      "url": "https://check.hanria.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-hanria-check": {
      "type": "http",
      "url": "https://check.hanria.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-hanria-check]
url = "https://check.hanria.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-hanria-check": {
      "type": "remote",
      "url": "https://check.hanria.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-hanria-check --url 'https://check.hanria.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-hanria-check:
    url: "https://check.hanria.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-hanria-check": {
      "Transport": "http",
      "Url": "https://check.hanria.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-hanria-check -t streamable-http -u 'https://check.hanria.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-hanria-check": {
      "type": "http",
      "url": "https://check.hanria.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-18 (score 80, +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.

### 2026-10-16 (score 79, +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.

### 2026-10-14 (score 78, +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.

### 2026-10-12 (score 77, +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.

### 2026-10-11 (score 76, 0)

- [functional] Server version: 0.7.1 → 0.7.4

### 2026-10-10 (score 76, +2)

- [functional] Server version: 0.6.1 → 0.7.1

## MCP tools (2)

### `check_action` (~236 tokens)

Check an agent action against a mandate

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

Input parameters:

- `action` (object, required): 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, required): 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…

Output parameters:

- `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): Treat error as deny.
- `reason` (string)
- `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)

### `validate_mandate` (~176 tokens)

Check a mandate for errors

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

Input parameters:

- `mandate` (object, required): 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…

Output parameters:

- `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)
- `schema_version` (string)
- `valid` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-hanria-check/check#diagnostics

## Score history

- 2026-10-23: 82
- 2026-10-22: 81
- 2026-10-21: 81
- 2026-10-20: 80
- 2026-10-19: 80
- 2026-10-18: 80
- 2026-10-17: 79
- 2026-10-16: 79
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 77
- 2026-10-12: 77
- 2026-10-11: 76
- 2026-10-10: 76
- 2026-10-07: 74
- 2026-10-06: 74
- 2026-10-05: 73
- 2026-10-04: 73
- 2026-10-03: 73
- 2026-10-02: 71
- 2026-10-01: 71
- 2026-09-30: 70
- 2026-09-29: 68
- 2026-09-28: 54

## Common questions

### What is the ai.hanria/check MCP server?

ai.hanria/check is an MCP server listed in the public MCP registry as ai.hanria/check. Check a proposed agent action against operator's rules: permit, deny or escalate, with the clause. This page covers its hosted endpoint (https://check.hanria.ai/mcp).

### Is the ai.hanria/check MCP server safe to use?

ai.hanria/check scores 82 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 ai.hanria/check MCP server expose?

ai.hanria/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 ai.hanria/check MCP server require authentication?

No. We connected to ai.hanria/check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ai.hanria/check MCP server still maintained?

ai.hanria/check is marked deprecated in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://check.hanria.ai/mcp
- Website: https://hanria.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-hanria-check/check.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-hanria-check/check.json
- HTML version of this page: https://verifymcp.io/servers/ai-hanria-check/check