Veritasgraph vs Fetch
A side-by-side look at the Veritasgraph and Fetch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Veritasgraph for search & data extraction work as a local process; choose Fetch for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Veritasgraph when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- You want tools like
veritasgraph_ingest_document, veritasgraph_query, veritasgraph_search_entities.
Choose Fetch when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
fetch.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 64/100 · Good | 80/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 325 | 91,526 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 5 | 1 |
| Full listing | View Veritasgraph | View Fetch |
Tools & capabilities
Veritasgraph tools 5
veritasgraph_ingest_documentIngest a document into the VeritasGraph knowledge graph. Chunks the text, extracts entities and relationships with a local model, and records the source chunk behind every node/edge for verifiable attribution.veritasgraph_queryAsk a question and get a graph-grounded, multi-hop answer with verifiable [doc#chunk] citations and the reasoning path used.veritasgraph_search_entitiesRetrieve the subgraph most relevant to a query (entities, relationships, seeds) without invoking the LLM. Fast graph lookup.veritasgraph_get_graphReturn the full knowledge graph: all nodes, edges, and stats.veritasgraph_clear_graphClear the entire knowledge graph (destructive; removes all data).
Fetch tools 1
fetchFetches a URL from the internet and extracts its contents as markdown.
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.
Veritasgraph
{
"mcpServers": {
"veritasgraph": {
"command": "uvx",
"args": [
"veritasgraph-mcp"
]
}
}
}
Fetch
{
"mcpServers": {
"fetch": {
"command": "uvx",
"args": [
"mcp-server-fetch"
]
}
}
}
Frequently asked questions
Veritasgraph is categorized under Search & Data Extraction and uses a local stdio subprocess. Fetch belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Veritasgraph for search & data extraction work and Fetch for search & data extraction.
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.
Veritasgraph is bring-your-own-key: usage is billed by the API provider you supply a key for. Fetch 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 veritasgraph and fetch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Veritasgraph has a quality signal of 64/100 (Good) with 0 views, 0 installs and 325 GitHub stars. Fetch has 80/100 (Excellent) with 5 views, 0 installs and 91,526 GitHub stars.