Skip to main content
Glama
VeritasGraph

VeritasGraph

by bibinprathap

Related Servers

Alternatives to VeritasGraph

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An 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
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP 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.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for local RAG over personal notes, PDFs, and documents, enabling plain-English querying and hybrid search with multi-hop context expansion.
      MIT

    TDQS

    B3.2/5.0

    Scored across 17 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data