scopeguard-mcp
Related Servers
Alternatives to scopeguard-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables MCP clients to run deterministic AST safety audits, secret scanning, and sandboxed test execution on codebases, with human approval required before any remediation action.5MIT
- AlicenseAqualityCmaintenanceEnables policy-governed MCP interactions with deterministic authorization, tenant isolation, minimized PII exposure, and human approval gates for sensitive mutations, while producing structured audit events.3MIT
- AlicenseAqualityCmaintenanceEnables agents to audit and safeguard repositories by detecting dependency pinning issues, license compliance problems, hardcoded secrets, and dead code through MCP tools.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP servers to operate under autonomous security enforcement, including pre-deployment scanning, per-call authorization, runtime monitoring, incident containment, and comprehensive auditing.1MIT

Symbiotic MCP Serverofficial
AlicenseAqualityDmaintenanceEnables security analysis of code and infrastructure files via MCP, using Symbiotic CLI for scanning vulnerabilities.4MIT- FlicenseBqualityCmaintenanceEnables secure, policy-controlled operations on local git repositories through MCP, including bounded reads, context-checked patches, allowlisted tasks, and guarded git operations.10-
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: health for status, engagement lifecycle (create/revoke), scope checking, planning, header analysis, repository scanning, and audit operations (list/verify). Even the two audit tools are distinct in intent—listing versus verifying integrity. There is no meaningful overlap that would cause an agent to select the wrong tool.
Most tools follow a consistent verb_noun snake_case pattern (create_dry_run_engagement, revoke_engagement, check_scope, plan_assessment, analyze_headers, scan_repository, list_audit_events, verify_audit_chain). The only deviation is 'health', which is a noun instead of a verb_noun form, but this is a common exception for status endpoints and does not detract from overall readability.
With 9 tools, this server is well-scoped for its domain of security assessment scope management. Each tool addresses a distinct operation without redundancy, and the count feels neither thin nor bloated.
The tool surface covers engagement creation and revocation, scope checking, planning, analysis, scanning, and audit verification. However, there is no way to list existing engagements or retrieve engagement details, which creates a gap in the engagement lifecycle. An agent cannot easily determine what engagements are active or inspect a specific engagement's configuration, limiting practical management.