io.github.crunchtools/airlock
OfficialRelated Servers
Alternatives to io.github.crunchtools/airlock
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceSecurely fetches web content, extracts links and metadata, and downloads files through a sandboxed MCP server without JavaScript execution. Includes prompt-injection detection and comprehensive HTML sanitization for safe web data retrieval.2MIT
- AlicenseAqualityAmaintenanceSafe, self-hosted MCP server for web grounding that fetches live pages through a stealth-patched Chrome and returns clean Markdown with provenance, preventing SSRF and blocks.41MIT
- AlicenseAqualityCmaintenanceAn MCP server that fetches web pages and extracts clean, AI-friendly Markdown content using Mozilla Readability. It provides secure web access for LLMs with built-in SSRF protection and automated content cleaning for improved context retrieval and summarization.190 npmMIT
- FlicenseNot gradedqualityCmaintenanceA read-only MCP server that fetches hard-to-scrape web pages via an anti-detection browser and returns clean, token-efficient markdown. It exposes a single fetch tool that converts pages to markdown without requiring approval prompts.-
- AlicenseAqualityCmaintenanceFetch URLs and return clean, LLM-ready markdown with metadata and layered prompt injection defense. Configurable timeouts, word limits, JS rendering, and link extraction. All-in-one MCP server + CLI.11MIT
- FlicenseNot gradedqualityFmaintenanceAn MCP server for prompt injection boundary enforcement that scans URL content using a tiered LLM model strategy.-
TDQS
Scored across 9 tools
The five judgment tools (content, dir, read, fetch, search) share the same 'judge through all three layers' mechanism but are cleanly separated by input source (inline text, directory, file, URL, web search). The admin tools (cache_flush, quarantine_stats, reconnect_backend, reload_profiles) each have a distinct operational purpose, though reconnect_backend and cache_flush overlap slightly in effect, which the description explicitly clarifies.
Every tool uses the identical snake_case pattern with a consistent '_tool' suffix (content_tool, dir_tool, fetch_tool, read_tool, search_tool, cache_flush_tool, etc.). No mixing of camelCase or verb styles; the convention is uniform throughout.
Nine tools is well within the ideal 3-15 range and each earns its place: five content-judgment entry points plus four gateway-administration operations. No redundant or filler tools.
The surface covers content judgment across all major input sources plus the key operational tasks (cache flush, backend recovery, profile reload, quarantine stats). Minor gaps exist, such as no explicit audit-log or detections-listing tool and no blocklist-editing tool, but agents can work around these via quarantine_stats and reload_profiles.