ipatlas IP geolocation vs IPGeolocation.io MCP Server
ipatlas IP geolocation is an MCP server published by ipatlas.dev. Marketplaces we read that list it: 1 (Official MCP Registry). IPGeolocation.io MCP Server is an MCP server published by IPGeolocation. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   IPGeolocation.io MCP Server | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 2.0.1 Downloads/month (npm): 475 Downloads/week (npm): 73 Forks (GitHub): 4 Stars (GitHub): 4 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ipatlas IP geolocation | IPGeolocation.io MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 4 |
| Forks (GitHub) (differs) | No figure on GitHub | 4 |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | Remote server (api.ipatlas.dev/mcp) | On your machine (ipgeolocation-io-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/ipgeolocation/ipgeolocation-io-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-18 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
ipatlas IP geolocation
IP geolocation: country, EU status, region, city, time zone and ASN for any IPv4/IPv6 address.
IPGeolocation.io MCP Server
IP geolocation, security, ASN, abuse, time zones, astronomy, and user-agent parsing over stdio.
How to run each
ipatlas IP geolocation As a remote MCP server
claude mcp add --transport http ipatlas https://api.ipatlas.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
IPGeolocation.io MCP Server As a local MCP server: npm package
claude mcp add --env "IPGEOLOCATION_API_KEY=<YOUR_IPGEOLOCATION_API_KEY>" --transport stdio ipgeolocation-io-mcp -- npx -y ipgeolocation-io-mcpRequires: IPGEOLOCATION_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only ipatlas IP geolocation has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of ipatlas IP geolocation publish no settings it asks for, so we do not compare settings.
What it can do: ipatlas IP geolocation · What it can do: IPGeolocation.io MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.