Onion-OSINT-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOR_EXE_PATH | No | Ruta explícita al ejecutable tor / tor.exe si no está en PATH. | |
| TOR_PROXY_URL | No | URL completa del proxy SOCKS5h externo (ej. socks5h://127.0.0.1:9050). | |
| ONION_INDEX_DB | No | Ruta del archivo SQLite para el índice local. | |
| TOR_SOCKS_HOST | No | Host del proxy SOCKS5 de Tor. | 127.0.0.1 |
| TOR_SOCKS_PORT | No | Puerto SOCKS5 de Tor. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_onion_webA | Busca información pública, foros, documentación o menciones en servicios ocultos (.onion) de la red Tor a través de proxy SOCKS5h (Ahmia .onion + base de datos indexada local SQLite). Distingue en 'status' entre 'completed', 'local_only' y 'connection_failed'. |
| read_onion_pageA | Realiza una lectura pasiva (HTTP GET) de una URL .onion a través del proxy SOCKS5h de Tor, eliminando scripts y formularios de credenciales por seguridad OSINT. Distingue en 'status' entre 'completed', 'tls_error' (certificado autofirmado), 'timeout' y 'connection_failed'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.