Skip to main content
Glama
Sign In
mcp-secret-sentinel

mcp-secret-sentinel

by AleBrito124356
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-secret-sentinel

No user-submitted related servers found.

    Related Servers

    • secretscanner

      Kiara1616
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for autonomous AI agents to scan and detect hardcoded secrets, API keys, and passwords in source code files.
      1
      MIT

    • leak-secure-mcp

      cbuntingde
      A
      license
      A
      quality
      Not graded
      maintenance
      Enterprise-grade MCP (Model Context Protocol) server for detecting secrets and sensitive information in GitHub repositories. Scans for 35+ types of secrets including API keys, passwords, tokens, and credentials with production-ready reliability features.
      5
      0
      -

    • re-leak-scan

      Heretek-RE
      A
      license
      A
      quality
      C
      maintenance
      MCP server for detecting publisher telemetry pipeline leaks in binary artifacts by scanning for sensitive strings like Sentry DSNs, Slack tokens, and AWS keys.
      6
      MIT

    • graneth-mcp

      zubovartemiy
      A
      license
      Not graded
      quality
      D
      maintenance
      An account-free MCP server that checks AI-written changes before they are committed, detecting nonexistent packages, dependency risk shapes, and hardcoded secrets.
      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

    A4.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct scope: listing patterns, scanning text/files/directories, git staged/history/range scanning, agent config auditing, and redaction. The multiple scan_* tools are differentiated by explicit target (text, file, directory, git staged, git history, git range, agent configs) rather than overlapping behavior. An agent can reliably choose the right tool from names and descriptions.

    Naming Consistency5/5

    All tool names use consistent snake_case with a predictable verb_noun pattern (list_patterns, scan_text, redact_text, scan_file, scan_directory, scan_git_staged, scan_git_history, scan_git_range, scan_agent_configs). The scan_ prefix groups related scanning operations, while list_ and redact_ are used appropriately. There is no mixing of camelCase or inconsistent verb styles.

    Tool Count5/5

    Nine tools is well scoped for a secret-scanning server. The set covers distinct scanning targets and a redaction utility without excessive fragmentation. Each tool has a clear purpose and earns its place.

    Completeness4/5

    The surface covers the core secret-detection workflow comprehensively: pattern listing, text/file/directory scanning, git staged/history/range scanning, agent config auditing, and redaction. Minor gaps exist around managing custom patterns, allowlist rules, or baselines, but these are handled by project configuration files and are not critical for the scanning lifecycle.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources