Home / MCP registry index / dev.geocodeai/geocode

Geocode AI

dev.geocodeai/geocode in the official MCP registry. Endpoint https://geocodeai.dev/mcp.

The registry describes it as: Administrative boundaries for every place on Earth: search, reverse lookup, polygons, areas.

We read its 43 tools on 2026-11-03. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http geocode https://geocodeai.dev/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "geocode": {
      "url": "https://geocodeai.dev/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"geocode","type":"http","url":"https://geocodeai.dev/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

search_boundaries get_boundary export_boundary reverse_boundaries list_children contains_points union_boundaries create_area get_account update_profile get_usage list_api_keys create_api_key revoke_api_key get_email_preferences update_email_preferences list_orgs list_members list_teams list_invites list_audit_log save_file list_files get_file update_file delete_file share_file unshare_file get_subscription create_checkout_link get_billing_link list_feedback get_feedback list_my_feedback request_feature report_issue upvote_feedback remove_feedback_vote comment_on_feedback list_reviews get_my_review submit_review get_pricing

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-03): e1ced095025c0f81. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/dev-geocodeai-geocode/badge.svg)](https://lazaretto.dev/mcp-registry/dev-geocodeai-geocode)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.