MCP App Store
by KeenEthics
Intentrax icon

Intentrax MCP Server for Claude

By Intentrax, Inc.

Overview

Intentrax issues signed proofs for consequential actions taken by AI agents, such as payments, infrastructure changes and regulated decisions. Anyone can check these proofs, without trusting the operator's logs. This connector brings that check into Claude. It has three read-only tools: - Verify a published proof. Look up a proof by its ID on Intentrax's public verifier, and get its status, verdict, and a per-dimension assessment of what was and was not verified. - Get the signing keys. Fetch Intentrax's published production or sandbox key set with its SHA-256, for checking proofs offline. - Verify a proof export. Paste an exported proof, and the connector runs the same verifier as npx @intentrax/sdk verify-proof, against the pinned production keys. Every answer states its limits. A proof records an Intentrax decision about one action. It does not by itself show that an external effect happened, or that every agent action was routed through Intentrax. The connector needs no account and no key. It never executes, admits, signs, or writes anything. It keeps nothing you send it: a pasted export is checked in a temporary folder that is deleted afterwards.

How to connect

  1. Claude: Open the Intentrax listing in the Claude connectors directory and choose Connect. Claude listing Intentrax exposes 3 tools here.

Tools

intentrax_get_trusted_key_set

Claude
Return the published Ed25519 signer key set Intentrax proofs are checked against (production: trust-bearing, min_trusted_signers applies; sandbox: never trust-bearing), with its SHA-256, so the user can verify a proof offline with npx @intentrax/sdk verify-proof --trusted-keys. Read-only; no network call.

intentrax_verify_proof_export

Claude
Verify an exported proof package (the JSON from GET /v1/proofs/{id}/export or the console's Export button) against Intentrax's published production and sandbox keys, using the same verifier as npx @intentrax/sdk verify-proof --json. Pure computation: no network call, nothing is stored. status PASS means every signer is a published trust-bearing key and the signer threshold is met; SANDBOX_NON_TRUST_BEARING means the mechanics check out with sandbox keys only; FAILED_CLOSED means integrity or a signature did not verify. PASS does not show that an external effect happened; the result's verification_assessment and limitations list what was and was not assessed.

intentrax_verify_public_proof

Claude
Look up a published proof by its ID on Intentrax's public verifier (verify.intentrax.com) and return the verifier's status and per-dimension assessment. Read-only. The hosted assessment covers the record integrity and signer checks done by Intentrax's service; it is not a check against keys pinned on the caller's side. A proof records an Intentrax decision; it does not show that an external effect happened.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/intentrax"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/intentrax)