Check

ai.hanriaPublished by hanria.aiOfficial publisherv0.2.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that checks a proposed agent action against the operator's mandate and returns permit, deny or escalate with the deciding clause.

What you can do
Check a consequential action (send, pay, delete, publish, install, change access) against the operator's rules and get permit, deny or escalate with the clause that decided it, passing the mandate, action kind, verb, target, and optional counterparty and amount. Validate a written or edited mandate before relying on it, returning valid or invalid with reasons such as schema errors, unreachable clauses, unbounded prefixes, credential material and expiry.
When to use it
Use it when an agent can take consequential actions and you want a policy gate before sending, paying, deleting, publishing, installing or changing access. Also useful to sanity-check a mandate after writing or editing it, since an invalid mandate makes every action check fail.
Requirements
A remote MCP endpoint at check.hanria.ai over streamable HTTP; no packages, environment variables or headers are declared. The operator's mandate text must be supplied with each check.
Before you install
The mandate is the operator's rule set and is sent to the remote service with each check; avoid embedding credential material, which the validator flags. A deny or escalate result is advisory to the agent, so enforcement depends on the agent actually calling the check first.

Installation

In SourceWeft

  1. Open Check in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.hanria%2Fcheck/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

2

check_action

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

Parametersactionrequiredmandaterequired

validate_mandate

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

Parametersmandaterequired

Version history

2
  1. v0.2.0LatestSep 29, 2026
  2. v0.1.0Sep 29, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Hanria integrations