Get your MCP server listed
You made something. Type its npm name and it gets a run report, a page agents can look up through Bragproof's MCP server and API, and a badge for its README. No post to write, no account, no pull request, and nothing to install.
What happens
- A public job picks it up, usually within 15 minutes. It installs the newest version from npm on a throwaway machine and starts it with no arguments, no environment and no input.
- It records what it saw: whether your server answered, what it printed if it did not, every tool and description it listed, the addresses it looked up, and the files it wrote.
- The report goes up at
https://bragproof.smaverk.com/r/your-package, signed by GitHub, so any later edit, by this site too, would show.
Getting a good report
- Answer
tools/listwithout a key. Ask for the key when a tool is called, not at start. Then agents can see what you offer before anyone signs up for anything. A large share of the servers we ran need setup first (see the numbers). - Say what is missing. If you must have a setting, print its name to the error stream before you exit. The report shows it to whoever is about to use you.
- Keep start quiet. Contacting a server just from being started shows up in the report.
- Write tool descriptions for a stranger's agent. Describe what the tool does. Text that addresses the user, other tools or private files is quoted on your report.
The badge
Once the report is in, put this in your README. It shows the newest report.
[](https://bragproof.smaverk.com/r/YOUR-PACKAGE)
Released a new version? Ask again here; a report older than a day is run afresh.
For agents
curl -X POST https://bragproof.smaverk.com/v1/requests -H 'content-type: application/json' -d '{"package":"your-package"}'
Or call request_report at https://bragproof.smaverk.com/mcp. Then read https://bragproof.smaverk.com/v1/reports/your-package.
Going further: proven calls
A run report shows that your server starts. To show that a tool works, state a claim with the exact calls that prove it, and have them run where you cannot tamper with the result.
How to add a proven call
- Write a spec: one sentence, the exact version, and one or more tool calls with what each must return.
{ "v": 1, "claim": "The echo tool returns the message it was given, prefixed with 'Echo: '.", "subject": { "kind": "mcp-stdio", "name": "mcp-echo-server", "package": "mcp-echo-server", "version": "1.0.0" }, "steps": [ { "tool": "echo", "arguments": { "message": "hello" }, "expect": { "equals": "Echo: hello" } } ], "tags": [ "mcp", "testing" ] } - In a public GitHub repository, save this as
.github/workflows/prove.yml, withspec_b64set to the output ofbase64 < spec.json | tr -d '\n', and run it from the Actions tab.name: prove on: workflow_dispatch jobs: prove: permissions: { id-token: write, contents: read } uses: itsHaddad/bragproof/.github/workflows/check.yml@check-v1 with: feed: https://bragproof.smaverk.com spec_b64: PASTE_YOUR_SPEC_BASE64_HERE - The run posts its receipt here. It is listed under proven calls and on your package's report.
The run has no API keys, so claim what works without them. For hardware evidence, the same check can run in a confidential machine: see the repository.