WHOIS MCP Server

Related Servers

Alternatives to WHOIS MCP Server

No user-submitted related servers found.

Related Servers

Whois MCP
Search Web Scraping
modelcontextprotocol-servers
A
license
B
quality
D
maintenance
Enables AI agents to perform WHOIS lookups to retrieve domain registration details, including ownership, registration dates, and availability status without requiring browser searches.
Updated 2 years ago (2025-03-07 10:13 UTC)
4
15 npm
21
MIT
mcp-ripe-stat
Networking & Infrastructure Location Services Open Data
pipeworx-io
A
license
Not graded
quality
C
maintenance
Provides IP, ASN, and BGP routing data from RIPE Stat API, enabling whois lookups, network info, AS overview, BGP state, abuse contacts, and geolocation queries.
Updated 2 days ago (2026-09-18 23:23 UTC)
1 npm
MIT
DomainDetails MCP Server
Networking & Infrastructure Search
simplebytes-com
A
license
A
quality
F
maintenance
Provides comprehensive domain research tools including RDAP, WHOIS, and DNS lookup capabilities, with automatic fallback and support for 50+ TLDs.
Updated 10 months ago (2025-11-28 10:33 UTC)
1
10 npm
1
MIT
domain-whois-mcp
Networking & Infrastructure Open Data
kemalabuteliyte
A
license
A
quality
D
maintenance
Enables AI agents to perform real-time WHOIS and RDAP lookups, domain availability checks, and TLD infrastructure exploration using native protocols without API keys.
Updated 5 months ago (2026-04-17 17:23 UTC)
8
MIT
whois
Networking & Infrastructure Open Data
KincaidYang
A
license
Not graded
quality
A
maintenance
Query WHOIS/RDAP information for domains, IP addresses, CIDR prefixes and ASNs. Results are normalized to RDAP-style (RFC 9083) JSON. Public instance of the open-source KincaidYang/whois server, which can also be self-hosted.
Updated 5 days ago (2026-09-16 02:27 UTC)
64
MIT
Domain Tools (WHOIS + DNS)
Search Web Scraping
patrickdappollonio
A
license
Not graded
quality
C
maintenance
Perform DNS lookups, WHOIS queries, connectivity testing, TLS certificate analysis, HTTP endpoint monitoring, and hostname resolution, all from your trusty AI.
Updated 3 months ago (2026-06-11 00:33 UTC)
10
MIT

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.6/5.0

Scored 2026-04-18 08:35 across 14 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with minimal overlap. The server provides contact cards, raw WHOIS queries, route validation, and AS-SET expansion for each RIR, and descriptions explicitly differentiate them (e.g., 'DO NOT use for contact information - use X_contact_card'). This prevents misselection and ensures agents can easily choose the correct tool for specific tasks like incident response or network analysis.

Naming Consistency5/5

Tool names follow a highly consistent pattern: all use snake_case with a structure of 'rir_operation_object' (e.g., arin_contact_card, ripe_validate_route_object). This predictability makes it easy for agents to understand and navigate the toolset, as the naming convention clearly indicates the RIR, operation type, and target resource across all 14 tools.

Tool Count5/5

With 14 tools, the count is well-scoped for a WHOIS server covering multiple RIRs. Each tool earns its place by providing specialized functions (contact retrieval, raw queries, route validation, AS-SET expansion) across five RIRs, ensuring comprehensive coverage without redundancy. This aligns with the server's purpose of detailed network and contact information lookup.

Completeness5/5

The toolset offers complete coverage for WHOIS-related tasks across all major RIRs. It includes contact retrieval, raw data queries, route validation, and AS-SET expansion, addressing key use cases like incident response, network troubleshooting, and compliance. There are no obvious gaps; agents can perform full CRUD-like operations (e.g., query, validate, expand) for each region without dead ends.