Skip to main content
Glama
Sign In
darknet-mcp-server

darknet-mcp-server

by badchars
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

intelx_search

Search IntelligenceX for leaked data and dark web content. Returns a search ID for result retrieval.

Instructions

Initiate a search on IntelligenceX for leaked data, dark web content, and more. Returns a search ID to retrieve results. Requires INTELX_API_KEY.

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": {
      "term": "<term>"
    },
    "name": "intelx_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesSearch term (email, domain, IP, Bitcoin address, etc.)
max_resultsNoMax results (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full transparency burden. It discloses the API key requirement and that the result is a search ID, not direct data. However, it does not describe rate limits, expiration of the search ID, or any side effects beyond initiating a search, leaving some behavioral uncertainty.

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 two concise sentences, front-loaded with the action verb ('Initiate'). It includes essential information (purpose, return behavior, authentication) without extraneous detail, making it easy to parse.

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 simple two-parameter tool with no output schema, the description covers the primary action, return type, and prerequisite. It could be slightly more explicit about the need to use a subsequent endpoint to fetch results, but 'Returns a search ID to retrieve results' conveys the asynchronous workflow adequately.

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% with both term and max_results described. The description adds that the search covers 'leaked data, dark web content, and more,' which contextualizes the term parameter but provides no additional syntax or semantics beyond the schema. Baseline 3 is appropriate.

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 the action: initiate a search on IntelligenceX. It specifies the scope (leaked data, dark web content) and the key output (a search ID). This distinguishes it from sibling tools like intelx_search_results, which retrieve results rather than initiate searches.

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 the tool is the first step in a two-step process by noting it returns a search ID to retrieve results, but it does not explicitly name the companion endpoint or state when to use this tool over alternatives. It mentions the API key requirement as a prerequisite, but no explicit exclusions or alternative comparisons.

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