Skip to main content
Glama
Rlealbarili

governed-rag-mcp

by Rlealbarili
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to governed-rag-mcp

No user-submitted related servers found.

    Related Servers

    • SQAI by thyn-ai

      SQAIofficial

      thyn-ai
      A
      license
      A
      quality
      B
      maintenance
      Official SQAI MCP server: governed structured data access powered by Mojo kernels. 3 stdio tools: listSources (discovery), queryData (deterministic read-only queries + compute with provenance), explainQuery (dry-run validation). Introspection needs no credentials; execution requires a one-time free sqai login. npm: @thyn-ai/sqai-mcp. Source: packages/mcp. Registry: io.github.thyn-ai/sqai.
      4
      Apache 2.0

    • policy-corpus

      MkRafa
      F
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server providing 5 tools for hybrid search, clause retrieval, policy versioning, code lookup, and plan rider override queries over a synthetic medical-policy corpus.
      -

    • Aegis

      Demi8-patch
      F
      license
      A
      quality
      C
      maintenance
      Provides read-only MCP tools to search and retrieve evidence-grounded knowledge compiled from video content, including hybrid semantic and lexical search with citations.
      5
      -

    • Archive MCP Server

      Surajp1602
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables querying enterprise records and retention policies from any MCP client over stdio, with read-only tools for searching records, fetching retention verdicts, identifying archival candidates, summarizing departments, forecasting retentions, and viewing audit history.
      -
    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

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing source metadata, checking system status, and performing search. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    Two tools use verb_noun naming (list_knowledge_sources, search_knowledge), while rag_status follows a noun_noun pattern. The inconsistency is minor and does not hinder readability.

    Tool Count4/5

    Three tools is a reasonable count for a focused RAG server that provides search and monitoring capabilities. While on the small side, it is neither too sparse nor overwhelming.

    Completeness4/5

    The surface covers core operations: listing sources, searching, and checking status. Missing management operations like adding/removing sources may be out of scope for a governed read-only interface.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources