Skip to main content
Glama
joeyg6393

AgentBreakWatch MCP Server

by joeyg6393
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to AgentBreakWatch MCP Server

No user-submitted related servers found.

    Related Servers

    • shipcheck-mcp

      noureldeensalama
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI agents to scan code for leaked secrets, copyleft licenses, unprotected routes, missing privacy policies, and risky card handling before committing or shipping.
      103 npm
      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

    • agent-sec-mcp

      sudo-ai-git
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables authorized security auditing of AI-agent supply chains and agent-facing surfaces: deterministic local skill-bundle audits against eight attack patterns, secrets scanning, and scope-gated read-only recon of agent endpoints and MCP surfaces.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools target distinct operations: whole-config audit, single-package lookup, archived-package migration matrix, and telemetry-ranked listing. The only real overlap is check_stack_drift vs get_package_stability, but the description explicitly disambiguates when to prefer each. An agent can reliably pick the right tool.

    Naming Consistency5/5

    All names use consistent snake_case with clear verb prefixes (check_, get_, list_) followed by specific nouns. No mixed conventions or vague verbs; patterns are predictable across the set.

    Tool Count5/5

    Four tools is well-scoped for a focused dependency/version-auditing service. Each tool covers a distinct query surface with no redundancy or filler.

    Completeness4/5

    Core lifecycle is covered: discovery (list_volatile_packages), single-package inspection, stack audit, and archived-package migration. Minor gaps exist—no free-text search across the 256-package index or bulk/batch audit of multiple packages—but agents can work around these via single-package lookups.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources