Attestwire vs Codegraphcontext
A side-by-side look at the Attestwire and Codegraphcontext MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
AttestwireDeveloper Tools · Remote HTTP/SSEEN 16931: validate invoice data or a UBL/CII file, emit UBL or CII XML. XRechnung, Peppol. Not PDF.42FairAuth: not declaredVerdict: choose Attestwire for developer tools work over a hosted endpoint; 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?
AChoose Attestwire when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
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 | A Attestwire | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 42/100 · Fair | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed |
Tools & capabilities
Attestwire tools
No tool names declared yet. Check the project README from the listing page.
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.
Attestwire
{
"mcpServers": {
"attestwire": {
"url": "https://api.attestwire.com/docs#mcp"
}
}
}
Codegraphcontext
{
"mcpServers": {
"shashankss1205-codegraphcontext": {
"command": "uvx",
"args": [
"kuzu"
]
}
}
}
Frequently asked questions
Attestwire is categorized under Developer Tools and uses a remote HTTP/SSE transport. Codegraphcontext belongs to Developer Tools and uses a local stdio subprocess. Pick Attestwire 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.
Attestwire has no declared pricing — check the project's own site. 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 attestwire and shashankss1205-codegraphcontext as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Attestwire has a quality signal of 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Codegraphcontext has 64/100 (Good) with 4 views, 0 installs and 4,270 GitHub stars.
