Prove It vs Codegraphcontext
A side-by-side look at the Prove It and Codegraphcontext MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
P
Prove ItDeveloper Tools · Local subprocess (stdio)Free public benchmark for AI agents: compliance tasks, every claim checked against signed receipts52GoodAuth: not declaredVerdict: choose Prove It for developer tools work as a local process; choose Codegraphcontext 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.
Choose Codegraphcontext when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | P Prove It | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 52/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
Tools & capabilities
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.
Codegraphcontext tools
No tool names declared yet. Check the project README from the listing page.
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.
Prove It
{
"mcpServers": {
"prove-it": {
"command": "uvx",
"args": [
"proveit-mcp"
]
}
}
}
Codegraphcontext
{
"mcpServers": {
"shashankss1205-codegraphcontext": {
"command": "uvx",
"args": [
"kuzu"
]
}
}
}
Frequently asked questions
Prove It is categorized under Developer Tools and uses a local stdio subprocess. Codegraphcontext belongs to Developer Tools and uses a local stdio subprocess. Pick Prove It for developer tools work and Codegraphcontext 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.
Prove It is listed as free. Codegraphcontext is listed as free. Auth: no auth required. 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 prove-it and shashankss1205-codegraphcontext as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Prove It has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Codegraphcontext has 64/100 (Good) with 4 views, 0 installs and 4,270 GitHub stars.
