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

darknet-mcp-server

by badchars
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

otx_ip

Retrieve threat intelligence for any IPv4 address, including reputation, associated pulses, country, and ASN, using AlienVault OTX data.

Instructions

Look up threat intelligence for an IP address via AlienVault OTX. Returns pulse info, reputation, country, ASN.

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": {
      "ip": "<ip>"
    },
    "name": "otx_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesIPv4 address to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 full transparency burden. It discloses the return fields (pulse info, reputation, country, ASN) but does not mention authentication, rate limits, or other operational caveats. For a simple read-only lookup, this is adequate but not comprehensive.

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, tight sentence of 19 words, front-loading the action and source, then immediately listing return data. Every word earns its place, with no filler or redundancy.

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

Completeness3/5

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

Given the tool's simplicity (one parameter, no output schema), the description covers the basic purpose and return content. However, it lacks guidance on when to choose this tool over alternative IP intelligence sources (AbuseIPDB, GreyNoise, etc.), which is a notable gap in the broader context.

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 schema already provides 100% coverage for the single 'ip' parameter, including its description ('IPv4 address to look up'). The tool description adds no additional parameter semantics beyond what the schema states, so baseline 3 applies.

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 tool performs an IP address lookup via AlienVault OTX, using a specific verb ('look up') and resource. It also enumerates return values (pulse info, reputation, country, ASN), distinguishing it from sibling OTX tools for other IOC types.

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

Usage Guidelines4/5

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

The description provides clear context: this tool is for IP address threat intelligence. It does not explicitly mention alternatives or exclusion criteria, but the context is specific enough for an agent to recognize when IP lookup is intended.

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