darknet-mcp-server

tor_exit_nodes

Retrieve current Tor exit node IP addresses from the official Tor Project bulk exit list for network monitoring or filtering.

Instructions

Get a list of current Tor exit node IP addresses from the official Tor Project bulk exit list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tor_exit_nodes"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max IPs to return (default: all)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does convey that the data is current and from an official source, but does not mention output format, pagination, or network behavior. This is adequate but minimal.

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

Conciseness5/5

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

The description is a single sentence with a clear front-loaded action, containing zero filler. It effectively communicates the tool's core purpose in minimal words.

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?

This is a simple tool with one optional parameter and no output schema. The description states the return is a list of IP addresses, which covers the basic return value. It could elaborate on response format or limit behavior, but the schema handles that, making the description sufficient for its simplicity.

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?

The input schema already provides a full description of the 'limit' parameter (Max IPs to return, default: all), covering 100% of parameters. The description adds no additional parameter-specific meaning, which is acceptable given the schema coverage.

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

Purpose5/5

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

The description clearly states a specific action ('Get') and resource ('list of current Tor exit node IP addresses') with a distinct source ('official Tor Project bulk exit list'). This differentiates it from siblings like tor_exit_check or tor_exit_details.

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 description offers no guidance on when to use this tool versus the alternative Tor exit-related tools, nor any exclusions or prerequisites. It simply describes what it does without context.

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

Deploy Server