Local Evidence MCP
Related Servers
Alternatives to Local Evidence MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to read only explicitly allowlisted Linux project files and selected Codex conversation turns. It supports listing projects and files, reading UTF-8 files, bounded text search, and paged reading of authorized conversations.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to browse selected folders, search filenames, inspect metadata, and read bounded UTF-8 text files through a read-only, token-authenticated interface.1MIT
- AlicenseAqualityBmaintenanceA local-first MCP server for retrieving a small evidence set and recording reviewed conclusions, policy-gated and redacted without giving an agent general filesystem access.5MIT
- FlicenseNot gradedqualityCmaintenanceProvides read-only, citation-backed semantic search and retrieval-augmented generation over enterprise documents via standardized MCP tools, with local embeddings for privacy.-
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to search and read a folder of Markdown/text documents via a read-only MCP server with hybrid BM25 and local embedding search, treating the calling model as untrusted.148 npmMIT
- FlicenseAqualityCmaintenanceProvides read-only MCP tools to search and retrieve evidence-grounded knowledge compiled from video content, including hybrid semantic and lexical search with citations.5-
TDQS
Scored across 5 tools
Each tool targets a clearly distinct operation: status (introspection), search (query), read (fetch single note), create_note (write), and append_lesson (ledger write). There is no meaningful overlap between search/read or create/append, and the descriptions make the boundaries explicit.
All tools share the evidence_ prefix followed by a clear snake_case verb or noun (status, search, read, create_note, append_lesson). The pattern is predictable and readable throughout.
Five tools is well-scoped for a local evidence/notes server, covering introspection, retrieval, and writing without redundancy. Each tool earns its place.
The surface covers the core lifecycle: status, search, read, create, and append. Update/delete are absent, but the 'never overwrite' policy and append-only ledger suggest this is intentional immutability rather than a gap.