Skip to main content
Glama
AleBrito124356

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.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct input target: raw text, single file, directory tree, git staged diff, git history, and a git range. The three git tools (staged/history/range) could superficially overlap, but their descriptions crisply define different scopes (pre-commit checkpoint, past commits, pre-push range), and list_patterns is clearly the only non-scanning tool.

    Naming Consistency5/5

    All seven tools follow a strict verb_noun convention (list_patterns, scan_text, scan_file, scan_directory, scan_git_staged, scan_git_history, scan_git_range). The scan_git_* family is a predictable, self-describing sub-pattern that makes the set easy to navigate.

    Tool Count5/5

    Seven tools is well-scoped for a secret scanner: one introspection tool plus six scan variants covering distinct sources, with no redundant or filler entries. Each tool earns its place by addressing a different context (editor text, file, tree, pre-commit, history, pre-push).

    Completeness4/5

    The surface covers the full scanning lifecycle (ad-hoc text, files, directories, staged changes, history, push range) plus detector introspection, which is strong. The only gap is that allowlist/detector configuration is read-only (list_patterns) with no way to add or modify rules via tools, though this is plausibly handled by external config files.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources