AgentBreakWatch MCP Server
Related Servers
Alternatives to AgentBreakWatch MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables developers to audit MCP tool schemas and annotations, multi-agent delegation graphs, multi-turn behavioral drift, bias, and token/cost telemetry from inside their IDE or CLI, and to generate EU AI Act, NIST AI RMF, and SOC 2 compliance dossiers. It also provides sub-250ms inline circuit-breaking, adversarial IPIP-NEO-120 persona cohorts, stress testing, and chaos fault injection.121,313 npm1Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP-compliant clients to audit software bills of materials and quarantine supply-chain malicious package dependencies using Snyk and Socket.dev.8-
- AlicenseNot gradedqualityDmaintenanceEnables 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.MIT
- AlicenseAqualityBmaintenanceEnables AI agents and users to check npm, PyPI, and crates.io packages before installation for hallucinated names, malware, exact-version CVEs, and signs of compromised releases, with MCP tools for package checks and lockfile audits.2Apache 2.0
- AlicenseBqualityBmaintenanceEnables 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.321MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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
TDQS
Scored across 4 tools
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.
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.
Four tools is well-scoped for a focused dependency/version-auditing service. Each tool covers a distinct query surface with no redundancy or filler.
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.