Claude IPGeolocation.io connectorWhat Claude can do in your IPGeolocation.io account.
The Claude IPGeolocation.io connector exposes 16 tools. 16 look up public data (IP location, threats, networks, timezones, astronomy, user agents), 0 change anything, 0 are undocumented. Here: what each lookup costs, what needs a key, and what it cannot do.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can query IPGeolocation.io
Claude cannot tell by itself where an IP address sits or whether it hides behind a VPN. With this desktop extension installed, it queries IPGeolocation.io while it answers: location, network owner, threat signals, timezone, even sunrise times. You paste an address or a log line, Claude runs the right lookup and explains the result in plain words.
Triage a suspicious login. lookup_ip places the address, and check_security flags VPN, proxy, Tor or bot signals, so you know in one exchange whether to worry.
Clean up a list of visitors. bulk_lookup_ip geolocates a whole batch of addresses and bulk_parse_user_agent decodes their browsers and devices, which turns a raw export into a readable picture.
Plan across time zones. convert_timezone converts a meeting time between two cities, and get_astronomy_time_series lists sunrise and sunset for up to 90 days.
Now the limits. Every tool looks up data; none changes anything, and Claude never files an abuse report for you. Only get_my_ip works without an API key. Seven tools sit on IPGeolocation.io's base offer and the other nine need a higher one. It is a desktop extension, so it runs in Claude Desktop only. And nothing runs on its own: no lookup fires when a new IP hits your server. For that, you want an automation tool, a different job; the IPGeolocation.io Make integration covers that side, and the Integrations hub lists the rest.
The vocabulary in one minute
Five words you will run into while plugging IPGeolocation.io in.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude picks the ones it needs on its own, and the directory lists them by name.
- Authorization
- The sign-in screen of IPGeolocation.io itself, where you hand Claude the access it will use. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes your account, shown right in the chat.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as IPGeolocation.io.
Plug IPGeolocation.io into Claude in three steps
- 01
Find IPGeolocation.io in Claude
In Claude's settings, open Customize, then Connectors, and look for IPGeolocation.io in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can connect.
- 02
Start the connection
Click Connect on the IPGeolocation.io row, then sign in to IPGeolocation.io in the window the service opens itself. If the link ever breaks, use Disconnect and plug it back in.
- 03
Read the authorization screen
Before you approve, check what the access covers. That screen belongs to the service, not to Claude. On this connector, the access that matters is your IPGeolocation.io API key, which you can revoke from your IPGeolocation.io account.
The 16 tools of the Claude IPGeolocation.io connector
IPGeolocation.io MCP Server gives Claude 16 tools: 16 that read your account, 0 that change something in it.
One group only: every tool looks up data and changes nothing. The names stay the ones Claude shows, in English, and each note gives the credit cost IPGeolocation.io publishes.
- 16 read
What Claude looks up (16)
16 toolsSixteen lookups on public network, time and device data. None of them writes anywhere.
lookup_ip
Returns the location, timezone, currency and network owner (ASN) behind one IP address, for 1 credit. Claude can then explain where a connection comes from in plain words.
bulk_lookup_ip
Geolocates a whole batch of IP addresses in one call, 1 credit per IP, up to 50,000 per call with a default cap of 1,000.
get_my_ip
Gives the public IP of the machine running the extension, at 0 credits and without an API key, which makes it the one tool that works before any setup.
lookup_company
Names the company and the ASN holder for one IP, for 1 credit, so Claude can tell you which organization a visit likely came from.
lookup_currency
Returns the currency and country metadata tied to one IP address, for 1 credit, which Claude can use to reason about pricing display.
lookup_network
Describes the route prefix, connection type and anycast status of an IP, for 1 credit, so Claude can say what kind of network sits behind it.
check_security
Flags VPN, proxy, Tor, bot, spam and threat signals for one IP, at 2 credits, so Claude can tell you how risky a connection looks.
bulk_security_check
Runs the same threat checks on a batch of IP addresses, at 2 credits per IP, which turns a log extract into a list of risky sources.
get_timezone
Gives current time and timezone details for a timezone name, a location, an IP, an airport code or a UN/LOCODE, for 1 credit.
convert_timezone
Converts a given time from one location to another, for 1 credit, so Claude can plan across time zones without mental math.
get_astronomy
Returns sunrise, sunset, moonrise, moonset, twilight and moon phase for one date and place, for 1 credit.
get_astronomy_time_series
Gives daily astronomy data across a date range of up to 90 days, for 1 credit, which Claude can turn into a schedule.
parse_user_agent
Breaks one user-agent string into browser, device, operating system and engine, for 1 credit, so Claude can tell you what a visitor was using.
bulk_parse_user_agent
Parses a batch of user-agent strings, 1 credit each, up to 50,000 per call with a default cap of 1,000, for a quick picture of your traffic.
lookup_asn
Returns details on an autonomous system number: peers, upstreams, downstreams, routes and WHOIS, for 1 credit.
get_abuse_contact
Finds the abuse contact behind an IP, with emails, phone, address and route, for 1 credit, so you know whom to report an attack to.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. The request shows up in the conversation, at the moment it matters.
On a Team or Enterprise workspace, the owners decide whether a member can let some actions through without being asked every time. They can also limit what a connector may do for the whole organization, for instance keep reading open and close writing. That setting applies to everyone, and nobody gets around it from their own account. Claude also works with the IPGeolocation.io key you configure and nothing more.
Which plans include it
Out of the 819 sheets in the official directory, not one shows availability by plan. The connector by connector answer is published nowhere: that is a real gap in the catalogue.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before each member can connect. For the current status, check the IPGeolocation.io sheet in the official directory from your own account.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a new IP reaches your server, a threat list changes or a date comes around.
This connector is documented only by its publisher: no Claude help page covers it. The tool list is an observed floor, not a promise, since an admin can open actions that no public sheet shows. The directory's partner badge is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as announced. Plug in what comes from a publisher you trust, here IPGeolocation.io itself.
Need help connecting IPGeolocation.io MCP Server to Claude?
A person reads every message.
