mcp-airlock
Related Servers
Alternatives to mcp-airlock
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA drop-in proxy that guards MCP servers with policy enforcement, secret redaction, prompt-injection screening, rug-pull detection, rate limiting, and audit logging.7 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceZero-dependency local proxy that wraps any MCP server to redact secrets, strip hidden-Unicode prompt injection, and block writes to protected paths like ~/.ssh and .env.4MIT
- AlicenseNot gradedqualityBmaintenanceSits in front of any MCP server to enforce allow/ask/block policies on tool calls, paths, shell commands, and network domains, with local approval prompts and an audit log.MIT
- FlicenseNot gradedqualityBmaintenanceA firewall proxy for any stdio MCP server: every tool call is checked against a restrict-only policy before it runs, with encoded-argument inspection, taint tracking so private data can't leave, tool pinning, and a write-ahead audit log.1-
- AlicenseNot gradedqualityCmaintenanceA transparent MCP stdio proxy that sits between an agent client and a real MCP server, intercepting tools/call requests to enforce runtime guardrails derived from the same YAML rules used for CI regression testing. It blocks forbidden, out-of-whitelist, looping, or non-idempotent tool invocations with JSON-RPC errors and writes every decision to an audit log.1MIT
- AlicenseBqualityCmaintenanceSecurity gateway that wraps any MCP server with per-tool policies, approval gates, and optional Ed25519-signed decision receipts. Shadow mode logs every tool call without blocking; enforce mode applies block, rate-limit, and minimum-tier rules. Receipts are independently verifiable offline with no accounts needed.52,368 npm11MIT
TDQS
Scored across 17 tools
Most tools map to a distinct MCP protocol feature, but several pairs overlap in intent: trigger-log-messages vs toggle-simulated-logging, trigger-resource-update vs toggle-subscriber-updates, and get-resource-links vs get-resource-reference. The descriptions do explain the deprecated/demo distinction, and airlock_report is a completely different (governance/audit) purpose bolted onto a protocol-demo surface, which muddies what the server is for.
Nearly everything follows a kebab-case verb_noun or get-* pattern (get-env, get-sum, trigger-list-changed, toggle-subscriber-updates, gzip-file-as-resource). The only deviation is airlock_report using snake_case, which is a minor but visible inconsistency.
17 tools sits at the heavy end for a demo/protocol-conformance server, and two of them (toggle-simulated-logging, toggle-subscriber-updates) are explicitly deprecated duplicates of trigger-* equivalents. Each remaining tool does demonstrate a separate capability, so it is defensible but not tight.
Coverage of tools/annotations/structured content/resources/logging/notifications is broad, but there is no prompt demo, no sampling or elicitation demo, and no tool to actually read or list resources despite the resource-link and resource-update tools. For a server whose apparent purpose is exercising the full MCP surface, these are notable gaps.