VeritasGraph
Related Servers
Alternatives to VeritasGraph
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceLocal-first MCP graph intelligence server providing RRF hybrid search, multi-hop traversal, source snippets, and rationale nodes for AI agents, without Docker or web UI.5-
- FlicenseNot gradedqualityDmaintenanceA local-first, LLM-agnostic MCP server that lets you ask hard questions about your documents, media, and code, and get traceable answers entirely offline.-
- FlicenseNot gradedqualityDmaintenanceA local-first MCP server that transforms crypto whitepapers into a knowledge graph and vector corpus, enabling entity-filtered RAG question answering with optional knowledge graph enrichment.-
- AlicenseNot gradedqualityDmaintenanceAn open-source MCP server for RAG over personal documents. Supports three parallel strategies — Traditional, Contextual, and Graph RAG — with all data stored locally for privacy.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for building knowledge graphs from documents. It ingests PDF/PPTX/DOCX files, transcribes to Markdown, and uses LLM to bootstrap entity patterns and build a JSONL knowledge graph with RAG chunks.-
- AlicenseNot gradedqualityBmaintenanceMCP server for local RAG over personal notes, PDFs, and documents, enabling plain-English querying and hybrid search with multi-hop context expansion.MIT
TDQS
Scored across 17 tools
Most tools have clearly distinct targets: graph QA (query) versus SQL QA (structured_ask), full graph (get_graph) versus subgraph (search_entities) versus single entity (get_entity), each at a distinct granularity. The weakest boundary is glossary terms (search_terms/get_term) versus structured-data catalog terms (structured_search/structured_get_term), which share vocabulary and could be misselected by an agent despite the 'structured_' prefix hinting at the distinction.
The set is overwhelmingly verb_noun (get_entity, search_terms, propose_term, ingest_document, import_graph), with a coherent 'structured_' namespace for the SQL sub-domain. Minor deviations: bare 'query' lacks a noun, 'compile_status' is a noun phrase with no verb, and the structured_* tools put the namespace before the verb, inverting the dominant pattern.
17 tools spans three coherent sub-surfaces (graph QA/verification, ontology+glossary curation, structured-data access) plus ingestion, and each tool maps to a real operation. It is on the heavy side of the ideal band and a few read tools (e.g. get_term vs search_terms) could be merged, but nothing feels gratuitous.
Core workflows are covered end-to-end: ingest, query with citations, verify via receipts and check_answerable, inspect ontology and entities, and query structured data. However, the curation lifecycle is a dead end — propose_term exists and compile_status reports open curation suggestions, but there is no tool to list, certify, update, or delete terms/suggestions, and receipts expose feedback with no way to submit it.