Skip to main content
Glama
sagarv48

Knowledge Fabric

by sagarv48
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Knowledge Fabric

No user-submitted related servers found.

    Related Servers

    • Evidence MCP

      zzkws
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides an evidence-oriented MCP interface for Evidence RAG Pilot, enabling retrieval of evidence packages, chunks, and evidence images from PDF-based corpora.
      1
      Apache 2.0

    • mcp-rag-platform

      mittal-umang
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables retrieval-augmented question answering with source-grounded citations, document retrieval, and idempotent ingestion through MCP tools.
      -

    • mcp-rag-service

      Gurmeher23
      F
      license
      Not graded
      quality
      C
      maintenance
      A production-minded RAG service for MCP that answers questions over your documents with hybrid retrieval, PII redaction, and source citations, packaged for Docker/Kubernetes.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clear boundaries: retrieve_evidence executes search, get_evidence fetches a chunk by ID, get_document likely fetches a full document, and the three diagnostics target different concerns (runtime health, index state, data consistency). Minor ambiguity exists between health_check and get_index_status, and get_document lacks a description, making its boundary with get_evidence less obvious.

    Naming Consistency4/5

    The set mostly follows a snake_case verb_noun pattern: list_sources, retrieve_evidence, get_document, explain_retrieval, check_consistency. health_check breaks the pattern slightly (noun-like compound instead of check_health), and get_document/get_evidence/get_index_status share the get_ prefix with different objects, which is predictable.

    Tool Count5/5

    Eight tools is well-scoped for a knowledge-retrieval and diagnostics server: query, evidence/document access, explainability, health, index status, consistency, and source discovery. Each tool serves a distinct operational need without redundancy.

    Completeness4/5

    The retrieval workflow is covered end-to-end: discover sources, retrieve evidence, fetch specific chunks/documents, explain scoring, and inspect health/index/consistency. Minor gaps are the undocumented get_document behavior and the absence of any listing/management operation beyond sources, though ingestion appears to be handled outside this server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources