Onion-OSINT-MCP
Related Servers
Alternatives to Onion-OSINT-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access Tor hidden services and the dark web through tools for search, fetch, and analysis over Tor.20MIT
- AlicenseNot gradedqualityCmaintenanceEnables searching onion services through multiple search adapters and reading pages over Tor, with tools for fetching, status checks, link extraction, and Tor health plus content filtering and in-memory caches.MIT
- AlicenseAqualityCmaintenanceEnables AI agents and compatible MCP clients to fetch, search, and download web content—including .onion services—anonymously through the Tor network, using a fresh circuit per call and retrying when exit nodes are blocked.62MIT
- AlicenseAqualityCmaintenanceDark web & threat intelligence for AI agents. HIBP, ThreatFox, ransomware tracking, Tor .onion access, blockchain intel, exploit search, stealer logs, malware analysis — unified into a single MCP server.66305 npm530MIT
- FlicenseCqualityDmaintenanceEnables AI clients to scrape anti-bot-protected and JavaScript-rendered websites, search the web, pull Wayback snapshots, transcribe YouTube videos, parse remote PDFs/Office docs, and run OSINT/GEOINT reconnaissance across 25+ platforms with confidence scoring, all backed by local SQLite caching and an OpenAPI bridge.33-
- AlicenseNot gradedqualityDmaintenanceEnables secure access to Tor/onion services with content filtering and safety guardrails for AI assistants.8MIT
TDQS
Scored across 2 tools
The two tools target clearly different operations: search_onion_web queries an index (Ahmia/local SQLite) and returns mentions, while read_onion_page performs a direct HTTP GET against a specific .onion URL. Their distinct status vocabularies (local_only/connection_failed vs tls_error/timeout) reinforce the operational boundary, leaving no realistic path to misselection.
Both names follow the same snake_case verb_noun pattern (search_..., read_...) with a consistent 'onion' resource qualifier. No mixed conventions or vague verbs.
Two tools is on the thin side, but they map to the two essential primitives of onion OSINT (discover and retrieve). Still, a 2-tool surface sits at the borderline where an agent may need workarounds for anything beyond a single search-then-read loop.
Search plus passive fetch covers the core discover-then-read lifecycle of the stated OSINT purpose, with sensible error statuses. Minor gaps remain: no result pagination/limits handling surfaced as a tool, no bulk or follow-link extraction, and no way to record or export findings.