Skip to main content
Glama
Heretek-RE

re-leak-scan

by Heretek-RE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to re-leak-scan

No user-submitted related servers found.

    Related Servers

    • mcp-secret-sentinel

      AleBrito124356
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that scans code for exposed secrets (API keys, tokens, private keys, high-entropy strings) with placeholder-aware allowlisting and fully redacted reports, enabling agents to detect leaks before committing.
      3
      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
      -

    • secretscanner

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

    • secscan-mcp

      openjkai
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Cursor that scans codebases for security issues including hardcoded secrets, SAST, vulnerable dependencies, and IaC misconfigurations.
      7
      MIT

    • mcp-tenant-isolation

      subodhkc
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for static analysis of multi-tenant SaaS and MCP server code, catching cross-tenant data leakage. Provides tools to scan code, list/explain rules, and manage suppressions.
      5,009 npm
      4
      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.3/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools are distinct: check_leak_scan for status, extract_strings for raw extraction, find_secrets for catalog detection, scan as a wrapper, and verification tools for URLs/DSNs. However, find_secrets and scan overlap significantly, as scan is essentially a convenience wrapper for find_secrets with all detectors.

    Naming Consistency4/5

    Tools predominantly use verb_noun snake_case (e.g., extract_strings, verify_confluence_url), but 'scan' is a bare verb, breaking the pattern. This minor inconsistency does not hinder readability.

    Tool Count5/5

    With 6 tools, the set is well-scoped for a leak scanning server, covering status checking, string extraction, detection, full pipeline, and specific verifications. No unnecessary tools, and the count is appropriate for the domain.

    Completeness4/5

    The tool surface covers the core workflow: status check, extraction, detection, and verification for two common services. Minor gaps exist, such as pattern catalog management (listing/updating) and support for more service types, but essential operations are present.

    Maintenance

    ActivityStale
    ResponsivenessSyncing

    Resources