Skip to main content
Glama

ip-doctor 🩺

Live reputation, network type & abuse score for any IP or domain β€” from real DNS lookups, no API key.

ip-doctor is both:

  • an MCP server (npx -y ip-doctor-mcp) you add to Claude, Cursor or any agent, and

  • a pay-per-call HTTP API gated by x402 (USDC on Base) β€” no sign-up, no key.

Give it an IP address or a domain and get back a CLEAN / LOW_RISK / ELEVATED / HIGH_RISK verdict with a 0–100 risk score and explained findings.

Why an MCP server?

An LLM can reason about an IP, but it cannot run live DNS, DNSBL or reverse-DNS lookups by itself. ip-doctor does exactly that on demand β€” the moat is the live network access, not the reasoning.

Related MCP server: mcp-server-dns

What it returns

Signal

Source (key-less)

🌍 Geolocation (RIR country) + ASN + organisation + BGP prefix

Team Cymru DNS IP-to-ASN

🏷️ Network type β€” datacenter/hosting, VPN/proxy, Tor exit, mobile/carrier, residential ISP

deduced from ASN org + PTR + Tor list

πŸ” Reverse DNS (PTR)

node:dns reverse

🚫 DNS blocklist (DNSBL) membership

DroneBL, blocklist.de, s5h, SORBS, UCEPROTECT, Barracuda, Spamhaus ZEN

πŸ§… Tor exit node

Tor DNS exit list (dnsel.torproject.org)

πŸ“Š 0–100 abuse/risk score + verdict

derived from the above

Honesty: geolocation is the coarse RIR-allocation country, not city-level GeoIP. The network type is a deduction from org/PTR signals, not an authoritative paid label. Blocklist zones that don't answer from a public resolver are reported as inconclusive, never silently "clean".

Use it as an MCP server (free)

{
  "mcpServers": {
    "ip-doctor": { "command": "npx", "args": ["-y", "ip-doctor-mcp"] }
  }
}

Tools:

  • check_ip β€” { target: "8.8.8.8" | "example.com", deep?: boolean }

  • check_many β€” { targets: ["1.1.1.1", "evil.example", ...] }

Or connect over HTTP at POST /mcp (stateless JSON-RPC).

Use it as an HTTP API

Free tier (rate-limited, 40/h/IP):

GET https://ip-doctor.vercel.app/check?target=8.8.8.8
GET https://ip-doctor.vercel.app/check?target=example.com&deep=true
GET https://ip-doctor.vercel.app/check_many?targets=1.1.1.1,8.8.8.8,9.9.9.9

Pay-per-call (x402, $0.02 USDC on Base, DEEP tier β€” more blocklists + listing reasons, no rate limit):

GET https://ip-doctor.vercel.app/pro/check?target=<ip|domain>
GET https://ip-doctor.vercel.app/pro/check_many?targets=...

Your agent's x402-aware HTTP client pays automatically on the 402 challenge. The server holds no private key β€” payTo is a public receiving address only.

Typical uses

  • Vet inbound traffic / API callers (datacenter or Tor β†’ step-up auth).

  • Validate sign-ups & registrations (block known-abusive or proxy IPs).

  • Moderate user-supplied IPs/domains in a pipeline.

  • Enrich logs with ASN/org/type/blocklist context.

Local dev

npm install
npm run build
npm run test:engine     # live DNS smoke tests
npm run dev:http        # local HTTP server on :8080 (payments OFF by default unless env set)
npm run dev:mcp         # stdio MCP server

Notes

  • Read-only. No code is executed; nothing is written. All lookups are DNS/DNSBL/reverse-DNS.

  • Private/reserved addresses (RFC1918, loopback, CGNAT, link-local) are detected and skipped β€” no meaningless public lookups.

  • IPv6 is supported for ASN/PTR/geo; most DNSBLs are IPv4-only and are reported as not-applicable for IPv6.

MIT licensed. Source: https://github.com/Baneado98/ip-doctor

Available Tools

2 tools
check_ipA

Run a LIVE network & abuse reputation check on an IP address or a domain name. Performs real DNS / DNSBL / reverse-DNS lookups (something an LLM cannot do on its own) and returns: geolocation (RIR country) + ASN/organisation + BGP prefix, reverse DNS (PTR), a network-TYPE deduction (datacenter/hosting, VPN/proxy, Tor exit, mobile/carrier, or residential ISP), DNS blocklist (DNSBL) membership, Tor-exit status, and a 0–100 abuse/risk score with a CLEAN / LOW_RISK / ELEVATED / HIGH_RISK verdict and explained findings. Use this to vet inbound traffic, validate signups/registrations, decide whether to challenge a request, or moderate user-supplied IPs/domains. Pass deep=true for more blocklists and richer reasons.

Inputs: target (required), deep.

check_manyA

Run the live IP/domain reputation check on several targets at once (e.g. a list of IPs from your logs). Returns one concise verdict per target. Useful for batch-vetting traffic or a blocklist candidate set.

Inputs: targets (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: check_ip handles single targets while check_many handles batch processing. Descriptions explicitly differentiate the use cases.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern: 'check' + target type (ip or many). Simple and predictable.

    Tool Count3/5

    Only 2 tools for IP/domain reputation checking feels thin. While the core functionality is covered, the server would benefit from additional tools for advanced features like whitelist management or historical queries.

    Completeness4/5

    The tool set covers the primary use case of live reputation checking for single and multiple targets. Minor gaps exist (e.g., no tool for checking URLs or managing blocklists), but the domain is simple and adequately served.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      D
      quality
      D
      maintenance
      A comprehensive MCP server providing tools for IP, domain, email, and image-based open-source intelligence. It integrates services like Shodan, VirusTotal, and HaveIBeenPwned to facilitate advanced security research and data gathering.
      56
      108 npm
      ISC
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for DNS lookups, reverse DNS, WHOIS, and domain checks. Zero auth, zero config.
      5
      64 npm
      3
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server for domain availability checks, WHOIS lookups, and domain suggestions using RDAP and TCP port 43. It allows users to perform bulk checks and retrieve registration details across multiple TLDs without requiring an API key.
      28 npm
      -