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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago