xProof
REMOTE · XPROOF.APP · SCANNED SEP 20
Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the xProof MCP server?
xProof is a hosted endpoint at https://xproof.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · xproof.app
claude mcp add --transport http jasonxkensei-xproof 'https://xproof.app/mcp'
{
"mcpServers": {
"jasonxkensei-xproof": {
"url": "https://xproof.app/mcp"
}
}
} {
"servers": {
"jasonxkensei-xproof": {
"type": "http",
"url": "https://xproof.app/mcp"
}
}
} [mcp_servers.jasonxkensei-xproof] url = "https://xproof.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jasonxkensei-xproof": {
"type": "remote",
"url": "https://xproof.app/mcp",
"enabled": true
}
}
} openclaw mcp add jasonxkensei-xproof --url 'https://xproof.app/mcp' --transport streamable-http
mcp_servers:
jasonxkensei-xproof:
url: "https://xproof.app/mcp" {
"McpServers": {
"jasonxkensei-xproof": {
"Transport": "http",
"Url": "https://xproof.app/mcp"
}
}
} assistant mcp add jasonxkensei-xproof -t streamable-http -u 'https://xproof.app/mcp'
{
"mcpServers": {
"jasonxkensei-xproof": {
"type": "http",
"url": "https://xproof.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.80 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server changed its declared name: xproof → prove-before-act security
- 1 Aug 26 0
- Schema quality: 126 → 144 ▼ functional
- New tool “check_coherence” functional
- New tool “require_coherence_anchor” functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://xproof.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=xproof.app | CN=YE2,O=Let's Encrypt,C=US | 8 Jul 2026 | 6 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5199a3ee140d4f99519862f515b7790b893 |
| SANs: xproof.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of xproof.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| xproof.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 301 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://xproof.app/mcp | Redirected | 301 | https://provebeforeact.com/mcp |
| http (plaintext) | http://xproof.app/mcp | HTTPS enforced | 301 | https://xproof.app:443/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_agent_session ~354
Certify an AI agent's work session on the MultiversX blockchain BEFORE executing any critical action (trade, deploy, data access). Returns a proof_id compliance certificate. The agent MUST call this tool before acting — certification failure blocks execution. Governance: set reversibility_class='irreversible' for actions that cannot be undone — a policy violation is flagged if confidence_level < 0.95 on irreversible decisions. Schema: https://xproof.app/.well-known/agent-audit-schema.json
| Name | Type | Req | Description |
|---|---|---|---|
| action_description | string | yes | Human-readable description of the specific action |
| action_type | string | yes | Category of the action being certified |
| agent_id | string | yes | Identifier of the agent making the decision |
| context | object | – | Optional additional context (model version, environment, tool chain, etc.) |
| decision | string | yes | Agent's decision about whether to proceed |
| inputs_hash | string | yes | SHA-256 of all inputs analyzed before making the decision |
| reversibility_class | string | – | Governance: how reversible is this action? 'reversible' = can be undone at low cost, 'costly' = reversible but expensive (fees, slippage, delay), 'irreversible' = cannot be undone (on-chain settlemen… |
| risk_level | string | yes | Assessed risk level of the action |
| risk_summary | string | – | Optional brief risk analysis justifying the decision |
| session_id | string | yes | Unique session identifier (UUID or timestamp-based) |
| timestamp | string | yes | ISO 8601 timestamp of when the decision was made |
No output schema declared.
No examples provided.
certify_file ~123
Create a blockchain certification for a file. Records the SHA-256 hash on MultiversX blockchain as immutable proof of existence and ownership. Cost: $0.01 per certification, paid in EGLD.
| Name | Type | Req | Description |
|---|---|---|---|
| author_name | string | – | Name of the certifier (default: AI Agent, max 128 chars) |
| file_hash | string | yes | SHA-256 hash of the file (64 hex characters) |
| filename | string | yes | Original filename with extension (max 255 chars) |
| webhook_url | string | – | Optional HTTPS URL for on-chain confirmation callback |
No output schema declared.
No examples provided.
certify_with_confidence ~401
Create a staged blockchain certification with a confidence score. Use this when your decision builds progressively — certify at 60% (initial assessment), 80% (pre-commitment), and 100% (final decision). Each stage shares the same decision_id, creating an on-chain audit trail of the decision process. Governance: set reversibility_class='irreversible' for actions that cannot be undone — xproof will flag a policy violation if confidence_level < 0.95. Cost: $0.01 per certification.
| Name | Type | Req | Description |
|---|---|---|---|
| author_name | string | – | Name of the certifying agent (default: AI Agent, max 128 chars) |
| confidence_level | number | yes | Confidence score from 0.0 to 1.0. Typical values: 0.6 (initial), 0.8 (pre-commitment), 1.0 (final). |
| decision_id | string | yes | Shared UUID linking all confidence stages for the same decision. Generate once and reuse across all stages. |
| file_hash | string | yes | SHA-256 hash of the decision or output file (64 hex characters) |
| filename | string | yes | Original filename with extension (e.g. decision.json, max 255 chars) |
| reversibility_class | string | – | Governance: how reversible is this action? 'reversible' = can be undone, 'costly' = reversible but expensive, 'irreversible' = cannot be undone (on-chain settlement, data deletion, sent email). When… |
| threshold_stage | string | yes | Named stage of the decision: initial (first assessment), partial (gathering info), pre-commitment (almost certain), final (committed). |
| who | string | – | Agent identity (wallet address, name, or agent ID) |
| why | string | – | Reason or instruction hash driving this decision |
No output schema declared.
No examples provided.
check_attestations ~106
Check domain-specific attestations for an AI agent wallet on xproof. Returns active attestations issued by third-party certifying bodies (healthcare, finance, legal, security, research). Each active attestation adds +50 to the agent's trust score (max +150 from 3 attestations). Use this to verify an agent's credentials before delegating a sensitive task.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | MultiversX wallet address (erd1...) of the agent to check |
No output schema declared.
No examples provided.
check_coherence ~237
Anchor your agent's reasoning as an immutable WHY proof BEFORE executing an action. Implements the Prove Before Act / Coherence Layer pattern. Pass intent (goal), context (facts considered), and decision (action about to execute). Receives: proof_id, coherence_anchor (SHA-256 of the payload), timestamp. Link the returned proof_id to your WHAT proof via certify_file metadata.why_proof_id to complete the full 4W audit trail. Cost: $0.01 per anchor (same as certify_file).
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Relevant facts, constraints, and inputs considered before the decision (e.g. 'BTC RSI=38, allocation 2.1%, policy v3.1') |
| decision | string | yes | The specific action the agent is about to execute (e.g. 'BUY 0.5 BTC at market') |
| intent | string | yes | The agent's stated goal or objective for this action (e.g. 'Optimize portfolio allocation for Q3') |
| who | string | – | Agent identifier — wallet address, agent name, or model id (default: derived from API key owner) |
No output schema declared.
No examples provided.
discover_services ~24
Discover available xproof certification services, pricing, and capabilities. No authentication required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_calibration ~115
Query an agent's calibration quality over time: mean confidence gap, variance, bias label (overconfident / underconfident / calibrated), and per-decision time series. Fully public — use this to evaluate another agent before trusting it. agentId accepts a MultiversX wallet address (erd1...) or internal user id.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent wallet address (erd1...) or internal user id |
| n | integer | – | Number of recent outcomes to include (default 50, max 200) |
No output schema declared.
No examples provided.
get_proof ~56
Retrieve a proof in structured JSON or Markdown format. Use JSON for machine processing, Markdown for LLM consumption.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format: json or md |
| proof_id | string | yes | UUID of the certification |
No output schema declared.
No examples provided.
investigate_proof ~167
Reconstruct the full 4W audit trail for a contested agent action. Returns WHO (agent identity + SIGIL), WHAT (SHA-256 hash on-chain), WHEN (MultiversX block timestamp), WHY (decision chain anchored before acting). Includes verification summary with intent_preceded_execution flag, chronological timeline of WHY/WHAT proofs, and session heartbeat anchor. Requires x402 payment ($0.01 USDC on Base via X-PAYMENT header) or API key authentication. Without payment, returns payment requirements with USDC address and amount.
| Name | Type | Req | Description |
|---|---|---|---|
| proof_id | string | yes | UUID of any proof in the action pair — WHY (reasoning), WHAT (action), or heartbeat session proof |
| wallet | string | yes | Agent wallet address (erd1...) that owns the proof |
No output schema declared.
No examples provided.
register_trial ~103
START HERE if you have no API key. Get 10 free on-chain certifications instantly — no wallet, no credit card, no account required. Call this once with any agent_name, receive a pm_ key, then use certify_file or audit_agent_session immediately. Takes under 1 second.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | A short identifier for your agent (e.g. 'trading-bot', 'my-langchain-agent'). Must be unique across the platform. |
No output schema declared.
No examples provided.
require_coherence_anchor ~286
Policy gate: verify a valid, unexpired coherence anchor (WHY proof) exists for a given intent BEFORE allowing an action to execute. Call this from an orchestrator before delegating a sub-action. Pass either the exact intent_hash (the coherence_anchor returned by check_coherence) or the same intent + context + decision payload (the anchor hash is recomputed deterministically). Returns { allowed, anchor_id, expires_at }. If allowed=false, block execution and call check_coherence first. Free — no credit consumed.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | The facts considered — must be byte-identical to the check_coherence call |
| decision | string | – | The action to execute — must be byte-identical to the check_coherence call |
| intent | string | – | The stated goal — must be byte-identical to the check_coherence call (used with context + decision to recompute the anchor hash) |
| intent_hash | string | – | The coherence_anchor hash returned by check_coherence (64 hex chars). Fastest path — pass this if you have it. |
| max_age_minutes | integer | – | Anchor validity window in minutes (default 120 = 2h). Anchors older than this are considered expired/divergent. |
| who | string | – | Agent identifier — must match the value used in check_coherence (default: derived from API key owner) |
No output schema declared.
No examples provided.
submit_outcome ~121
Submit the actual outcome for a decision previously anchored with metadata.confidence_level. Computes the confidence gap (anchored − actual) and stores it for calibration tracking. Operator-only — you must own the proof. Each proof can only have one outcome.
| Name | Type | Req | Description |
|---|---|---|---|
| outcome_score | number | yes | Actual outcome quality (0.0 = complete failure, 1.0 = fully successful) |
| proof_id | string | yes | UUID of the certification that was anchored with metadata.confidence_level |
| visibility | string | – | Whether this outcome is publicly visible (default: public) |
No output schema declared.
No examples provided.
verify_proof ~46
Verify an existing xproof certification. Returns proof details including file hash, timestamp, blockchain transaction, and verification status.
| Name | Type | Req | Description |
|---|---|---|---|
| proof_id | string | yes | UUID of the certification to verify |
No output schema declared.
No examples provided.
What is the xProof MCP server?
xProof is an MCP server listed in the public MCP registry as io.github.jasonxkensei/xproof. Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs. This page covers its hosted endpoint (https://xproof.app/mcp).
Is the xProof MCP server safe to use?
xProof scores 25 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the xProof MCP server expose?
xProof exposes 13 tools: register_trial, certify_file, certify_with_confidence, verify_proof, get_proof, and 8 more. Their descriptions and schemas cost roughly 2,139 tokens of context every time the server is loaded.
Does the xProof MCP server require authentication?
No. We connected to xProof without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the xProof MCP server still maintained?
xProof is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.