Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

OnionLens Tor Tools

REMOTE · ONIONLENS.ORG

Tor address validation and retrieval fixtures, with disclosed research logging.

Available components

+4 this week 63 Trust /100

Last scanned (23 hours ago)

Scores higher than 44% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 74 tokens (~24/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 0.1.2 → 0.1.3 functional
  • 23 Oct 26 57

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://onionlens.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onionlens.org CN=WE1,O=Google Trust Services,C=US 22 Oct 2026 20 Jan 2027 ECDSA 256 ECDSA-SHA256 225163019b1df2030ed20254d7fc60e4
SANs: onionlens.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of onionlens.org. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
org. present 26974 8 Verified
onionlens.org. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
content-security-policy default-src 'self'; style-src 'self'; font-src 'self'; img-src 'self'; script-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'self'
x-content-type-options nosniff
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://onionlens.org/mcp Verified 200
http (plaintext) http://onionlens.org/mcp HTTPS enforced 301 https://onionlens.org/mcp
MCP tools · 3 exposed · ~74 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list_resources ~19

List primary-source Tor integration references and controlled retrieval fixtures.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

retrieval_fixture ~22

Return a deterministic UTF-8 retrieval fixture for transport and parsing checks.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

validate_onion_address ~33

Validate a Tor v3 address format, version and checksum without a network request.

NameTypeReqDescription
addressstringyes–

No output schema declared.

No examples provided.

Install

How do I install the OnionLens Tor Tools MCP server?

OnionLens Tor Tools is a hosted endpoint at https://onionlens.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · onionlens.org

# add to Claude Code
claude mcp add --transport http org-onionlens-tor-tools 'https://onionlens.org/mcp'
Common questions

What is the OnionLens Tor Tools MCP server?

OnionLens Tor Tools is an MCP server listed in the public MCP registry as org.onionlens/tor-tools. Tor address validation and retrieval fixtures, with disclosed research logging. This page covers its hosted endpoint (https://onionlens.org/mcp).

Is the OnionLens Tor Tools MCP server safe to use?

OnionLens Tor Tools scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the OnionLens Tor Tools MCP server expose?

OnionLens Tor Tools exposes 3 tools: validate_onion_address, list_resources, retrieval_fixture. Their descriptions and schemas cost roughly 74 tokens of context every time the server is loaded.

Does the OnionLens Tor Tools MCP server require authentication?

No. We connected to OnionLens Tor Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the OnionLens Tor Tools MCP server still maintained?

OnionLens Tor Tools is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.