Skip to main content
Glama
doazvjettu

leakguard-mcp

by doazvjettu

Related Servers

Alternatives to leakguard-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables auditing and verification of algorithmic trading backtests from coding agents like Claude Code, Cursor, and Windsurf, including look-ahead bias detection, overfitting checks, and sealed audit proof verification.
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI models to perform static taint analysis on Python code, detecting security vulnerabilities by tracking data flows from sources to sinks.
      9
      AGPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Static analysis for vibe-coded apps. Flags security, reliability, performance, and AI quality issues in code generated by Cursor, v0, Bolt, and Copilot.
      575 npm
      15
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      AI-powered security scanner for Python projects and GitHub repositories. Detects vulnerabilities, secrets, and provides AI risk assessment.
      11
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Local-first backtesting engine with built-in overfitting detection (PBO, deflated Sharpe, bootstrap CI, walk-forward) and a native MCP server for AI agents to validate trading strategies.
      4
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct action: listing rules, explaining a single rule, scanning code from a string, scanning a single file, and scanning files by glob. There is no ambiguity; an agent can easily distinguish between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores. The verbs vary but are descriptive, and the nouns specify the target clearly. This pattern is predictable and easy to understand.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a linter. It provides rule introspection and scanning at three levels of granularity without unnecessary clutter, making the count appropriate for its purpose.

    Completeness4/5

    The server covers the core lifecycle: rule discovery (list_rules), rule understanding (explain_rule), and scanning (lint_code/file/paths). Minor gaps like rule configuration or suppression are absent, but the essential functionality is complete for standard usage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues