leakguard-mcp
Related Servers
Alternatives to leakguard-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables 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.3MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI models to perform static taint analysis on Python code, detecting security vulnerabilities by tracking data flows from sources to sinks.9AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceStatic analysis for vibe-coded apps. Flags security, reliability, performance, and AI quality issues in code generated by Cursor, v0, Bolt, and Copilot.575 npm15MIT
- AlicenseNot gradedqualityCmaintenanceAI-powered security scanner for Python projects and GitHub repositories. Detects vulnerabilities, secrets, and provides AI risk assessment.11MIT
- AlicenseBqualityCmaintenanceAudits local datasets and ML training code for target, temporal, and entity leakage, PII exposure, and invalid evaluation design, returning structured evidence and pass/review/block verdicts before model training.4MIT
- AlicenseNot gradedqualityCmaintenanceLocal-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.4Apache 2.0
TDQS
Scored across 5 tools
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.
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.
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.
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.