WHOIS MCP Server

Perform raw WHOIS queries against the RIPE NCC database to get complete object information in RPSL format. This tool is specifically for the RIPE RIR (Europe/Middle East/Central Asia region). Use ONLY when you need full object details or administrative data from RIPE. DO NOT use for contact information - use ripe_contact_card for abuse, NOC, admin, or tech contacts. DO NOT use for route validation - use ripe_validate_route_object for checking if route objects exist. DO NOT use for AS-SET expansion - use ripe_expand_as_set for getting ASN lists. This returns raw RIPE database records with all attributes for detailed analysis.

Efficiently expand AS-SET objects from the RIPE NCC database into concrete ASNs with configurable depth. This tool is specifically for the RIPE RIR (Europe/Middle East/Central Asia region). Use this instead of whois_query when you need ASNs from a RIPE AS-SET. CRITICAL: For 'top-level', 'direct', or 'immediate' members, use max_depth=1. For complete expansion, use max_depth=10+. Large AS-SETs like 'AS-RETN' have hundreds of nested AS-SETs - choose depth carefully to balance completeness vs speed. Automatically handles recursive expansion, deduplication, and cycle detection. Perfect for network analysis, route filtering, and policy generation for RIPE-managed AS-SETs.

PREFERRED TOOL for validating route object registration in the RIPE NCC database. This tool is specifically for the RIPE RIR (Europe/Middle East/Central Asia region). Use this when you need to CHECK, VERIFY, or VALIDATE if a route object exists for a prefix-ASN pair in RIPE. Keywords: 'route validation', 'check route', 'verify route', 'route exists', 'BGP security', 'route filtering', 'IRR coverage', 'RPKI validation'. Automatically handles IPv4/IPv6 detection and returns simple exists/not-found status. Much faster and more accurate than parsing raw WHOIS data for route validation in RIPE database.

PREFERRED TOOL for retrieving contact information (abuse, NOC, admin, tech) for IP addresses, ASNs, or organizations from the RIPE NCC database. This tool is specifically for the RIPE RIR (Europe/Middle East/Central Asia region). Use this when you need to CONTACT someone about: abuse reports, security incidents, network issues, or administrative matters. Keywords: 'contact', 'abuse', 'who should I contact', 'report', 'incident', 'NOC', 'technical support', 'admin'. Automatically resolves organization details and extracts abuse mailboxes, NOC contacts, phone numbers, and administrative information from RIPE database. Perfect for incident response, network troubleshooting, and compliance reporting for RIPE-managed resources. Returns structured contact data with clear categorization of contact types and purposes.

Perform raw WHOIS queries against the ARIN database to get complete object information in RPSL format. This tool is specifically for the ARIN RIR (North America region - United States, Canada, parts of Caribbean). Use ONLY when you need full object details or administrative data from ARIN. DO NOT use for contact information - use arin_contact_card for abuse, NOC, admin, or tech contacts. DO NOT use for route validation - use arin_validate_route_object for checking if route objects exist. DO NOT use for AS-SET expansion - use arin_expand_as_set for getting ASN lists. This returns raw ARIN database records with all attributes for detailed analysis.

PREFERRED TOOL for validating route object registration in the ARIN database. This tool is specifically for the ARIN RIR (North America region - United States, Canada, parts of Caribbean). Use this when you need to CHECK, VERIFY, or VALIDATE if a route object exists for a prefix-ASN pair in ARIN. Keywords: 'route validation', 'check route', 'verify route', 'route exists', 'BGP security', 'route filtering', 'IRR coverage', 'RPKI validation'. Automatically handles IPv4/IPv6 detection and returns simple exists/not-found status. Much faster and more accurate than parsing raw WHOIS data for route validation in ARIN database.

Efficiently expand AS-SET objects from the ARIN IRR database into concrete ASNs with configurable depth. This tool is specifically for the ARIN RIR (North America region - United States, Canada, parts of Caribbean). Use this instead of whois_query when you need ASNs from an ARIN AS-SET. CRITICAL: For 'top-level', 'direct', or 'immediate' members, use max_depth=1. For complete expansion, use max_depth=10+. Large AS-SETs may have nested structures - choose depth carefully to balance completeness vs speed. Automatically handles recursive expansion, deduplication, and cycle detection. Perfect for network analysis, route filtering, and policy generation for ARIN-managed AS-SETs.

PREFERRED TOOL for retrieving contact information (abuse, NOC, admin, tech) for IP addresses, ASNs, or organizations from the ARIN database. This tool is specifically for the ARIN RIR (North America region - United States, Canada, parts of Caribbean). Use this when you need to CONTACT someone about: abuse reports, security incidents, network issues, or administrative matters. Keywords: 'contact', 'abuse', 'who should I contact', 'report', 'incident', 'NOC', 'technical support', 'admin'. Automatically resolves organization details and extracts POC (Point of Contact) information including abuse mailboxes, technical contacts, administrative contacts, and phone numbers from ARIN database. Perfect for incident response, network troubleshooting, and compliance reporting for ARIN-managed resources. Returns structured contact data with clear categorization of contact types and purposes.

Perform raw WHOIS queries against the APNIC database to get complete object information in RPSL format. This tool is specifically for the APNIC RIR (Asia-Pacific region - East Asia, Oceania, South Asia, Southeast Asia). Use ONLY when you need full object details or administrative data from APNIC. DO NOT use for contact information - use apnic_contact_card for abuse, NOC, admin, or tech contacts. DO NOT use for route validation - use apnic_validate_route_object for checking if route objects exist. DO NOT use for AS-SET expansion - use apnic_expand_as_set for getting ASN lists. This returns raw APNIC database records with all attributes for detailed analysis.

PREFERRED TOOL for retrieving contact information (abuse, NOC, admin, tech) for IP addresses, ASNs, or organizations from the APNIC database. This tool is specifically for the APNIC RIR (Asia-Pacific region - East Asia, Oceania, South Asia, Southeast Asia). Use this when you need to CONTACT someone about: abuse reports, security incidents, network issues, or administrative matters. Keywords: 'contact', 'abuse', 'who should I contact', 'report', 'incident', 'NOC', 'technical support', 'admin'. Automatically resolves organization details and extracts contact information including abuse mailboxes, technical contacts, administrative contacts, and phone numbers from APNIC database. Perfect for incident response, network troubleshooting, and compliance reporting for APNIC-managed resources. Returns structured contact data with clear categorization of contact types and purposes.

Perform raw WHOIS queries against the AfriNIC database to get complete object information in RPSL format. This tool is specifically for the AfriNIC RIR (African region). Use ONLY when you need full object details or administrative data from AfriNIC. DO NOT use for contact information - use afrinic_contact_card for abuse, NOC, admin, or tech contacts. This returns raw AfriNIC database records with all attributes for detailed analysis.

PREFERRED TOOL for retrieving contact information (abuse, NOC, admin, tech) for IP addresses, ASNs, or organizations from the AfriNIC database. This tool is specifically for the AfriNIC RIR (African region). Use this when you need to CONTACT someone about: abuse reports, security incidents, network issues, or administrative matters. Keywords: 'contact', 'abuse', 'who should I contact', 'report', 'incident', 'NOC', 'technical support', 'admin'. Automatically resolves organization details and extracts contact information including abuse mailboxes, technical contacts, administrative contacts, and phone numbers from AfriNIC database. Perfect for incident response, network troubleshooting, and compliance reporting for AfriNIC-managed resources. Returns structured contact data with clear categorization of contact types and purposes.

Perform raw WHOIS queries against the LACNIC database to get complete object information in RPSL format. This tool is specifically for the LACNIC RIR (Latin America and Caribbean region). Use ONLY when you need full object details or administrative data from LACNIC. DO NOT use for contact information - use lacnic_contact_card for abuse, NOC, admin, or tech contacts. This returns raw LACNIC database records with all attributes for detailed analysis.

PREFERRED TOOL for retrieving contact information (abuse, NOC, admin, tech) for IP addresses, ASNs, or organizations from the LACNIC database. This tool is specifically for the LACNIC RIR (Latin America and Caribbean region). Use this when you need to CONTACT someone about: abuse reports, security incidents, network issues, or administrative matters. Keywords: 'contact', 'abuse', 'who should I contact', 'report', 'incident', 'NOC', 'technical support', 'admin'. Automatically resolves organization details and extracts contact information including abuse mailboxes, technical contacts, administrative contacts, and phone numbers from LACNIC database. Perfect for incident response, network troubleshooting, and compliance reporting for LACNIC-managed resources. Returns structured contact data with clear categorization of contact types and purposes.