Redacted Context MCP
Related Servers
Alternatives to Redacted Context MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceProvides LLMs with safe, read-only access to local codebases for searching, reading files, and finding function definitions. All source code remains local, ensuring privacy while enabling AI assistants to explore project structures and functionality.4-
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with secure, read-only file system access to analyze and understand project codebases, enabling multi-repository context aggregation and cross-project code tracing.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to safely inspect a local repository's code and metadata while blocking private data from leaving the machine, providing read-only tools for search, change tracking, and integrity verification.MIT
- AlicenseAqualityCmaintenanceEnables AI clients to securely inspect local source repositories with read-only tools for listing files, reading files, and searching text, while enforcing path traversal protection and sensitive-file filtering.3MIT
- AlicenseAqualityBmaintenanceEnables coding agents to retrieve token-budgeted, source-hashed code context from explicitly registered local repositories via read-only MCP tools, reducing broad repository crawling while providing structure, symbols, and impact slices.9MIT
- AlicenseNot gradedqualityAmaintenanceCombines AST intelligence and guarded file operations to provide a secure, controlled repository workflow for coding agents, enabling structural code analysis and safe edits without unbounded editor access.306 npmMIT
TDQS
Scored across 14 tools
redctx_search and redctx_retrieve both perform redacted text lookup with only subtle differences in ranking behavior, while redctx_list and redctx_tree both enumerate redacted paths and could be easily confused. Descriptions help somewhat, but several tool boundaries are not crisp.
All tools share the redctx_ prefix and mostly use snake_case verbs like search, refresh, retrieve, list, read, and stat. However, a few names are bare nouns (tree, bundle, doctor, audit) and the github_* sub-namespace mixes styles, creating minor inconsistency.
With 14 tools, the server is well-scoped for its stated purpose of redacted file and issue exploration. Each tool covers a distinct aspect of the workflow without drowning the agent in redundant endpoints.
The surface provides thorough read-oriented coverage: search, retrieve, tree, list, read, stat, bundle, plus safety checks and GitHub issue reads. The only real gaps are write/update operations and deeper GitHub interactions, but those are arguably out of scope for a redaction/context tool.