mcpField
R
Rocky Geo Mcp

Rocky Geo Mcp

Local
github.com/racccoinorgDeveloper Tools0Updated 23w ago
Repository

About Rocky Geo Mcp

Rocky Geo Mcp wraps the RockyGeo IP geolocation API hosted on RapidAPI as an MCP server. It is for MCP-compatible clients that need IPv4 or IPv6 lookups, with tools for individual and batch queries as well as health checks.

Key features

  1. 01Geolocate a single IP address
  2. 02Batch lookup 1 to 100 IPs
  3. 03Check service status and data version
  4. 04Configure the RapidAPI key and API URL

Use cases

  1. 01Look up the location of an IPv4 or IPv6 address
  2. 02Process multiple IP geolocation queries
  3. 03Check the RockyGeo API's operational status

MCP support

The MCP server exposes the `lookup_ip`, `lookup_ips_batch`, and `health_check` tools, calling the RockyGeo API through RapidAPI.

#ip#geo#api#mcp#rapidapi

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

rockygeo-mcp

MCP (Model Context Protocol) server that wraps the RockyGeo IP geolocation API hosted on RapidAPI. Lets MCP-compatible clients (Claude Desktop, Claude Code, etc.) perform IPv4/IPv6 geolocation lookups via tool calls.

Install

npm install
npm run build

Configure

VariableDefaultNotes
RAPIDAPI_KEY(required)Sent as x-rapidapi-key. Override with --api-key <k>.
ROCKYGEO_BASE_URLhttps://rocky-geo.p.rapidapi.com/v1Point at a different Rocky Geo API provider.
ROCKYGEO_RAPIDAPI_HOSTparsed from base URLSent as x-rapidapi-host for *.rapidapi.com hosts.

MCP client setup

Add to your client config (Claude Code ~/.claude.json, Claude Desktop claude_desktop_config.json, etc.):

{
  "mcpServers": {
    "rockygeo": {
      "command": "node",
      "args": ["/Users/cyborg97/rockygeomcp/dist/index.js"],
      "env": { "RAPIDAPI_KEY": "<your-key>" }
    }
  }
}

Tools

  • lookup_ip — { ip: string } → geolocation for one IP. Private/reserved IPs return { found: false }.
  • lookup_ips_batch — { ips: string[] } (1–100) → { results: { [ip]: ... } }.
  • health_check — {} → { status, dataVersion, lastSyncAt, uptime }.

Smoke test with the inspector

RAPIDAPI_KEY=<key> npx @modelcontextprotocol/inspector node dist/index.js

Then in the inspector UI: list tools, run lookup_ip with { "ip": "8.8.8.8" }.

Integration tests

End-to-end tests in tests/integration.test.js spawn the built server as a child process and exercise every tool over the real MCP stdio transport, hitting the live RockyGeo API.

npm test

If RAPIDAPI_KEY is not in the environment, the runner prompts for it (input is hidden). The runner also auto-builds dist/ if it is missing.

Note: tests hit the real upstream API, so they consume RapidAPI quota and may be rate-limited on the Free plan (1 RPS).

License

MIT.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.