Skip to main content
Glama
Onion-OSINT-MCP

Onion-OSINT-MCP

by jotatito05

search_onion_web

Search public .onion forums, documentation, and mentions through a SOCKS5h Tor proxy or local SQLite index, with optional recency and result filters.

Instructions

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'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_onion_web"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoFiltro opcional de antigüedad máxima en días (ej. 7 o 30)
queryYesTérmino de búsqueda, actor de amenaza, CVE o IoC a consultar en la red Tor (.onion)
local_onlyNoSi es true, consulta únicamente la base de datos SQLite indexada local sin conectar a Tor
max_resultsNoNúmero máximo de resultados a devolver (por defecto 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does a solid job: it names the SOCKS5h proxy path, the two data sources (Ahmia .onion + local indexed SQLite), and explains the 'status' field values ('completed', 'local_only', 'connection_failed'). It still omits rate-limit, failure/fallback mechanics, and result shape, keeping it below the top score.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences that are front-loaded with the core purpose before the technical detail. No wasted filler, though it packs proxy and status details into a single long sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter search tool without an output schema, it covers purpose, sourcing, network mode and status semantics adequately. The main gap is the absence of result-format detail and explicit routing against the read_onion_page sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all four parameters (query, days, local_only, max_results) are already documented in the schema. The description adds only indirect context via the source discussion (Ahmia + local DB relating to local_only), so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Busca') and a well-defined resource: public information, forums, documentation and mentions on Tor .onion services, plus the sourcing mechanism (Ahmia + local SQLite). An agent can distinguish this search operation from the sibling read_onion_page, though the description never names the sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The search purpose implicitly suggests when to use this tool, but there is no explicit guidance on when to choose it over read_onion_page or any stated exclusions. It lacks an 'use this when…/not when…' framing that would help selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools