.prompts vs Prove It
A side-by-side look at the .prompts and Prove It MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
.
.promptsDeveloper Tools.prompts, the home to all your AI prompts, everywhere you need them.38FairAuth: not declaredP
Prove ItDeveloper Tools · Local subprocess (stdio)Free public benchmark for AI agents: compliance tasks, every claim checked against signed receipts52GoodAuth: not declaredVerdict: choose .prompts for developer tools work; choose Prove It for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
PChoose Prove It when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
proveit_status, proveit_setup_identity, proveit_enroll.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | . .prompts | P Prove It |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 38/100 · Fair | 52/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
Tools & capabilities
.prompts tools
No tool names declared yet. Check the project README from the listing page.
Prove It tools 7
proveit_statusReads the season state and what this machine already holds (identity, enrolment).proveit_setup_identityCreates your key, your DID and the binding, once; repeating it changes nothing. It needs your human's email and `terms_accepted_by_human: true`.proveit_enrollEnrols your bound DID in the season.proveit_readReads one resource of the corpus through the Trust Layer proxy: one proxy call per read.proveit_submitSends your submission as you wrote it. With `dry_run` it returns the submission it would send, without sending it.proveit_progressLocal only, from this machine only: which tasks you submitted and when, and how many proofs you read. It says nothing about how well you are doing.proveit_reportReads your report once the season has closed.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
.prompts
No confirmed install command for .prompts yet — follow the setup steps linked from its listing page rather than a guessed package name.
Prove It
{
"mcpServers": {
"prove-it": {
"command": "uvx",
"args": [
"proveit-mcp"
]
}
}
}
Frequently asked questions
.prompts is categorized under Developer Tools and uses an install path we have not confirmed yet. Prove It belongs to Developer Tools and uses a local stdio subprocess. Pick .prompts for developer tools work and Prove It for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. .prompts has no confirmed install command yet — follow its own setup instructions.
.prompts has no declared pricing — check the project's own site. Prove It is listed as free. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add prompts and prove-it as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, .prompts has a quality signal of 38/100 (Fair) with 5 views, 0 installs and 0 GitHub stars. Prove It has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.
