IPGeolocation.io MCP for AI. Know the origin, threat, and time of any IP address.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
How this MCP server connects to your AI agent
IPGeolocation.io provides real-time intelligence for analyzing IP addresses, domains, and time zones directly through your AI client. Use this MCP to identify a location, check for VPN usage, determine network details (like ASN info), or calculate precise time zone shifts based on an IP address.
It's essential for security analysis, localization logic, and data enrichment.
What AI agents can do with IPGeolocation.io Automation
Bulk security
Checks multiple IP addresses at once to determine their security status or threat level.
Bulk user agent
Parses and categorizes a list of browser strings (User-Agents) into common device types and operating systems.
Convert timezone
Calculates the exact time difference when moving a specific moment between two different time zones.
Retrieve city, country, ISP, coordinates, and other geographical data for any IPv4 or IPv6 address.
Check if an IP is associated with a VPN, proxy, Tor node, or calculate its overall threat score.
Find the local time for any location or convert a specific time between two different time zones.
Access details about an IP's Autonomous System Number (ASN) or find abuse contact information for reporting issues.
Break down a complex user-agent string into structured device and operating system information.
Ask an AI about this
Waiting for input…
What AI agents can do with IPGeolocation.io: 11 Tools
These tools let you query IP addresses, parse user agents, convert times, check security status, and retrieve detailed network information on demand.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using IPGeolocation.io on VinkiusBulk Security
Checks multiple IP addresses at once to determine their security status or threat level.
Bulk User Agent
Parses and categorizes a list of browser strings (User-Agents) into common device...
Convert Timezone
Calculates the exact time difference when moving a specific moment between two...
Get Abuse
Retrieves contact information for reporting abuse related to a given IP address...
Get Asn
Provides technical details about the Autonomous System Number (ASN) associated with...
Get Astronomy
Retrieves astronomical data, like sunrise or sunset times, for a specified location.
Get Ip
Determines the public IP address that is currently making the request to your agent.
Get Ipgeo
Looks up geographical data, like city and country coordinates, from a single IP...
Get Security
Checks the security status of one specific IP address to identify if it’s flagged as...
Get Timezone
Determines the correct time zone identifier for any given location or IP address.
Get User Agent
Analyzes a single browser string to extract details about the device and OS that...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The IPGeolocation.io integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with IPGeolocation.io, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by IPGeolocation.io. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 11 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The Headache of Context Switching, Solved with Vinkius AI Gateway
Today, figuring out the full story behind an IP address means jumping between three different tools. You check a geo-lookup site for location; then you go to a threat intel dashboard to see if it's flagged as a proxy; and finally, you open a separate calendar tool just to figure out what time zone that location uses. It’s slow, tedious, and the data never lines up perfectly.
With this MCP, all of that context is centralized. You feed an IP address into your agent, and it runs multiple checks in sequence: getting the coordinates with `get_ipgeo`, checking for threats with `get_security`, and confirming the correct timezone using `get_timezone`. The output you get back is one clean block of data—no manual switching required.
IPGeolocation.io MCP Provides Full Network Context
You don't have to copy an IP address into a geo-lookup tool, then manually paste the resulting coordinates into your database, and finally run that coordinate through a separate time conversion widget. All those steps are gone.
The agent handles the entire chain: it gets the location data via `get_ipgeo`, uses `get_asn` to give depth to that data point, and then gives you clean date/time logic using `convert_timezone`. You just ask a question, and you get the fully researched answer.
What your AI can actually do with this
Look, sometimes you don't just need to know where an IP address is from; you need to know what it means. This MCP handles the full spectrum of network context. You can run checks on suspicious IPs to see if they are proxies or known threats, which saves time when vetting user submissions.
It also gives you precise timezone data for any given location, so your application logic always calculates times correctly, regardless of where the user is. Plus, it breaks down complex browser strings into readable details. When you connect this via Vinkius, your AI client gets a full suite of tools to analyze network and geographical data without ever leaving the chat window.
It’s basically having a whole security intelligence platform ready whenever you need it.
019e5d27-d148-7014-a077-a2cdccd799ba 
Here's how it actually works
The bottom line is you get reliable, real-time access to deep network intelligence without writing a single API call yourself.
Subscribe to this MCP and paste your API key.
Your AI client uses natural language prompts to call the available tools, passing in necessary parameters like IP addresses or timezones.
The MCP processes the query against its network databases and returns structured data (e.g., JSON) that your agent can use for further analysis.
Who is this actually for?
Security analysts who are tired of switching between multiple threat intel platforms. Data scientists needing consistent geographical and network metadata for large datasets. Developers whose applications rely on perfect, multi-timezone scheduling.
Vetting suspicious IP addresses from user reports or logs to immediately detect if they're proxies or part of a botnet.
Implementing localization features, ensuring that date/time displayed in the UI correctly adjusts for different geographic zones.
Enriching raw datasets with geographical context (city, country) and network metadata using bulk lookups.
What Changes When You Connect
Stop guessing about location. Use get_ipgeo to get immediate city, country, and coordinate data for any IPv4 or IPv6 address.
Improve fraud detection. Run a quick check using get_security on suspicious IPs to see if they're known VPNs or proxies before processing the request.
Fix scheduling bugs instantly. Never worry about time zones again; simply use convert_timezone to normalize times across global users.
Enrich your data pipelines. When you need context, run get_asn to understand which network infrastructure owns an IP range, adding critical detail to your reports.
Handle client variation easily. Instead of writing complex regex for browser types, let the agent use get_user_agent to parse device metadata automatically.
See it in action
Vetting a user submission from an unknown IP
A security analyst receives an alert about an unusual login. Instead of manual lookups, the agent first runs get_ipgeo to determine the country and coordinates. Next, it uses get_security to check if the IP is flagged as a Tor node or proxy before alerting the team.
Building an international scheduling tool
A developer needs to schedule a meeting that spans New York and Tokyo. The agent first uses get_timezone on both locations, then uses convert_timezone to calculate the precise overlap window, guaranteeing correct time display for all users.
Auditing web form data
A data scientist is cleaning up user-submitted forms. They use bulk_user_agent on a batch of submissions and then run get_ipgeo to tag the dataset with precise location context, making analysis much richer.
Debugging network logs
A DevOps engineer is troubleshooting a connection error. They use get_asn on the failed IP address to identify the owning network provider and then run get_abuse to find who they need to contact about the issue.
The honest tradeoffs
Assuming time zones are consistent
The developer assumes that if a user is in London, it's always GMT. They hardcode 'UTC+0' for all dates and see scheduling errors when users travel during daylight savings.
Always let the agent use get_timezone first to confirm the correct zone identifier (e.g., 'Europe/London'), then use convert_timezone to handle any date shifts or DST changes reliably.
Treating all IPs equally
The system accepts an IP address and immediately trusts its location, failing to check if it's a known data center proxy. This leads to false positives in threat analysis.
Before using get_ipgeo, always run the IP through get_security first. If the score is high or it flags as a VPN/Proxy, you can treat the resulting location data with caution.
Writing complex parsing logic
The engineer writes massive regex patterns in their code base to figure out if a user's browser is Chrome on Windows or Safari on MacOS. This code breaks every time Apple updates something.
Just let the agent run get_user_agent. It handles the parsing of complex strings and gives you clean, readable metadata about the device and OS in one shot.
When It Fits, When It Doesn't
Look, this MCP is your Swiss Army knife for network context. Use it if your problem involves anything related to location, time, or identity derived from an IP address or browser string. For instance, you need to know a user's city? Use get_ipgeo. You suspect fraud? Run through get_security and maybe check the ASN with get_asn. If the issue is scheduling across continents, convert_timezone is your only bet.
Don't use this if you simply need to validate a user-provided string against a simple list (e.g., checking an email format). For that, a standard validation library works fine. Also, don't try to use it to determine the intent of a user; it only reads data points. If your issue is pure application logic flow, stick to your existing code base. The key boundary here is: if you need external, real-time network information, this MCP solves it.
Questions you might have
How do I use get_ipgeo with an IP address? +
You simply tell your agent to 'get the location for 8.8.8.8.' The tool handles the lookup, returning precise city, country, and coordinate data.
Can I check multiple IPs at once using bulk_security? +
Yep. Use bulk_security when you have a list of IPs (like from a CSV file). It runs the threat check on every IP in the batch and returns a summary for all of them.
What is the difference between get_ipgeo and get_timezone? +
Geo provides where an IP is (country, city), while get_timezone tells you the correct time zone identifier (like 'America/Los_Angeles') for that location.
When should I use convert_timezone? +
Use it whenever a conversation or data point involves two different locations. It calculates the exact corresponding time, preventing scheduling errors.
How does get_user_agent help with client identification? +
get_user_agent takes a browser string and breaks it into structured parts, telling you the device type (e.g., mobile) and the operating system that generated it.
What happens if I make too many calls using `get_ipgeo`? +
You will encounter a rate limit error. The API response includes an HTTP status code and often specifies when you can retry the request. Always manage your calling volume to avoid service interruptions.
When should I use `get_asn` instead of general IP location data? +
Use it when network ownership matters more than geography. While basic lookups give you a city, running get_asn gives you the Autonomous System Number, which identifies the specific organization that owns the entire block of IP addresses.
How do I find out who to contact if an IP address is causing problems? +
Use the get_abuse tool. This retrieves the designated abuse contact information for a given IP range or block. It lets you report network issues directly to the right party, bypassing general support channels.
Can I detect if an IP address is a VPN or a security risk? +
Yes. Use the get_security tool to retrieve a threat score and detect if the IP belongs to a VPN, Proxy, or Tor network. You can also use bulk_security for multiple IPs.
How do I find the local time for a specific IP address? +
Simply use the get_timezone tool with the target IP. It will return the current time, date, and full timezone details for that specific geographical location.
Can I look up ASN information for a network? +
Yes, the get_asn tool provides detailed information about Autonomous System Numbers, including routes and WHOIS responses for a specific ASN or IP.
We've already built the connector for IPGeolocation.io. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 11 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.