Intentrax proof verification MCP server
com.intentrax/mcpintentrax.comstreamable-httpv0.1.0Scanned
Keyless, read-only checks of Intentrax AI-agent execution proofs. Never executes, signs, or writes.
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Intentrax proof verification MCP server can do
The Intentrax proof verification MCP server is published by intentrax.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: intentrax_verify_public_proof and intentrax_verify_proof_export), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 2Claude Code: ask
intentrax_verify_proof_exportVerify 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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Verify an exported Intentrax proof against pinned keys
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
intentrax_verify_public_proofLook 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Verify a published Intentrax proof
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
intentrax_get_trusted_key_setReturn the published Ed25519 signer key set Intentrax proofs are checked against (production: trust-bearing, min_trusted_signers applies; sandbox: never trust-bearing), with its SH…No findings
Why it is in this group
- The name "intentrax_get_trusted_key_set" says "get": a word for reading.
Description, as the server wrote 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.
Annotations the server declares
- title: Get Intentrax's published signer keys
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:18 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.intentrax.com/public: tools/list returned 3 tools to an anonymous client, including intentrax_verify_public_proof (write), intentrax_verify_proof_export (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http intentrax https://mcp.intentrax.com/publicclaude mcp add --transport http intentrax https://mcp.intentrax.com/publicRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__intentrax__intentrax_get_trusted_key_set"
],
"ask": [
"mcp__intentrax__intentrax_verify_public_proof",
"mcp__intentrax__intentrax_verify_proof_export"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as intentrax. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.intentrax/mcp/verify?hash=8bc20c444cb84a0f678155ada7822a6390c19c7424fce21f4f9d2eafdd4afac4" | jq -e '.changed == false'Pinned hash 8bc20c444cb8, from Nov 19, 2026, 17:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.intentrax/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.intentrax/mcp)Source: MCP Registry. Synced Nov 19, 2026, 17:17 UTC.
Intentrax proof verification MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Intentrax proof verification MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Intentrax proof verification MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Intentrax proof verification MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Intentrax proof verification MCP server have?
- 3 tools: 2 write, 1 read. intentrax_verify_public_proof, intentrax_verify_proof_export and intentrax_get_trusted_key_set.
Does the Intentrax proof verification MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Intentrax proof verification MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Intentrax proof verification MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.