ip-enrichment-mcp
Related Servers
Alternatives to ip-enrichment-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceGives AI agents access to public internet interconnection data, letting them look up which networks connect to each other, at which internet exchanges and facilities they are present, under what peering policy, and who a given IP range or AS number is registered to. Responses are compact, sourced and aged, and it distinguishes missing records from genuinely absent networks rather than guessing.1MIT
- AlicenseNot gradedqualityBmaintenanceProvides DNS and network-reconnaissance tools that let agents run lookups for records, reverse DNS, ping, passive subdomain discovery, shared nameservers, geolocation, reverse IP, ASN, HTTP headers, subnet arithmetic and page links, plus key-gated WHOIS, MTR and traceroute. Responses are parsed into structured JSON with verbatim raw text, and it runs either through a hosted gateway or as a local stdio server.416 npmMIT
- AlicenseAqualityDmaintenanceMCP server providing DNS resolution, reverse DNS, RDAP-based WHOIS, and IP geolocation lookups. No API keys required , and all upstreams are public.4MIT
- AlicenseAqualityCmaintenanceProvides global internet resource intelligence by querying RIRs for IP and ASN data, routing visibility, and network health. It enables users to perform RPKI validation, BGP inspection, and historical allocation analysis through natural language or a REST API.421MIT
- AlicenseAqualityDmaintenanceProvides threat intelligence lookups against the AbuseIPDB database, enabling IP reputation checks, CIDR block analysis, and log enrichment. It features intelligent caching and rate limiting to efficiently manage API usage for security analysis and automated workflows.5MIT
- AlicenseNot gradedqualityAmaintenanceQuery 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.64MIT
TDQS
Scored across 2 tools
resolve_ips operates on IP addresses, while list_service_tag_ranges operates on a tag name; the two tools have clearly distinct inputs and outputs, with no overlap in purpose.
Both tools use snake_case and follow a verb_noun pattern (resolve_ips, list_service_tag_ranges), providing a consistent and predictable naming convention.
Only two tools are provided; while each is distinct, the surface feels thin for an enrichment server that could reasonably support additional query or discovery operations (e.g., listing all tags, sync status).
The core enrichment workflow (IP resolution) is well-covered, and the auxiliary tag-range lookup adds value. However, minor gaps exist, such as no tool to list available service tags or explicitly check/trigger index synchronization.