Skip to main content
Glama
mtn888

document-evidence-mcp

by mtn888
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to document-evidence-mcp

No user-submitted related servers found.

    Related Servers

    • Knowledge Fabric

      sagarv48
      A
      license
      B
      quality
      A
      maintenance
      An MCP-native evidence retrieval platform that ingests source material, builds lexical and vector indexes, performs hybrid retrieval, and returns structured evidence packages for AI assistants.
      8
      8
      Apache 2.0

    • local-Rag

      zongzi-zongzhi
      A
      license
      A
      quality
      D
      maintenance
      A local-first document retrieval MCP server that enables AI coding tools like Codex to search private local documents via semantic search and keyword boost, supporting ingestion of PDF, DOCX, TXT, Markdown, and HTML files.
      7
      MIT

    • 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

    • rag

      akshayvarala
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to retrieve relevant context from local documents via MCP tools, supporting ingestion, semantic search, metadata filtering, and evidence inspection entirely on-device.
      MIT

    • vectorise-mcp

      jameslovespancakes
      A
      license
      Not graded
      quality
      D
      maintenance
      Local MCP server that indexes folders of documents into a hybrid vector + keyword search index for Claude Desktop, with support for PDFs, Office files, and images via OCR.
      MIT
    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

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the document evidence lifecycle: ingestion, searching, retrieval by ID, document listing, document metadata, rendering crops, and health checks. The overlapping-sounding pairs (search/get, list/get) are clearly differentiated by their descriptions and return types.

    Naming Consistency4/5

    Six of seven tools follow a consistent verb_noun pattern (ingest_document, search_evidence, get_evidence, list_documents, get_document, render_crop). The lone exception is 'doctor', which breaks the pattern and is the only naming inconsistency.

    Tool Count5/5

    Seven tools is well-scoped for a document evidence management server, covering the full workflow from ingestion through search, retrieval, rendering, and diagnostics. Each tool has a clear purpose with no redundancy.

    Completeness5/5

    The toolset provides a complete lifecycle from ingestion to evidence retrieval and rendering, including document management and a health check. There are no obvious missing operations, as updates can be handled via explicit new revisions during ingestion.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources