Intentrax proof verification

Keyless, read-only checks of Intentrax AI-agent execution proofs. Never executes, signs, or writes.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~821Tokens (tool definitions)
~1.5 KBTypical response size
Moderate attention impact (0.64% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.intentrax.com/public"
    }
  }
}

Remote endpoints

https://mcp.intentrax.com/publicstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢intentrax_verify_public_proof(proof_id)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "proof_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 128,
      "pattern": "^[A-Za-z0-9_.-]+$",
      "description": "Published Intentrax proof identifier (usually a 64-character hex string)."
    }
  },
  "required": [
    "proof_id"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {
    "proof_id": {
      "type": "string"
    },
    "verification_status": {
      "type": "string"
    },
    "verdict": {
      "type": [
        "string",
        "null"
      ]
    },
    "verify_url": {
      "type": "string"
    },
    "verification_assessment": {
      "type": [
        "object",
        "null"
      ]
    },
    "limitations": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "public_verification": {
      "type": "object"
    }
  },
  "required": [
    "proof_id",
    "verification_status",
    "verify_url",
    "limitations"
  ]
}
🟢intentrax_get_trusted_key_set(environment)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "environment": {
      "type": "string",
      "enum": [
        "production",
        "sandbox"
      ],
      "description": "Which published key set to return."
    }
  },
  "required": [
    "environment"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {
    "environment": {
      "type": "string"
    },
    "key_set_sha256": {
      "type": "string"
    },
    "source": {
      "type": "string"
    },
    "key_set": {
      "type": "object"
    },
    "how_to_verify_offline": {
      "type": "string"
    }
  },
  "required": [
    "environment",
    "key_set_sha256",
    "key_set",
    "source"
  ]
}
🟢intentrax_verify_proof_export(proof_export)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "proof_export": {
      "type": "object",
      "description": "The exported proof lookup package, as a JSON object (up to 1 MiB)."
    }
  },
  "required": [
    "proof_export"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string"
    },
    "reason": {
      "type": "string"
    },
    "verified_by": {
      "type": "string"
    },
    "report": {
      "type": "object"
    },
    "limitations": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  },
  "required": [
    "status",
    "verified_by",
    "limitations"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools