IP Geolocation API
Enrich requests with city-level IP geolocation and VPN, proxy, or Tor signals from inside your agent workflow.
Overview
io.github.Br0ski777/ip-geolocation is a MCP server for the Build phase that returns IP geolocation plus ISP, ASN, and VPN, proxy, or Tor detection via remote SSE with x402.
What is this MCP server?
- IP geolocation with city-level and ISP or ASN context
- VPN, proxy, and Tor detection flags for risk-aware flows
- Remote MCP SSE at ip-geolocation.api.klymax402.com
- x402 micropayment on the hosted geolocation API
- Version 1.1.0 server with GitHub source ip-geolocation-x402
- MCP server version 1.1.0
- 1 remote SSE endpoint: ip-geolocation.api.klymax402.com/mcp
- Detection classes include VPN, proxy, and Tor per server description
What problem does it solve?
You need IP location and anonymizer hints in your product but do not want to integrate a full geo vendor SDK before your backend MVP works.
Who is it for?
Builders shipping SaaS or APIs who want fast IP context and basic threat signals inside agent-driven backend work.
Skip if: Enterprises requiring guaranteed accuracy, on-prem geo databases, or compliance-certified fraud platforms without third-party remotes.
What do I get? / Deliverables
Your agent can query IP intelligence through MCP so you can prototype geo-aware features, logging, and abuse checks during backend development.
- Structured geolocation and network metadata for IPs
- VPN, proxy, and Tor detection signals for risk branching
Recommended MCP Servers
Journey fit
Geolocation and risk signals are wired into APIs, auth, and analytics while you implement backend behavior, before launch-scale fraud ops. Backend integrations need IP context for localization, rate limits, compliance hints, and abuse detection without bolting on a separate research sprint.
How it compares
Pay-per-call geolocation MCP tool, not a self-hosted MaxMind import or full fraud suite.
Common Questions / FAQ
Who is io.github.Br0ski777/ip-geolocation for?
Solo builders and small teams using MCP agents to add IP geolocation and VPN or proxy awareness to backends and internal tools.
When should I use io.github.Br0ski777/ip-geolocation?
Use it while building auth, analytics, or rate-limiting features when you need quick city and ISP context plus Tor or VPN hints.
How do I add io.github.Br0ski777/ip-geolocation to my agent?
Register https://ip-geolocation.api.klymax402.com/mcp as a remote SSE MCP server in your client and configure x402 micropayment per Klymax402 guidance.