{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-whois-mcp","slug":"whois-mcp","name":"Whois MCP","type":"mcp","url":"https://github.com/bharathvaj-ganesan/whois-mcp","page_url":"https://unfragile.ai/whois-mcp","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-whois-mcp__cap_0","uri":"capability://tool.use.integration.domain.whois.lookup.with.registrar.parsing","name":"domain-whois-lookup-with-registrar-parsing","description":"Performs WHOIS lookups against domain names by querying authoritative WHOIS servers and parsing structured registrar responses to extract registration details, expiration dates, nameservers, and registrant information. Implements server-side WHOIS protocol communication (RFC 3912) with automatic fallback to public WHOIS gateways when direct server queries fail, returning normalized JSON output compatible with MCP tool schemas.","intents":["Check domain registration status and expiration dates programmatically","Extract nameserver information for a domain to verify DNS configuration","Retrieve registrant contact details and registrar information for domain ownership verification","Bulk query domain WHOIS data for security audits or domain portfolio management"],"best_for":["Security researchers performing domain reconnaissance","DevOps engineers automating DNS and domain infrastructure audits","MCP client applications needing domain metadata enrichment","Teams building domain monitoring or expiration alert systems"],"limitations":["Rate-limited by WHOIS servers (typically 1-5 queries per second per IP); bulk operations may require delays between requests","Registrar-specific response formats require custom parsing logic; some registrars return obfuscated or redacted data due to GDPR/privacy policies","No caching layer built-in; repeated queries for same domain hit WHOIS servers each time, increasing latency","Timeout handling depends on WHOIS server responsiveness; some servers may take 5-10 seconds to respond"],"requires":["Network connectivity to public WHOIS servers (port 43)","MCP client compatible with tool-use-integration protocol","Valid domain name in standard format (e.g., example.com)"],"input_types":["text (domain name string)"],"output_types":["structured JSON (registrar, expiration date, nameservers, registrant info)"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-whois-mcp__cap_1","uri":"capability://tool.use.integration.ip.address.whois.lookup.with.asn.resolution","name":"ip-address-whois-lookup-with-asn-resolution","description":"Performs WHOIS lookups against IPv4 and IPv6 addresses by querying Regional Internet Registries (RIRs: ARIN, RIPE, APNIC, LACNIC, AFRINIC) and extracting autonomous system number (ASN), network range, organization ownership, and geolocation hints. Implements automatic RIR selection based on IP address space allocation, with fallback to secondary WHOIS servers when primary RIR is unreachable.","intents":["Identify the organization and ASN responsible for a given IP address","Determine network CIDR blocks and address space allocation for IP ranges","Perform reverse IP lookups to find associated domain names and hosting providers","Validate IP ownership during security investigations or threat intelligence workflows"],"best_for":["Security operations teams performing IP-based threat intelligence","Network engineers auditing IP space allocation and ownership","MCP agents building automated incident response workflows","Developers building IP geolocation or ASN enrichment pipelines"],"limitations":["RIR response times vary significantly (ARIN typically fast, APNIC may be slower); queries can take 2-10 seconds","IPv6 WHOIS data is less complete than IPv4; some RIRs have sparse IPv6 registrations","Geolocation hints from WHOIS are approximate and should not be used for precise location determination","Some IP ranges are reserved or private (RFC 1918, link-local) and will not return meaningful WHOIS data"],"requires":["Network connectivity to RIR WHOIS servers (port 43)","Valid IPv4 or IPv6 address in standard notation","MCP client compatible with tool-use-integration protocol"],"input_types":["text (IPv4 or IPv6 address string)"],"output_types":["structured JSON (ASN, organization, network range, RIR, abuse contact)"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-whois-mcp__cap_2","uri":"capability://tool.use.integration.asn.whois.lookup.with.network.enumeration","name":"asn-whois-lookup-with-network-enumeration","description":"Performs WHOIS lookups against Autonomous System Numbers (ASNs) by querying RIRs and extracting organization details, network prefixes, routing policy information, and abuse contacts. Implements ASN-to-network mapping to enumerate all IP ranges announced by a given AS, supporting both IPv4 and IPv6 prefix queries with optional filtering by address family.","intents":["Enumerate all IP networks and prefixes announced by a specific autonomous system","Identify the organization operating a given ASN and retrieve abuse contact information","Map ASN to organization for threat intelligence and network reconnaissance","Validate BGP routing announcements against WHOIS-registered network prefixes"],"best_for":["Network security teams performing BGP hijacking detection and validation","Threat intelligence analysts mapping infrastructure ownership to organizations","MCP agents automating network reconnaissance workflows","ISP and hosting provider teams managing multi-AS infrastructure"],"limitations":["ASN WHOIS data does not include real-time BGP routing state; registered prefixes may differ from actively announced routes","Large ASNs (e.g., major ISPs) may have hundreds of registered prefixes, causing response payload to be large and queries to be slow","Some ASNs are legacy or deprecated and may have incomplete or outdated WHOIS records","Private ASNs (64512-65534) are not globally routable and have limited WHOIS data availability"],"requires":["Network connectivity to RIR WHOIS servers (port 43)","Valid ASN in numeric format (e.g., 15169 for Google)","MCP client compatible with tool-use-integration protocol"],"input_types":["text (ASN number as string or integer)"],"output_types":["structured JSON (organization, network prefixes, routing policy, abuse contact)"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-whois-mcp__cap_3","uri":"capability://tool.use.integration.tld.whois.lookup.with.registry.metadata","name":"tld-whois-lookup-with-registry-metadata","description":"Performs WHOIS lookups against top-level domains (TLDs) by querying the IANA WHOIS server and registry-specific WHOIS servers, extracting registry operator information, nameserver details, DNSSEC configuration, and registry contact information. Implements TLD-to-registry mapping with automatic fallback to IANA when registry-specific servers are unavailable.","intents":["Retrieve registry operator and administrative contact for a given TLD","Verify DNSSEC configuration and nameserver delegation for a TLD","Identify registry-specific policies and technical contacts for domain registration","Validate TLD existence and retrieve registry metadata for DNS infrastructure audits"],"best_for":["DNS administrators managing TLD-level infrastructure and DNSSEC","Domain registrars and registry operators automating TLD metadata retrieval","Security researchers auditing TLD-level DNS configuration","MCP agents building DNS infrastructure validation workflows"],"limitations":["TLD WHOIS responses are less standardized than domain WHOIS; registry-specific formats require custom parsing","Some TLDs (especially country-code TLDs) have restricted WHOIS access or require authentication","DNSSEC data in WHOIS is often incomplete; authoritative DNSSEC validation requires querying DNS directly","TLD WHOIS data changes infrequently; caching is recommended to avoid unnecessary queries"],"requires":["Network connectivity to IANA and registry WHOIS servers (port 43)","Valid TLD in standard format (e.g., .com, .org, .co.uk)","MCP client compatible with tool-use-integration protocol"],"input_types":["text (TLD string, with or without leading dot)"],"output_types":["structured JSON (registry operator, nameservers, DNSSEC, administrative contact)"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-whois-mcp__cap_4","uri":"capability://tool.use.integration.mcp.tool.schema.based.whois.integration","name":"mcp-tool-schema-based-whois-integration","description":"Exposes WHOIS lookup capabilities as standardized MCP tools with JSON schema definitions, allowing Claude and other MCP clients to invoke domain, IP, ASN, and TLD lookups through natural language requests. Implements tool parameter validation, error handling with user-friendly messages, and response formatting compatible with Claude's tool-use protocol, enabling seamless integration into multi-step agent workflows.","intents":["Enable Claude to perform WHOIS lookups as part of multi-step security investigation workflows","Allow MCP clients to call WHOIS tools with natural language without manual API construction","Integrate WHOIS data enrichment into automated incident response or threat intelligence pipelines","Build Claude-powered agents that combine WHOIS lookups with other tools for domain/IP reconnaissance"],"best_for":["Developers building Claude-powered security agents and incident response tools","Teams integrating WHOIS data into multi-tool MCP workflows","Organizations automating threat intelligence and domain reconnaissance","MCP client developers needing standardized WHOIS tool definitions"],"limitations":["Tool schema validation adds ~50-100ms overhead per request for parameter checking","Error messages from WHOIS servers are passed through with minimal sanitization; clients must handle WHOIS-specific error formats","No built-in rate limiting or request queuing; high-volume agent workflows may hit WHOIS server rate limits","Tool responses are JSON-serialized; very large responses (e.g., ASNs with hundreds of prefixes) may exceed MCP message size limits"],"requires":["MCP client compatible with tool-use-integration (Claude, other LLMs with MCP support)","MCP server runtime (Node.js, Python, or other supported language)","Network connectivity to WHOIS servers from MCP server environment"],"input_types":["natural language (Claude prompt)","structured JSON (MCP tool parameters)"],"output_types":["structured JSON (MCP tool response)","natural language (Claude interpretation of WHOIS data)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":24,"verified":false,"data_access_risk":"moderate","permissions":["Network connectivity to public WHOIS servers (port 43)","MCP client compatible with tool-use-integration protocol","Valid domain name in standard format (e.g., example.com)","Network connectivity to RIR WHOIS servers (port 43)","Valid IPv4 or IPv6 address in standard notation","Valid ASN in numeric format (e.g., 15169 for Google)","Network connectivity to IANA and registry WHOIS servers (port 43)","Valid TLD in standard format (e.g., .com, .org, .co.uk)","MCP client compatible with tool-use-integration (Claude, other LLMs with MCP support)","MCP server runtime (Node.js, Python, or other supported language)"],"failure_modes":["Rate-limited by WHOIS servers (typically 1-5 queries per second per IP); bulk operations may require delays between requests","Registrar-specific response formats require custom parsing logic; some registrars return obfuscated or redacted data due to GDPR/privacy policies","No caching layer built-in; repeated queries for same domain hit WHOIS servers each time, increasing latency","Timeout handling depends on WHOIS server responsiveness; some servers may take 5-10 seconds to respond","RIR response times vary significantly (ARIN typically fast, APNIC may be slower); queries can take 2-10 seconds","IPv6 WHOIS data is less complete than IPv4; some RIRs have sparse IPv6 registrations","Geolocation hints from WHOIS are approximate and should not be used for precise location determination","Some IP ranges are reserved or private (RFC 1918, link-local) and will not return meaningful WHOIS data","ASN WHOIS data does not include real-time BGP routing state; registered prefixes may differ from actively announced routes","Large ASNs (e.g., major ISPs) may have hundreds of registered prefixes, causing response payload to be large and queries to be slow","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.2,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:04.689Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=whois-mcp","compare_url":"https://unfragile.ai/compare?artifact=whois-mcp"}},"signature":"3Pq0QgOxhB2EmvdSI6yGzR2l+cua1R+hhP39dPeIDDEekn1/4xPqo54H95JLihHDkUiC45esjW8X3Vlf8EX6Dg==","signedAt":"2026-06-22T04:25:04.648Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/whois-mcp","artifact":"https://unfragile.ai/whois-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=whois-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}