Skip to main content
Glama
tarhou

chokepoint-finder-mcp

by tarhou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to chokepoint-finder-mcp

No user-submitted related servers found.

    Related Servers

    • remediation-flight-recorder

      SweetKenneth
      A
      license
      A
      quality
      C
      maintenance
      Enables security remediation as one auditable transaction: freezing pre-change exposure, computing blast radius, gating on policy and approval, binding execution receipts, verifying post-state, and rolling back on failure, all sealed in a SHA-256 evidence chain.
      6
      MIT

    • PEA MCP Server

      haothtrteen
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to analyze software artifacts through 35 tools covering read-only reconnaissance, secret/string/symbol scanning, native and Dart AOT structure checks, exposure tiering, protection planning, attack-simulation design, and an append-only evidence ledger with mechanical verified gates that treat unresolved unknowns as blocking. Gated execution tools apply reviewed transforms only to a managed copy inside an authorized workspace, with one-time approval tokens, independent verification, before/after diffs, and rollback.
      MIT
    • Break Anything by EnkiHQ

      Break Anythingofficial

      EnkiHQ
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects AI coding agents to security tooling so they can inspect authorized code, dependencies, container images, and infrastructure, confirm exploitability, and receive evidence-backed remediation plans.
      825 npm
      MIT

    • dsh-vulnerability-remediation

      dongsheng123132
      A
      license
      Not graded
      quality
      C
      maintenance
      Offers proof-only tools to inspect and verify remediation closure receipts, deterministically confirming asset coverage, fixed artifact deployment, rescanning, deadline compliance, and zero-residual closure without executing scans or touching live systems.
      MIT

    • MCP SSDLC Security Toolkit

      vuongdat67
      A
      license
      Not graded
      quality
      C
      maintenance
      Automates 85-95% of the Secure Software Development Lifecycle (SSDLC) planning phase through multi-role AI orchestration, enabling business analysis, threat modeling, test strategy design, and security code review.
      MIT

    • Sentinela

      alissonandrade1
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to run deterministic, fully local static security and compliance audits of code, configurations, and dependencies through 32 MCP tools covering 24 vulnerability categories. It also detects the project stack, generates risk reports and checklists, suggests stack-aware remediations, and re-validates fixes to confirm vulnerabilities were eliminated.
      32
      1
      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.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct roles in the workflow, but some pairs like chokepoint_payload and chokepoint_plan (both produce outputs for a chokepoint) could be confused. Similarly, chokepoint_supply_evidence and chokepoint_preflight are closely related input/evaluation steps.

    Naming Consistency4/5

    All tools share the consistent 'chokepoint_' prefix, but the second part mixes verbs (ingest, setup, rank, verify) with nouns (payload, plan) and verb phrases (mark_executed, supply_evidence). This is readable but not perfectly uniform.

    Tool Count5/5

    10 tools is well within the ideal 3-15 range. Each tool maps to a distinct phase in the chokepoint-finding and remediation workflow, and none feel redundant or unnecessary.

    Completeness5/5

    The tool set covers the full lifecycle from setup and ingest to ranking, evidence gating, plan/payload generation, execution marking, and verification. The design intentionally leaves out direct execution, which is documented and consistent with the server's zero-trust posture.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources