
Keyless, read-only checks of Intentrax AI-agent execution proofs. Never executes, signs, or writes.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
Which published key set to return.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http mcp https://mcp.intentrax.com/public
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.
| Argument | Type | Description |
|---|---|---|
| environment* | string | Which published key set to return. |
{
"type": "object",
"required": [
"environment"
],
"properties": {
"environment": {
"enum": [
"production",
"sandbox"
],
"type": "string",
"description": "Which published key set to return."
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| proof_export* | object | The exported proof lookup package, as a JSON object (up to 1 MiB). |
{
"type": "object",
"required": [
"proof_export"
],
"properties": {
"proof_export": {
"type": "object",
"description": "The exported proof lookup package, as a JSON object (up to 1 MiB)."
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| proof_id* | string | Published Intentrax proof identifier (usually a 64-character hex string). |
{
"type": "object",
"required": [
"proof_id"
],
"properties": {
"proof_id": {
"type": "string",
"pattern": "^[A-Za-z0-9_.-]+$",
"maxLength": 128,
"minLength": 1,
"description": "Published Intentrax proof identifier (usually a 64-character hex string)."
}
},
"additionalProperties": false
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 19, 2026.