MCP servers › dev.geocodeai › geocode

MCP server · registry snapshot 2026-11-06 · last tested 2026-11-06

geocode MCP server

Registry name dev.geocodeai/geocode

Geocode AI — the publisher's title

by geocodeai.dev · domain (the registry's namespace rule)npm ↗Website ↗

Administrative boundaries for every place on Earth: search, reverse lookup, polygons, areas. — the publisher's description

4 of 6 record checks metRead-only · tools listed 2026-11-06version 1.0.2MITstandard input/output, streamable HTTP43 tools

Summary

dev.geocodeai/geocode is a remote and local MCP server listed in the official MCP registry at version 1.0.2, under the namespace of the domain geocodeai.dev. On 2026-11-06 ProtocolProbe connected to it in read-only mode and read its inventory: 43 tools, 1 resource and 0 prompts.

Record checks

4 of 6 record checks met · 3 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
not met: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#1,893 of 18,557 packages by monthly downloads, tied with 1 other
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs: remote and local package
Transport: standard input/output, streamable HTTP
Your own values: none declared (not a guarantee)
Sign-in: none needed to open a session
Package: npm · listed version current
License: MIT
Dependencies: no known high or critical advisories
Tools: 43
Last tested: 2026-11-06

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-06 (geocodeai.dev), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.2).

Add to your client

Observed fact

This server accepted a session without any credential and lists 15 tools whose name or declaration suggests they change data (create_area, update_profile, create_api_key, revoke_api_key, update_email_preferences and 10 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-06.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-11-06

Mode

read-only (no tool calls)

Latest version

1.0.2, published 2026-11-05 (registry, as of the 2026-11-06 snapshot)

First listed version

2026-11-03 (earliest version still in the registry; older removed versions would be earlier)

Version history

3 versions listed, 2026-11-03 to 2026-11-05; 3 in the 90 days before the 2026-11-06 snapshot.

Most recent 3 versions

1.0.2 · 2026-11-05
1.0.1 · 2026-11-03
1.0.0 · 2026-11-03

(versions still listed in the registry only)

Registry data

snapshot 2026-11-06

Package and repository

checked 2026-11-06

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn. Does not apply: repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.0.1 (published 2026-11-03) → 1.0.2 (published 2026-11-05), between the registry lists of 2026-11-05 and 2026-11-06.

No release note: the registry entry links no GitHub repository.

Source: the official MCP Registry list on 2026-11-05 and on 2026-11-06; release notes from the GitHub Releases API, checked 2026-11-06.

What it is

What does this server offer?

Observed inventory

43tools

1resources

0prompts

None of its 43 tools are described as changing anything. For 43 the reading was uncertain, so no mark is shown.

search_boundaries
“Finds administrative boundaries (countries, states, counties, cities, districts) and postcode areas by name, in any language.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
6 inputs, 1 required
- qstringrequired“A place name, e.g.”
- countrystring“Limit to countries: ISO 3166-1 alpha-2, comma-separated (e.g.”
- kindstring“Only this kind (normalized across countries): country, state, region, province, county, district, municipality, city, borough, ward, neighbourhood, postal_code.”
- admin_levelinteger“Only this OSM admin_level (2 = country; meaning varies by country below that).”
- nearstring“lat,lon to prefer results near, e.g.”
- limitinteger“At most this many results (1–40, default 10).”
get_boundaryon 2 other servers
“Returns one boundary as a GeoJSON Feature: its polygon at a chosen detail plus properties (name, kind, admin_level, parents, bbox, area_km2, population, wikidata).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 2 required
- idstringrequired“Boundary id: r<OSM relation id> (e.g.”
- detailstring“Simplification relative to the boundary's size: low (~1,000 points across; the default without a key), medium (the default with a key, ~5,000), high (~25,000),…”
- precisioninteger“Coordinate decimals (3–7).”
- includearrayrequired“Comma-separated extras: parents, children.”
export_boundary
“Builds a boundary's polygon as a file (geojson, kml, wkt, svg or gml) at a detail level and returns a permanent public URL on our CDN; the REST route redirects straight to it.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
3 inputs, 1 required
- idstringrequired“Boundary id: r<OSM relation id> (e.g.”
- formatstring“geojson (a Feature), kml, wkt, svg or gml.”
- detailstring“Simplification relative to the boundary's size: low (~1,000 points across, maps and previews), medium (default, ~5,000), high (~25,000), full (unsimplified OSM…”
reverse_boundaries
“Every administrative boundary containing a point, country first down to the smallest district, plus postcode areas.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
- latnumberrequired“Latitude, -90 to 90.”
- lonnumberrequired“Longitude, -180 to 180.”
list_children
“The direct subdivisions of a boundary: a country's states, a state's counties, a city's districts.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- idstringrequired“Boundary id: r<OSM relation id> (e.g.”
- admin_levelinteger“Subdivision admin_level; default: the next level below the parent that exists.”
contains_points
“Tests up to 10,000 points ([lon, lat] pairs) against one boundary and returns a boolean per point plus the inside count.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
- idstringrequired“Boundary id: r<OSM relation id> (e.g.”
- pointsarrayrequired“Points as [lon, lat] (GeoJSON order).”
union_boundaries
“Merges boundaries into one polygon: the union of include minus the union of exclude (e.g.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 1 required
- includearrayrequired“Boundary ids to merge.”
- excludearray“Boundary ids to cut out.”
- detailstring“Simplification relative to the boundary's size: low (~1,000 points across, maps and previews), medium (default, ~5,000), high (~25,000), full (unsimplified OSM…”
create_area
“Turns a plain-language description of an area ("Alameda and Contra Costa counties excluding San Jose, plus SFO") or wording from a contract or policy into one validated land-only polygon.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
4 inputs, 1 required
- textstringrequired“The description of the area.”
- countrystring“ISO 3166-1 alpha-2 country code, if known.”
- sourcestring“Who wrote the description (agency, company).”
- seedobject“A point that must be inside the area.”
get_accounton 133 other servers
“The signed-in account and the organization the call acts in: email and profile, the organization (id, slug, name, personal or shared) and the caller's role in it (viewer, member, admin or owner), how…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
update_profileon 55 other servers
“Sets the account's name, company, use case (what you are building) and language (the language for emails and the dashboard).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
4 inputs
- namestring“Your name, used in emails ("Hey {first name},").”
- companystring“Company or project.”
- use_casestring“What you are building with boundaries and areas.”
- localestring“The language for emails and the dashboard: one of en, es, de, fr, ja, pt-BR.”
get_usageon 110 other servers
“The organization's daily usage for the last N days (default 30), by op, with cache hit counts, across every member and key.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- daysinteger“How many days back.”
list_api_keyson 28 other servers
“The organization's API keys (prefix, name, who created it, last use; never the secret).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- include_revokedboolean

Show 31 more tools

create_api_keyon 37 other servers
“Creates an API key for the organization and returns the secret once.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input
- namestring“A label, e.g.”
revoke_api_keyon 21 other servers
“Revokes an API key by id.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
1 input, 1 required
- idstringrequired“The key's id from list_api_keys.”
get_email_preferenceson 2 other servers
“Which automated emails the account receives: the global subscription and one switch per kind (getting-started notes, first boundary, usage milestones, quota warnings, check-ins, monthly digest).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
update_email_preferenceson 2 other servers
“Turns automated emails on or off: `subscribed: false` stops all of them (the same as the unsubscribe link), `subscribed: true` resubscribes, and `kinds` switches individual kinds.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
2 inputs
- subscribedboolean“false = unsubscribe from every automated email; true = resubscribe.”
- kindsobject“Per-kind switches, e.g.”
list_orgson 7 other servers
“The organizations you belong to, with your role in each and which one this call acts in (current).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
list_memberson 26 other servers
“The people in the organization: email, name, role (viewer, member, admin, owner), when they joined and their teams.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
list_teamson 19 other servers
“The organization's teams: slug, name, description and members with their team role (maintainer or member).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
list_inviteson 5 other servers
“Invitations to the organization: email, role, teams, status (pending, accepted, expired, revoked) and when they expire.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- include_closedboolean“Also list accepted, expired and revoked invites.”
list_audit_logon 3 other servers
“The organization's audit log, newest first: who (a person, an API key, an OAuth client or the system) changed membership, roles, teams, invites, API keys, billing or file sharing, and when.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
- limitinteger“Page size, at most 100.”
- offsetinteger
- actionstring“Only this action, e.g.”
save_fileon 3 other servers
“Exports a boundary (like export_boundary) and saves it in the organization's file library, so teammates find it on the dashboard and through list_files.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
5 inputs, 1 required
- boundary_idstringrequired“Boundary id, as get_boundary accepts it (r62422, wikidata:Q64, iso:US-CA…).”
- formatstring
- detailstring
- namestring“A label for the library; default: the boundary's name, format and detail.”
- visibilitystring
list_fileson 51 other servers
“The boundary files in the organization's library that you can see, newest first: org-visible ones plus restricted ones shared with you or a team you are in.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
- limitinteger“Page size, at most 100.”
- offsetinteger
get_fileon 23 other servers
“One library file: its boundary, format, detail, visibility, your access, the permanent download url and, when you can manage it, who it is shared with.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- idstringrequired“The file's id from list_files or save_file.”
update_fileon 6 other servers
“Renames a library file (write access) or sets its visibility (admin access on the file): org shares it with every member at their role, restricted keeps it to its creator, admins and explicit shares.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
3 inputs, 1 required
- idstringrequired“The file's id from list_files or save_file.”
- namestring
- visibilitystring
delete_fileon 30 other servers
“Removes a file from the organization's library and its shares (admin access on the file).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
1 input, 1 required
- idstringrequired“The file's id from list_files or save_file.”
share_fileon 7 other servers
“Shares a library file with a team (by slug or id) or a person in the organization (by email or user id) at read, write or admin access; sharing again changes the access.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
4 inputs, 1 required
- idstringrequired“The file's id from list_files or save_file.”
- teamstring“Team slug or id.”
- userstring“A member's email or user id.”
- accessstring
unshare_file
“Removes one share of a library file by its grant id (from get_file).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
2 inputs, 2 required
- idstringrequired“The file's id from list_files or save_file.”
- grant_idstringrequired
get_subscriptionon 13 other servers
“The organization's plan and subscription: plan, status, when the period renews or ends, whether it is set to cancel, the price, this month's use of every limit (units, described areas, API keys, rate…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
create_checkout_linkon 30 other servers
“A link a human opens to buy a plan (pro or business) on a Stripe page branded Geocode AI.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 1 required
- planstringrequired“The plan to buy.”
- yearlyboolean“Bill once a year: ten months' price (two months free).”
get_billing_linkon 2 other servers
“A link for the account's owner to open Stripe's Customer Portal: download invoices, change the card or billing details, switch plans, or cancel (at the end of the period already paid for).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
Takes no inputs.
list_feedbackon 7 other servers
“The feedback board: feature requests and published issues with their status and upvotes, most upvoted first (with a key, also your own private issues, and whether you voted).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
8 inputs
- kindstring“feature = feature requests, issue = bug reports.”
- statusstring“active = open, planned or in progress; closed = done, declined or duplicate.”
- sortstring“top = most upvoted, new = most recent, recent_activity = latest vote, comment or change.”
- qstring“Words to find in the title or description.”
- mineboolean or string“Only items you filed (needs a key); list_my_feedback also lists what you follow.”
- limitinteger“Page size, at most 100.”
- cursorstring“next_cursor from the previous page.”
- offsetinteger“Same as cursor, as a number.”
get_feedbackon 13 other servers
“One feedback item with its status, upvotes, comments (official team responses marked) and timeline of status changes.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- idintegerrequired“The item's id from list_feedback, request_feature or report_issue (e.g.”
list_my_feedbackon 1 other server
“What you filed (including private issues), what you follow because you voted or commented, and your review, each with its current status.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input
- limitinteger“Items per list, at most 100.”
request_featureon 8 other servers
“Files a feature request on the public board and upvotes it for you.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
3 inputs, 1 required
- titlestringrequired“What you want, in one line.”
- detailsstring“Why you need it and what you are building; concrete examples help it get planned.”
- forceboolean or string“File even when similar requests exist.”
report_issueon 27 other servers
“Reports a problem with Geocode AI: a failing or wrong API call, a wrong or missing boundary, a docs error.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
6 inputs, 1 required
- titlestringrequired“What is wrong, in one line.”
- detailsstring“What you did, what you expected and what happened.”
- request_idstring“The request_id of the failing call (same as context.request_id).”
- opstring“The op the failing call used, e.g.”
- contextobject“What we need to reproduce it.”
- forceboolean or string“File even when similar issues exist.”
upvote_feedback
“Adds your upvote to a feature request or issue (a "me too"); votes decide what gets built and fixed first, and you get an email when its status changes.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
1 input, 1 required
- idintegerrequired“The item's id from list_feedback, request_feature or report_issue (e.g.”
remove_feedback_vote
“Takes back your upvote on a feature request or issue, and stops its emails unless you filed or commented on it.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
1 input, 1 required
- idintegerrequired“The item's id from list_feedback, request_feature or report_issue (e.g.”
comment_on_feedback
“Adds context to an existing feature request or issue: your use case, another failing request id, a workaround.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
2 inputs, 2 required
- idintegerrequired“The item's id from list_feedback, request_feature or report_issue (e.g.”
- bodystringrequired“The comment.”
list_reviewson 19 other servers
“Published reviews of Geocode AI with the average rating and the distribution, and the team's response under each.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs
- sortstring“new = newest, helpful = most detailed, highest / lowest = by rating.”
- ratinginteger“Only reviews with this many stars.”
- limitinteger
- offsetinteger
get_my_review
“Your review of the product, if you posted one, with its status (published, pending a check, or hidden with the reason) and the team's response.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
Takes no inputs.
submit_reviewon 19 other servers
“Posts the human's public review of Geocode AI (1–5 stars, what they like and dislike, what they use it for), or replaces their existing one; each account has one review and earlier versions are kept.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
9 inputs, 1 required
- ratingintegerrequired“Stars, 1 to 5.”
- titlestring“A headline.”
- bodystring“The review.”
- likesstring“What works well.”
- dislikesstring“What should be better.”
- use_casestring“What they use it for.”
- display_namestring“Name shown with the review (default: first name).”
- display_companystring“Company shown with it, if they want.”
- marketing_consentboolean or string“May we quote it on our site and in marketing?”
get_pricingon 237 other servers
“Every plan with its monthly price, included units, limits (units, described areas, requests a minute, API keys), features and checkout_url, plus what each call costs in units and what works without a…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-06.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 88% of 96
Tools with a description: 100% of 43
Typical description length: 348 characters

The tool set

Counted from the listing

Tools: 43
Size of the list: about 10,935 tokens for an agent to load (characters ÷ 4)
Naming: 43 of 43 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 43 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package @meterapp/geocode

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "geocode": {
      "command": "npx",
      "args": [
        "-y",
        "@meterapp/geocode@0.2.6",
        "mcp"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "geocode": {
      "command": "npx",
      "args": [
        "-y",
        "@meterapp/geocode@0.2.6",
        "mcp"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "geocode": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@meterapp/geocode@0.2.6",
        "mcp"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"geocode","type":"stdio","command":"npx","args":["-y","@meterapp/geocode@0.2.6","mcp"]}'

Claude Code

claude mcp add --transport stdio geocode -- npx -y @meterapp/geocode@0.2.6 mcp

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "geocode": {
      "command": "npx",
      "args": [
        "-y",
        "@meterapp/geocode@0.2.6",
        "mcp"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

{
  "mcpServers": {
    "geocode": {
      "command": "npx",
      "args": [
        "-y",
        "@meterapp/geocode@0.2.6",
        "mcp"
      ]
    }
  }
}

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.geocode]
command = "npx"
args = ["-y", "@meterapp/geocode@0.2.6", "mcp"]

Zed · Zed settings file (command: zed: open settings file)

{
  "context_servers": {
    "geocode": {
      "command": "npx",
      "args": [
        "-y",
        "@meterapp/geocode@0.2.6",
        "mcp"
      ]
    }
  }
}

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @meterapp/geocode@0.2.6 mcp

Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
Optional settings the entry also lists (left out above): GEOCODE_API_KEY.
This runs the publisher's code on your machine (npx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-06 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://geocodeai.dev/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

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

VS Code · .vscode/mcp.json

{
  "servers": {
    "geocode": {
      "type": "http",
      "url": "https://geocodeai.dev/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

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

Claude Code

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

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "geocode": {
      "type": "streamableHttp",
      "url": "https://geocodeai.dev/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

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

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.geocode]
url = "https://geocodeai.dev/mcp"

Zed · Zed settings file (command: zed: open settings file)

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://geocodeai.dev/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 0.2.6
Latest stable: 0.2.6
Status: current
Withdrawn: no

Source: registry.npmjs.org · 2026-11-06. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-11-06 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha512-/FLa/bg+JSIQDrS1F…
Signature: signed
License: MIT

Source: the package registry · 2026-11-06.

Usage

Downloads: 1,412 in the last month

Source: api.npmjs.org · 2026-11-06.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint geocodeai.dev/mcp	Session opened	matches	our test · 2026-11-06
No credential declared as required	Opened a session without any credential	matches	our test · 2026-11-06
Version 0.2.6 on npm	Exists and can be installed	matches	npm · 2026-11-06

Tool list changes

Our reads compared · no tool called

Hosted endpoint geocodeai.dev/mcp

No change in the tool list across 2 reads (2026-11-04 to 2026-11-06; versions 1.0.1 to 1.0.2).

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-06 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

4 of 6 record checks met · 3 do not apply

#1,893 of 18,557 packages by monthly downloads, tied with 1 other
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-06. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about dev.geocodeai/geocode

Answered from the data above

Who publishes dev.geocodeai/geocode?

The registry ties the namespace dev.geocodeai to the domain geocodeai.dev; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Is dev.geocodeai/geocode safe to install?

We do not rate servers as safe or unsafe. 4 of its 6 applicable record checks are met (facts from public records, each listed on this page). What the records show: The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does dev.geocodeai/geocode need an API key or sign-in?

It opened a session without any credential on 2026-11-06. The registry entry declares no required credential; no declaration is not a guarantee.

Has dev.geocodeai/geocode been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Is the listed version current?

Yes. The registry lists 0.2.6, the latest stable release on npm.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-06

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 4

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 3

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-06, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
2,302 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 43 tools, 1 resource, 0 prompts.
9,238 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in a later update

listed 2026-11-06; not classified yet

Pricing modelAI-classified

pending: added in a later update

the website is not read yet

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote and local package

registry · 2026-11-06

MCP capability

resources, tools

our test · 2026-11-06

Transport

standard input/output, streamable HTTP

registry · 2026-11-06

Required credentials

none declared

registry · 2026-11-06 · no declaration is not a guarantee

Package registry

npm

registry · 2026-11-06

Freshness

0–30 days

registry updatedAt · 2026-11-06

Lifecycle status

active

registry · 2026-11-06

License class

permissive

package registry · 2026-11-06

Integrity hash

declared (sri)

package registry · 2026-11-06

Signature / provenance

signed

package registry · 2026-11-06

Dependency advisories

none known

npm audit · 2026-11-06

Popularity

1,412 downloads a month

package registry · 2026-11-06

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

either (remote or your machine)

where it runs, from the hosting type · 2026-11-06

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “dev.geocodeai/geocode: MCP server record.” Data checked 2026-11-06. https://protocolprobe.com/mcp/servers/dev.geocodeai/geocode

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/dev.geocodeai/geocode)](https://protocolprobe.com/mcp/servers/dev.geocodeai/geocode)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology