Whois MCP

Created By
dadepo9 months ago
A Model Context Protocol (MCP) server that provides LLMs with network information lookup tools through WHOIS and RIPE Database queries.
Overview

what is Whois MCP?

Whois MCP is a Model Context Protocol (MCP) server that provides Large Language Models (LLMs) with network information lookup tools through WHOIS and RIPE Database queries.

how to use Whois MCP?

To use Whois MCP, integrate it with a compatible MCP client like Claude Desktop by adding the server configuration to your client settings.

key features of Whois MCP?

  • whois_query: Query WHOIS servers for domains, IPs, and ASNs.
  • expand_as_set: Recursively expand AS-SETs into concrete ASN lists.
  • validate_route_object: Check IRR route/route6 object existence.
  • contact_card: Fetch abuse, admin, and technical contacts.

use cases of Whois MCP?

  1. Retrieving registration details for IP addresses.
  2. Listing member ASNs in a specific AS-SET.
  3. Validating the existence of route objects in IRR databases.
  4. Obtaining contact information for network-related inquiries.

FAQ from Whois MCP?

  • What is the primary focus of Whois MCP?

Whois MCP is optimized for RIPE NCC resources and databases, with plans to support other Regional Internet Registries.

  • How do I configure Whois MCP?

You can configure it by setting environment variables and adding the server configuration to your MCP client.

  • Is there a license for Whois MCP?

Yes, it is licensed under the MIT License.

Server Config

{
  "mcpServers": {
    "whois-mcp": {
      "command": "/path/to/bin/uvx",
      "args": [
        "--from",
        "git+https://github.com/dadepo/whois-mcp.git",
        "whois-mcp"
      ]
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
dadepo
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago