InternetData MCP Server
The InternetData MCP Server gives an AI agent nine read-only tools for InternetData's IP, AS, domain, database catalog, licensing, usage, and download-history data.
Look up one IP or many IPs: location, announcing network/ASN, company, abuse contact, reverse DNS, Tor/relay/anycast/carrier/satellite/service flags, VPN/proxy/hosting/CDN detection, Whois/RWHOIS, hosted domains, and more.
Look up an AS by number: operator, country, registry, allocation date, domain, announced prefixes with RPKI status, IP/prefix counts, and ASN Whois.
Look up a domain: registration status, DNS record types and records, organization IP ranges, and disposable-domain status.
Check the current API key's plan, field tier, usage, quota, hard limit, and reset window.
List database families with your organization's license standing, versions, and available formats.
Get database metadata: columns, sample rows, row count, build date, update frequency, and file sizes.
Get published checksums for a database file in a chosen format.
List recent download attempts for your organization, including refusals.
Results are read-only and come from latest database builds; coverage blocks explain which fields your plan excludes, and lookups do not send live DNS queries or open connections to targets.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@InternetData MCP Server which IP databases are we licensed for, and how big is the latest VPN build?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
InternetData MCP Server
The official Model Context Protocol server for the InternetData API.
It gives an AI agent nine read-only tools. Four look up an IP address, an AS or a domain in every database we publish: where an address is and who uses it, whether it is a VPN, a residential, datacenter, mobile or public proxy, a Tor node, a privacy relay, a hosting provider or a CDN, anycast, carrier, satellite or reserved space, and whether an SSH, mail, web, open DNS resolver or BitTorrent service answered on it. The rest cover your key's plan, the database catalog and your organization's license for each, what a database holds, its digests and your download history.
Getting Started
We host it at https://mcp.internetdata.io/mcp, and you sign in to it with your InternetData account. It also runs on your own machine from npm. Databases are licensed by contract. The Open ones, tor_ip_v1 among them, are licensed to every organization from the start and are free under CC BY-SA 4.0. For the rest, see the API documentation, or request an evaluation if your organization doesn't have a license yet.
In Claude
In claude.ai, the desktop app or Cowork, add https://mcp.internetdata.io/mcp as a custom connector and choose Use Claude's published identity when asked. In Claude Code, install our plugin, which adds the server with skills:
/plugin marketplace add internetdata/claude-plugin
/plugin install internetdata@internetdataEither way you sign in with your InternetData account, and Claude never sees your API key. The steps, the skills and how to disconnect: docs.internetdata.io/integrations/claude.
In ChatGPT and Codex
InternetData is in the plugin directory ChatGPT and Codex share: add it from its listing. Codex also installs our plugin from the command line, which adds the server with skills:
codex plugin marketplace add internetdata/openai-plugin
codex plugin add internetdata@internetdata
codex mcp login internetdataEither way you sign in with your InternetData account, and neither sees your API key. The steps: docs.internetdata.io/integrations/chatgpt and docs.internetdata.io/integrations/codex. On the OpenAI API, the Responses API's mcp tool takes the server as its server_url and your key as its authorization.
In Gemini CLI
Install our extension, which runs the npm package below on your machine:
gemini extensions install https://github.com/internetdata/mcpIt asks for your API key and keeps it in your system keychain. Leave it blank to look things up without one; the database tools need a key with the db.download scope.
In any other MCP client
Point it at https://mcp.internetdata.io/mcp. A client that supports MCP authorization signs in the same way. One that doesn't can send a key instead, as Authorization: Bearer your-key.
On your own machine
No API key needed to look something up. Unlimited, the free plan, answers with no daily or monthly cap, with a key or without one: an address's country-level location, the network that announces it, the company that uses it, its abuse email and reverse DNS name, and whether it is Tor, a relay, anycast, carrier or satellite space and which services answer on it; an AS's registration; and whether a domain is registered and which DNS record types it has. Every paid plan answers every field: VPN, proxy, hosting and CDN detection with the detail behind each flag, city-level location, Whois and RWHOIS, an AS's prefixes, RPKI status, neighbors and hosted domains, and a domain's records, IP ranges and whether it is disposable. A free account tries every field, 100 lookups a day.
Add this to your MCP client's config:
{
"mcpServers": {
"internetdata": {
"command": "npx",
"args": ["-y", "internetdata-mcp"]
}
}
}Requires Node.js 22 or newer.
A key on a paid plan unlocks every field, and the database tools need a key carrying the db.download scope. Put it in the environment:
{
"mcpServers": {
"internetdata": {
"command": "npx",
"args": ["-y", "internetdata-mcp"],
"env": { "INTERNETDATA_API_KEY": "your-key" }
}
}
}INTERNETDATA_BASE_URL overrides the endpoint if you need to point somewhere else.
Related MCP server: SQLite Explorer MCP
Tools
Tool | What it answers |
| What every database says about one address. |
| The same for a whole list of addresses in one call, keyed by address. A long list is batched for you. Needs a key on a paid plan; with a key on the free plan, a list of up to 10 addresses is looked up one address at a time instead. |
| What we know about one AS, by its number: its registration, and on a paid plan its prefixes, RPKI status and Whois record, its rank and Tier 1 flag, its upstreams, peers and downstreams, and the domains it hosts. |
| What we know about one domain: whether it is registered and which DNS record types it has, and on a paid plan the records, its organization's IP ranges and whether it is disposable. |
| What this key is entitled to and what it has spent: plan, field tier, requests so far, allowance, and when it resets. |
| Every database we publish, with its |
| A database's columns, sample rows, row count, build date and file sizes. |
| The published digests for one database file. |
| Your organization's recent download attempts, refusals included. |
Every tool is read-only. Answers come from our databases' latest builds: no lookup sends a DNS query, or opens a connection to the address or the domain.
There is deliberately no my_ip tool, although every client library has one. Over a hosted transport the address our edge observes belongs to whatever proxied the call - Claude's infrastructure, not the person asking - so the tool would answer confidently and wrongly for the only reading anyone would put on it. my_entitlement has no such problem and is the same answer from any transport, because it describes the credential rather than the connection.
A paid plan's usage counts against the anniversary of the subscription, not the calendar month and not the billing period, and the free plan's against the UTC day. hard_limit is where full answers stop, and a null one means they never do; it is not a limit of zero.
Reading a result
Each lookup comes back with a coverage block beside it:
{
"result": { "ip": "146.70.116.130", "is_bogon": false, "is_tor": false, "location": { "country": "AT", "...": "..." }, "...": "..." },
"coverage": {
"included": ["ip", "is_bogon", "is_tor", "is_relay", "tor", "relay", "location", "asn", "..."],
"not_included": ["is_vpn", "is_hosting", "vpn", "whois", "location.city", "..."],
"note": "The fields in not_included were not returned, because this API key's plan does not include them. ..."
}
}This matters more here than in a normal client library. A field missing from a result means your plan doesn't include it, never "we checked and found nothing" - and a model reading the result on its own will otherwise treat the absence as a negative answer. coverage states the difference explicitly so it can't. A paid field inside an object every plan gets, such as location.city, is named by its path.
An answer to a key on the free plan also carries trial_expired: false while its organization's daily trial of every field lasts, and true once the answer is Unlimited's, which coverage.note then says.
An answer to a key on a paid plan carries cap_reached instead: false while it has every field, and true once its organization's overage cap is reached and the answer has Unlimited's fields, unbilled, which coverage.note says too. Raising or removing the cap in Billing turns it false again. The API never answers a reached cap with an error, and in lookup_ips a cap reached part way through answers the rest of the list this way, so coverage then gives the narrowest answer's lists and says the answers differ.
Two spellings of a database ID
list_databases answers a base ID and a versions array:
{
"base": "vpn_ip",
"standing": "licensed",
"open": false,
"versions": [{ "id": "vpn_ip_v1", "version": 1, "formats": ["csvgz", "mmdb"] }]
}The base is what a license names. versions[].id is what a download names, and it is the one database_metadata and database_checksum accept. The tools say so in their own descriptions, so an agent generally gets this right on its own; it is worth knowing when you read a transcript where one was refused.
There is no download tool, deliberately
The published builds run to several GB, which is not something an agent should pull into a conversation. database_metadata is how you find out what a transfer would cost, and the client libraries or the API are how you actually move the bytes.
Reading the download history
list_downloads is a bounded window - at most 200 attempts, newest first - and it lists refusals alongside successes, because a denial and its http_status are what answer "it stopped working". A database missing from the answer means it is not in that window, never that it was never fetched.
Other Libraries
There are official InternetData client libraries available for many languages including PHP, Python, Go, Java, and Ruby. See our GitHub at https://github.com/internetdata for more.
About InternetData
Geolocation, anonymity, ownership, network, service and domain data for any IP address, AS or domain, by API or as databases you download.
License
This project is licensed under the MIT License.
Available Tools
9 toolsdatabase_checksumGet a database's checksumsARead-onlyIdempotentInspect
The published digests for one database file, for verifying a copy you already hold or deciding whether a build has changed since you last fetched it. It is licensed like the download itself, so a database this key cannot download is refused here too. Looking up a checksum is not a download and does not appear in list_downloads.
Inputs: format (required), dataset_id (required). Returns: checksums
database_metadataDescribe a databaseARead-onlyIdempotentInspect
What is inside one database before you fetch it: the columns in each published format with their types, a few sample rows, the row count, the build date and the file sizes. Use this to answer questions about what a database contains without downloading it - the files reach several GB - and to budget a transfer before starting one.
Inputs: dataset_id (required). Returns: The build document written by the exporter, served through unchanged.
list_databasesList databasesARead-onlyIdempotentInspect
The IP database catalog as this API key's organization may see it, one entry per database FAMILY, with standing saying where their license stands: licensed if the family is theirs today, expired if the term has ended, unlicensed if it is published but has never been bought. Each entry has a base ID, which is what a license names, and a versions array whose id is what the other database tools take - pass versions[].id (bogon_ip_v1), never the base (bogon_ip). Ask again rather than holding on to this: it is answered per key and is not the same for everyone.
Inputs: no named parameters. Returns: databases
list_downloadsList recent download attemptsARead-onlyInspect
This organization's own recent download attempts, newest first, REFUSALS INCLUDED - a denial carries the outcome and http_status that answer "it stopped working", which nothing else here can. Use it to explain a failing fetch, to confirm a transfer ran, or to check whether a request was theirs. This is a bounded WINDOW of at most 200 rows, so a database missing from the answer means it is not in this window - never that it was never downloaded.
Inputs: limit. Returns: downloads
lookup_asnLook up an ASARead-onlyIdempotentInspect
What InternetData knows about one autonomous system, by its number: its operator, country, registry, allocation date and domain, the kind of network it runs, how many IPv4 addresses and prefixes it announces with their RPKI counts, its ASN Whois record, its rank and whether it is Tier 1, the AS numbers it gets transit from, peers with and provides transit to, how many domains it hosts with the most popular, and the prefixes it announces in global BGP with their RPKI status. The prefixes and each list of AS numbers hold their first 100, the AS numbers ascending, with truncated giving the total where there are more. An AS no database knows comes back as its number with empty values. Unlimited, the free plan, answers its operator, country, registry, allocation date and domain, with a key or without one. Every paid plan answers every field up to any overage cap its organization sets, and so does a key on the free plan while its organization's daily trial lasts. Always read coverage.note before concluding anything from a field that is not in the result.
Inputs: asn (required). Returns: result, coverage, truncated
lookup_domainLook up a domainARead-onlyIdempotentInspect
What InternetData knows about one domain, from its latest snapshots rather than a live DNS query: whether it is registered, which DNS record types it has, the records themselves, its organization's IP ranges, and whether it is a disposable email domain. Unlimited, the free plan, answers whether it is registered and which record types it has, with a key or without one. Every paid plan answers every field up to any overage cap its organization sets, and so does a key on the free plan while its organization's daily trial lasts. Always read coverage.note before concluding anything from a field that is not in the result.
Inputs: domain (required). Returns: result, coverage
lookup_ipLook up an IP addressARead-onlyIdempotentInspect
What every database InternetData publishes says about one IPv4 or IPv6 address: where it is, which network announces it, who uses it, its abuse contact and reverse DNS name; whether it is a Tor node, a privacy relay, anycast, or a mobile carrier's or satellite operator's space; whether an SSH, mail, web, open DNS resolver or BitTorrent service answered on it; whether it is a VPN, a residential, datacenter, mobile or public proxy, a hosting provider or a CDN; and its Whois and RWHOIS records and how many domains it hosts. Unlimited, the free plan, answers with a key or without one: the location to its country, the network, the company, the abuse email, the reverse DNS name, and the Tor, relay, anycast, carrier, satellite and service flags, with the Tor and relay detail. Every paid plan answers every field up to any overage cap its organization sets, and so does a key on the free plan while its organization's daily trial lasts. Private and reserved addresses are answered locally, without calling the API. Always read coverage.note before concluding anything from a field that is not in the result.
Inputs: ip (required). Returns: result, coverage
lookup_ipsLook up several IP addressesARead-onlyIdempotentInspect
Look up a list of addresses in one call, returning a map keyed by address so duplicates collapse and the order you passed them stops mattering. Each answer is what lookup_ip gives for that address. Pass the whole list rather than splitting it yourself: a long one is batched for you. Prefer this over repeated lookup_ip calls when you already have the list, for example when triaging a log file. A batch needs a key on a paid plan: with a key on the free plan, a list of up to 10 addresses is looked up one address at a time instead, and a longer one comes back refused. An address that fails carries its error in place of a result rather than failing the batch. Always read coverage.note before concluding anything from a field that is not in the result.
Inputs: ips (required). Returns: results, coverage
my_entitlementPlan and usage for this keyARead-onlyInspect
What this API key is entitled to and how much of it has been used: the plan, the field tier that decides how much of a lookup answer comes back, the requests counted so far, the allowance, and when it resets. Use it to explain why a field is missing from a lookup, or before a large batch. A paid plan's usage counts against the anniversary of the subscription rather than the calendar month; the free plan's counts the lookups its daily trial answered with every field, against the UTC day. Either can lag a few seconds behind. hard_limit is where full answers stop, and a null one means they never do - it is NOT a limit of zero.
Inputs: no named parameters. Returns: entitlement
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool targets a clearly distinct resource or operation: single vs. batch IP lookup, ASN lookup, domain lookup, entitlement inspection, and database catalog/download-support tools. There is no meaningful overlap in purpose, and the singular/plural naming plus descriptions make lookup_ip versus lookup_ips obvious.
All names use snake_case and are highly readable, with clear prefixes such as lookup_ and list_. However, several tools are noun-first (database_checksum, database_metadata, my_entitlement) rather than following a single verb_noun convention throughout.
Nine tools is well-scoped for an internet-data lookup plus database-catalog server. Each tool covers a distinct need, and none feels redundant or gratuitous.
Core lookup coverage is strong across IPs, ASNs, and domains, and the database catalog, checksum, metadata, and download-history surfaces are present. However, there is no actual database download or fetch tool despite multiple descriptions referring to fetching files and the download itself, leaving a notable lifecycle gap.
Maintenance
Related MCP Connectors
IP intelligence, network diagnostics, and AI service availability tools for AI agents.
Free, no-API-key network lookups for AI agents — IP geolocation, DNS, WHOIS, HTTP and SSL/TLS certificate checks, and full domain health reports.
Read-only search of 2,189 AI agent tools (MCP servers, x402 APIs) with daily automated trust scores.
A read-only verified record of agent-operable GTM tools: search, fetch, compare, track changes.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables AI agents to classify IP addresses through the VPNDetection API with read-only tools that detect VPNs, residential and datacenter proxies, Tor nodes, relays, hosting providers and CDNs, in single or bulk lookups of up to 100 addresses. It also exposes which datasets an organisation is licensed for, along with their metadata and published checksums.73,011 npm1MIT
- AlicenseAqualityCmaintenanceEnables AI agents to explore and query SQLite databases through read-only, sandboxed tools for listing tables, describing schemas, fetching DDL, and running a single capped SELECT statement. Also supports plain-English questions that are converted to SQL and routed through the same sandbox.4MIT
- AlicenseAqualityBmaintenanceEnables AI agents and developers to introspect SQLite schemas, run sandboxed read-only queries with pagination, inspect query plans, and generate token-dense database summaries for LLM context. All operations enforce multi-layer read-only safety so databases can be explored without risk of mutation.5MIT
- AlicenseAqualityBmaintenanceEnables AI agents to compare two tables across the same or different databases and report what changed, which columns changed, and where changes concentrate, plus source/table discovery and schema description. Runs four read-only tools that take source names rather than connection strings, returning a stable JSON contract with a risk verdict.1152 npmMIT