Skip to main content
Glama
bibinprathap

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
      B
      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
      A
      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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: clearing the graph, retrieving the full graph, ingesting documents, querying with reasoning, and searching entities. No ambiguity or overlap.

    Naming Consistency4/5

    All tools use the 'veritasgraph_' prefix and mostly follow a verb_noun pattern (e.g., clear_graph, get_graph, ingest_document, search_entities). 'query' deviates slightly as a single verb, but it's still clear and consistent in style.

    Tool Count5/5

    With 5 tools, the set is well-scoped for a knowledge graph server, covering ingestion, retrieval, searching, and clearing without being excessive or insufficient.

    Completeness4/5

    The tool set covers core operations: create (ingest), read (get_graph, search_entities, query), and delete (clear_graph). Minor gaps include the lack of update or individual entity deletion, but these are reasonable omissions for the intended use case.

    Maintenance

    ActivityActive
    ResponsivenessNo issues