RunOnProof — Payment Decision and Agent ID
io.github.runonproofPublished by GitHub account runonproofv3.1.2Updated Oct 25, 2026
Free agent identity and signed US supplier-payment decisions. Inspect first; verify portable proof.
The publisher's own server: Proof Holdings
Overview
A remote MCP endpoint offering free agent identity and signed US supplier-payment decisions, with portable proof for inspection and verification.
- What you can do
- The listing names no individual tools, so capabilities come from the description only. It offers free agent identity, presumably so an assistant can identify itself to the service. It returns signed decisions about US supplier payments. It frames the workflow as inspecting first and then verifying portable proof of a decision.
- When to use it
- Worth considering when an assistant needs a verifiable, signed decision on whether a US supplier payment should proceed, or needs a portable proof artifact that can be checked later. Inspect the returned proof before relying on it.
- Requirements
- A remote streamable HTTP endpoint at the provider's API host; no local package, environment variables or headers are declared. The manifest declares no authentication, but the service may still expect an agent identity obtained through its own flow.
Installation
In SourceWeft
- Open RunOnProof — Payment Decision and Agent ID in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.runonproof%2Fcdo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"runonproof-payment-decision-and-agent-id": {
"type": "http",
"url": "https://api.runonproof.com/v1/agent/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
1- v3.1.2LatestSep 16, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.
Other Proof integrations
Proof Holdings
holdings.proofOfficial publisher
Proof Holdings MCP server lets an assistant run identity and control verifications (phone, email, domain, wallet), manage proof tokens and delegations, and…
Proof of Work
Published by GitHub account kivtxs
Lets an assistant read the rules of Proof of Work, check for a local account, and create an agent account to post, vote and back claims.
QuietProof
Published by GitHub account frankjie3-create
QuietProof offers free discovery tools for a catalog of deterministic, read-only audits that are paid per call in USDC on Base via x402.
SCRIPTMASTERLABS — 402Proof
com.scriptmasterlabs
Remote MCP endpoint for creating, verifying and scoring invoices settled with RLUSD on the XRPL ledger, with self-proof of settlements.
ZKStamp Proof-100
Published by GitHub account ZKStamp
Remote MCP server that writes SHA-256 fingerprints to the BitcoinZ blockchain as shielded, dated proof-of-existence timestamps.