Skip to main content
Glama
Onion-OSINT-MCP

Onion-OSINT-MCP

by jotatito05

read_onion_page

Fetch .onion pages through Tor's SOCKS5h proxy, strip scripts and credential forms for safer OSINT collection, and return clear statuses for TLS, timeout, and connection failures.

Instructions

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

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": {
      "url": "<url>"
    },
    "name": "read_onion_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL completa http(s)://<v3_address>.onion/...
max_charsNoLongitud máxima del texto extraído (por defecto 8000)
verify_tlsNoPor defecto true (reporta 'tls_error' ante certificados autofirmados). Si es false, permite leer servicios .onion con certificado HTTPS autofirmado.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 well: it discloses the transport (SOCKS5h via Tor), the method (GET), the sanitization behavior (strips scripts and credential forms), and the status taxonomy including tls_error for self-signed certificates. What it omits are rate limits, redirect/robots handling, and whether any content is logged, which keeps it from a 5.

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 with the core operation stated first and the status taxonomy second; nothing is padded. The parenthetical annotations are efficient, though the sentence is long and slightly overloaded.

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 3-parameter tool with no output schema and no annotations, the description supplies the most important return-value context by enumerating the status values. It does not describe the shape of the extracted text field or how it is returned, which is the main remaining gap.

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 description coverage is 100%, so all three parameters are already documented, and the baseline is 3. The description adds some meaning by linking tls_error to the self-signed-certificate case, which clarifies the intent of verify_tls, but it says nothing about max_chars or the interaction between the two optional parameters.

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?

The description states a specific verb and resource — a passive HTTP GET of a .onion URL routed through Tor's SOCKS5h proxy — so the agent knows exactly what class of operation this is. It does not name or contrast with the only sibling, search_onion_web, so differentiation from siblings is left implicit.

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

Usage Guidelines3/5

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

The description implies when to use it (fetching a known .onion URL passively for OSINT) by describing the read semantics and the security stripping of scripts and credential forms. However, it gives no explicit when-not guidance, no prerequisites, and never mentions when to prefer search_onion_web instead.

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