ProofMart
REMOTE · PROOFMART.FLY.DEV
One-stop claim verification for AI agents: verdicts with confidence, evidence, signed receipts.
Available components
Last scanned (13 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 663 tokens (~221/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 50% → 67% ▲ functional
- Server version: 0.11.0 → 0.12.0 functional
- Server version: 0.10.0 → 0.11.0 functional
- Server version: 0.8.0 → 0.10.0 functional
- New tool “check_agent_conduct” functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 25 Oct 26 70
First indexed and scored.
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 5 Nov 2026 · Probed https://proofmart.fly.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fly.dev | CN=YE1,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5e6e25e6df778e81cd07b85fc9f12d4df7d |
| SANs: *.fly.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 proofmart.fly.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fly.dev. | 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 | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://proofmart.fly.dev/mcp | Verified | 200 | |
| http (plaintext) | http://proofmart.fly.dev/mcp | HTTPS enforced | 301 | https://proofmart.fly.dev/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 →
check_agent_conduct Pull an agent's conduct record (Conduct Feed) ~253
Ask the Conduct Feed — a separate business from ProofMart, whose records are built from ProofMart check receipts — how an agent has behaved: a 0-100 conduct score with its component scores, the evidence mix behind it (event counts by tier, record span, settled payments), contested markings, and a signed attestation. Identify the agent by customer_id (a ProofMart customer number) or by wallet (its x402 payer address). Your OWN record is free when you send your customer key; pulling another agent's record costs $0.05, paid in USDC over x402: a call that needs payment is answered 402 with payment requirements in the PAYMENT-REQUIRED header — pay and retry with the signed payment in the PAYMENT-SIGNATURE header. An agent with no history answers standing 'no_record' — never a fabricated score. Full method: GET /conduct/methodology.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | – | The agent's ProofMart customer id number. |
| identity | string | – | A full identity string: 'customer:<id>' or 'wallet:<address>'. |
| wallet | string | – | The agent's wallet address (0x…), as used to pay over x402. |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | object | – | – |
| components | object | – | – |
| evidence | object | – | – |
| identity | string | yes | – |
| score | integer|null | – | – |
| standing | string | yes | – |
No examples provided.
list_plans List ProofMart plans ~47
The ProofMart menu: each plan's monthly check bundle and draft price. Free to call — no key needed, nothing metered. Useful when an owner asks what subscribing would get them.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_claim Verify a factual claim ~138
Submit one factual claim to ProofMart and get back a verdict (TRUE / FALSE / MIXED / UNVERIFIED), a confidence score (0-100), the evidence behind the verdict, and a signed receipt. Verdicts are remembered in ProofMart's Ledger: a claim that was already checked and is still fresh is answered instantly from memory (the result's 'source' field says 'ledger'; fresh research says 'checker'). Compound claims are split into individual facts automatically. One call = one metered check against the customer's plan.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | The factual claim to verify, e.g. 'The Eiffel Tower is in Paris.' |
| Name | Type | Req | Description |
|---|---|---|---|
| account | object | – | – |
| claim | string | yes | – |
| confidence | integer | yes | – |
| evidence | array | – | – |
| receipt | object | – | – |
| source | string | – | – |
| verdict | string | yes | – |
No examples provided.
How do I install the ProofMart MCP server?
ProofMart is a hosted endpoint at https://proofmart.fly.dev/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 · proofmart.fly.dev
claude mcp add --transport http proofmart-proofmart 'https://proofmart.fly.dev/mcp'
What is the ProofMart MCP server?
ProofMart is an MCP server listed in the public MCP registry as io.github.ProofMart/proofmart. One-stop claim verification for AI agents: verdicts with confidence, evidence, signed receipts. This page covers its hosted endpoint (https://proofmart.fly.dev/mcp).
Is the ProofMart MCP server safe to use?
ProofMart scores 73 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 ProofMart MCP server expose?
ProofMart exposes 3 tools: verify_claim, check_agent_conduct, list_plans. Their descriptions and schemas cost roughly 438 tokens of context every time the server is loaded.
Does the ProofMart MCP server require authentication?
No. We connected to ProofMart without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ProofMart MCP server still maintained?
ProofMart is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.