Proofrun

dev.workers.jeffmarcilliat.proofrun-closedv0.1.0Updated Oct 27, 2026

ProofRun: bounded HTTP acceptance checks for agent deployments. $0.01 USDC per pack.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

ProofRun is a remote MCP endpoint offering bounded HTTP acceptance checks for agent deployments, billed at $0.01 USDC per pack.

What you can do
  • Run bounded HTTP acceptance checks against a deployed agent or service.
  • Verify that an agent deployment responds as expected over HTTP.
  • Purchase check packs, priced at $0.01 USDC each.
  • No tool list is published, so the exact operations available are not documented in the supplied material.
When to use it
Consider it when you want an assistant to run quick HTTP acceptance checks on an agent deployment and are willing to pay a small per-pack USDC fee.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. The listing declares no authentication, environment variables or headers. Payment in USDC is required at $0.01 per pack, so a wallet or payment arrangement is implied.
Before you install
The service charges money: $0.01 USDC per pack, so usage can spend funds. No authentication is declared, and no tool list or documentation is provided, so the scope of what it does with your requests is unclear. Checks send HTTP requests to the targets you specify.

Installation

In SourceWeft

  1. Open Proofrun in the dashboard and add it to a workspace.
  2. 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/dev.workers.jeffmarcilliat.proofrun-closed%2Fproofrun/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "proofrun": {
      "type": "http",
      "url": "https://proofrun-closed.jeffmarcilliat.workers.dev/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestOct 11, 2026

Score

17% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.