Skip to main content
Glama

Related Servers

Alternatives to Redacted Context MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      D
      maintenance
      Provides 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
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to browse and read files from allowlisted folders while names, IDs, contacts, and secrets are replaced with consistent tokens locally before the agent ever sees them. The agent's final answer can then be restored to the original values locally, with no write tools and no file contents leaving the machine.
      26 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 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.
      41 PyPI
      5
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to retrieve focused, bounded repository context locally and read-only, reducing token usage while never modifying the repository or executing its code.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      A
      quality
      A
      maintenance
      Enables privacy-first, offline indexing and full-text search across local document workspaces while automatically redacting PII/secrets and enforcing path access controls before snippets reach LLMs.
      3
      MIT

    TDQS

    A4.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct operation and the descriptions explicitly cross-reference siblings (tree vs list, search vs retrieve, read vs bundle), giving an agent clear selection guidance. The github_* subset is cleanly separated from the filesystem tools with no overlap.

    Naming Consistency5/5

    All tools share the redctx_ snake_case prefix with predictable verb/noun forms (tree, list, read, search, retrieve, stat, bundle, doctor, audit, refresh_index), and the github namespace is consistently prefixed. No mixed casing or stray verb styles.

    Tool Count5/5

    Fourteen tools sit comfortably in the ideal range, and each one earns its place: filesystem navigation, content access, diagnostics, index maintenance, and a small GitHub issue surface. Nothing appears redundant or padded.

    Completeness4/5

    Coverage is strong for a read-oriented redacted-context server: hierarchy, listing, metadata, single/multi-file reads, exact and ranked search, plus diagnostics, audit, index refresh, and full issue read/list/search. Minor gaps remain, such as no explicit glob/filename-finder tool and no write operations, though these seem intentionally out of scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues