Geonames
NPM · @PIPEWORX/MCP-GEONAMES · 2 COMPONENTS
GeoNames MCP — GeoNames geographical database API
Available components
Last scanned (1 hour ago)
Scores higher than 72% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-geonames). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 799 tokens (~199/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 +2
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-geonames@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-geonames |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-geonames/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637323375 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f02b5bf40ae507b5d1a84f03248d4de7e924dfec1895456d2a9eef0329c3e39663459577824cb54122aa60f409ae316412f7f5430ebb46d99d1be75fa |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_postal_codes ~220
Look up postal/ZIP codes and places by each other. Pass "postal_code" (+ country) to find the place(s) a code maps to ("what city is ZIP 90210"); or pass "place" (+ country) to find the postal codes for a place name ("postal codes for Paris"). Returns place name, country, admin region (state/county), postal code, and coordinates.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | GeoNames username |
| country | string | – | ISO 3166-1 alpha-2 country code (e.g. "US", "FR"). Strongly recommended — codes and place names repeat across countries. |
| limit | number | – | Max results (default 10, max 100). |
| place | string | – | Place name to find postal codes for (e.g. "Paris", "Springfield"). Use instead of postal_code. |
| postal_code | string | – | Postal/ZIP code to look up (e.g. "90210", "75001"). Provide country for accuracy. |
No output schema declared.
No examples provided.
get_nearby ~121
Find places near a given latitude/longitude. Returns nearby cities, landmarks, and features sorted by distance. Example: get_nearby(48.8566, 2.3522) for places near Paris.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | GeoNames username |
| lat | number | yes | Latitude (e.g., 48.8566) |
| lng | number | yes | Longitude (e.g., 2.3522) |
| radius | number | – | Search radius in km (default: 10, max: 300) |
No output schema declared.
No examples provided.
get_timezone ~103
Get timezone information for a latitude/longitude location. Returns timezone ID, GMT offset, DST offset, current local time, sunrise, and sunset. Example: get_timezone(40.7128, -74.0060) for New York.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | GeoNames username |
| lat | number | yes | Latitude (e.g., 40.7128) |
| lng | number | yes | Longitude (e.g., -74.0060) |
No output schema declared.
No examples provided.
search_geonames ~301
Search for places (cities, towns, landmarks, regions) by name and get which STATE / PROVINCE / COUNTY / PREFECTURE / administrative division (German Bundesland, UK county, Canadian province, Japanese prefecture, Indian/Australian/Mexican state, etc.) they are in, plus country, coordinates, population, and feature type. Answers "what state is <city> in", "which US/German/Australian state is <city> in", "what province/county/prefecture/region is <place> in" — the `admin_region` field is the state/province/county/prefecture (e.g. search_geonames("Naperville", "US") → Illinois; ("Heidelberg", "DE") → Baden-Württemberg; ("Leeds", "GB") → England; ("Osaka", "JP") → Osaka). Worldwide coverage. Example: search_geonames("Paris", "FR"). Use get_nearby to find places near a known location.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | GeoNames username |
| country | string | – | ISO 3166-1 alpha-2 country code to filter (e.g., "US", "JP") |
| limit | number | – | Number of results (default: 10, max: 100) |
| query | string | yes | Place name to search for (e.g., "Tokyo", "Grand Canyon") |
No output schema declared.
No examples provided.
How do I install the Geonames MCP server?
Geonames runs locally as an npm package, launched with npx -y @pipeworx/mcp-geonames. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-geonames
claude mcp add pipeworx-io-geonames -- npx -y @pipeworx/mcp-geonames
What is the Geonames MCP server?
Geonames is an MCP server listed in the public MCP registry as io.github.pipeworx-io/geonames. GeoNames MCP, GeoNames geographical database API. This page covers its npm package (@pipeworx/mcp-geonames).
Is the Geonames MCP server safe to use?
Geonames scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Geonames MCP server expose?
Geonames exposes 4 tools: search_geonames, get_nearby, get_timezone, find_postal_codes. Their descriptions and schemas cost roughly 745 tokens of context every time the server is loaded.
Is the Geonames MCP server still maintained?
Geonames is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Geonames MCP server under?
Geonames declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.