Rocky Geo Mcp

What is Rocky Geo Mcp?

A Model Context Protocol (MCP) server that wraps the RockyGeo IP geolocation API on RapidAPI. It lets MCP-compatible clients like Claude Desktop or Claude Code perform IPv4/IPv6 geolocation lookups via tool calls.

How to use Rocky Geo Mcp?

Install with npm install && npm run build, then configure the RAPIDAPI_KEY environment variable (or pass via --api-key). Add the server to your MCP client config (e.g., claude_desktop_config.json) using the node command pointing at the built dist/index.js file.

Key features of Rocky Geo Mcp

• Single‑IP geolocation via lookup_ip tool
• Batch geolocation (1–100 IPs) via lookup_ips_batch
• Health check endpoint (health_check) returning status and data version
• Supports both IPv4 and IPv6 addresses
• Configurable base URL for self‑hosted RockyGeo instances
• Private/reserved IPs return { found: false }

Use cases of Rocky Geo Mcp

• Look up the geographical location of an IP address for security analysis
• Enrich log data by batch‑geolocating multiple IPs at once
• Verify connectivity and data freshness of the geolocation service

FAQ from Rocky Geo Mcp

How do I handle private or reserved IP addresses?

The server returns { found: false } for private or reserved IPs, indicating no geolocation data is available.

What is the batch size limit for IP lookups?

The lookup_ips_batch tool accepts between 1 and 100 IP addresses per call.

Is an API key required?

Yes, a RapidAPI key (RAPIDAPI_KEY) is required and must be set either as an environment variable or passed with --api-key. The free RapidAPI plan allows 1 request per second.

Can I use a self‑hosted RockyGeo backend?

Yes, set the ROCKYGEO_BASE_URL environment variable to point at your own instance. The default is https://rocky-geo.p.rapidapi.com/v1.

How are tests run?

End‑to‑end integration tests are in tests/integration.test.js and can be run with npm test. They hit the live RockyGeo API, so they consume RapidAPI quota and may be rate‑limited on the free plan.