proofrun MCP server
dev.pages.proofrun/proofrunproofrun.pages.devstreamable-httpv0.1.0Scanned
ProofRun: bounded HTTP acceptance checks for agent deployments. $0.01 USDC per pack.
5 tools: 3 change things and 2 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
3 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 proofrun MCP server can do
The proofrun MCP server is published by proofrun.pages.dev, a domain the MCP Registry verified. It has 5 tools. It can create or change data (3 tools: enroll_target, verify_target and preflight_pack), but cannot delete data. 2 tools only read.
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 15, 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.
5 tools
Changes things 3Claude Code: ask
enroll_targetStart authorization and origin-control proof for up to five exact read-only HTTPS GET paths.No findings
Why it is in this group
- The description's first verb is "start": a word for a change.
Description, as the server wrote it Start authorization and origin-control proof for up to five exact read-only HTTPS GET paths. Serve the returned proof JSON at proof_url before verifying. Private read_token must be generated and saved by the caller.
preflight_packFree configuration and enrollment preflight before paying.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.
Description, as the server wrote it Free configuration and enrollment preflight before paying. Validates exact authorized paths, pack and idempotency format; refuses an existing caller payment attempt. Makes no target request, signature, settlement or ledger write. Not a deployment test, wallet/balance check or capacity reservation.
verify_targetVerify the exact proof file for a previously started enrollment.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.
Description, as the server wrote it Verify the exact proof file for a previously started enrollment. Successful enrollment expires after 24 hours.
Only reads 2Show 2 read-only tools
read_reportRead or reconcile the original private report for a purchase.No findings
Why it is in this group
- The name "read_report" says "read": a word for reading.
Description, as the server wrote it Read or reconcile the original private report for a purchase. Use the ORIGINAL idempotency_key, not the report_id UUID. Free; never signs or charges. If state is uncertain do not pay again. Requires the original private read token; reports expire after seven days.
verify_deploymentReturn a $0.01 native Base USDC x402 challenge without paying.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Return a $0.01 native Base USDC x402 challenge without paying. For execution supply a verified enrollment, private read token, idempotency key and caller-created payment_signature or headers.PAYMENT-SIGNATURE. Only that payment header is accepted; enrollment/read token/idempotency remain explicit. Never creates a wallet signature. Returns bounded independent HTTP assertions, not security or full-application certification.
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 20, 2026, 18:52 UTC, unchanged since Oct 22, 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
- 3
- 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 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://proofrun.pages.dev/mcp: tools/list returned 5 tools to an anonymous client, including enroll_target (write), verify_target (write), preflight_pack (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 proofrun https://proofrun.pages.dev/mcpclaude mcp add --transport http proofrun https://proofrun.pages.dev/mcpRun 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__proofrun__verify_deployment",
"mcp__proofrun__read_report"
],
"ask": [
"mcp__proofrun__enroll_target",
"mcp__proofrun__verify_target",
"mcp__proofrun__preflight_pack"
],
"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 proofrun. 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/dev.pages.proofrun/proofrun/verify?hash=15a2dea5b9c0c055f53de69513c4d07035b9291e44904ed0b9085a676faa1bfd" | jq -e '.changed == false'Pinned hash 15a2dea5b9c0, from Nov 15, 2026, 03:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.pages.proofrun/proofrun/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.pages.proofrun/proofrun)Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.
proofrun MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the proofrun MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 3 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 proofrun MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the proofrun 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 proofrun MCP server have?
- 5 tools: 3 write, 2 read. enroll_target, verify_target, preflight_pack, verify_deployment and read_report.
Does the proofrun MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the proofrun MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the proofrun MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.