# io.github.cyanheads/nominatim-mcp-server (remote · nominatim.caseyjhand.com) Geocode, reverse geocode, and run Overpass spatial queries on OpenStreetMap data. - Trust score: 67/100 (medium) - Change this week: +5 - Registry status: active - Liveness: degraded - Owner verified: no - Last scored: 2026-08-03 > **Degraded**: one or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down. ## Components - remote · `nominatim.caseyjhand.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/cyanheads-nominatim-mcp-server/nominatim.md), [page](https://verifymcp.io/servers/cyanheads-nominatim-mcp-server/nominatim) - npm · `@cyanheads/nominatim-mcp-server`: 15/100, [markdown](https://verifymcp.io/servers/cyanheads-nominatim-mcp-server/cyanheads-nominatim-mcp-server.md), [page](https://verifymcp.io/servers/cyanheads-nominatim-mcp-server/cyanheads-nominatim-mcp-server) ## Channel facts - Endpoint: `https://nominatim.caseyjhand.com/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `0.1.8` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-08-03. - **Endpoint Security**: 66/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC is configured correctly; the domain's records validate against the full chain to the root. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 60/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 2885 tokens (~480/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 27/100 - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### Claude ```bash claude mcp add --transport http cyanheads-nominatim-mcp-server https://nominatim.caseyjhand.com/mcp ``` ### Codex ```toml [mcp_servers.cyanheads-nominatim-mcp-server] url = "https://nominatim.caseyjhand.com/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "cyanheads-nominatim-mcp-server": { "type": "remote", "url": "https://nominatim.caseyjhand.com/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add cyanheads-nominatim-mcp-server --url https://nominatim.caseyjhand.com/mcp --transport streamable-http ``` ### Hermes ```yaml mcp_servers: cyanheads-nominatim-mcp-server: url: "https://nominatim.caseyjhand.com/mcp" ``` ### Other ```json { "mcpServers": { "cyanheads-nominatim-mcp-server": { "type": "http", "url": "https://nominatim.caseyjhand.com/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-08-03 (score 67, 0) - [security] Tool “openstreetmap_query_raw” rewrote its description, which is the text the model reads - [functional] Server version: 0.3.4 → 0.3.6 - [cosmetic] “openstreetmap_query_raw” added an optional parameter “offset” - [cosmetic] “openstreetmap_query_raw” added an optional parameter “limit” - [cosmetic] “openstreetmap_query_raw” reworded the description of “timeout_seconds” ### 2026-08-02 (score 67, +1) No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-31 (score 66, +2) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-30 (score 64, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-29 (score 63, +1) No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-27 (score 62, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-26 (score 61) First indexed and scored. ## MCP tools (6) ### `openstreetmap_search_places` (~694 tokens) Geocode a place name or address Convert a place name or address to geographic coordinates and structured place data via Nominatim/OpenStreetMap. Accepts either a free-form query string (e.g., "Space Needle Seattle") or structured address fields (street, city, state, etc.) — the two modes are mutually exclusive. Returns results ordered by Nominatim relevance (importance score). Use countrycodes to restrict results to specific countries. For exhaustive POI lists in an area, use openstreetmap_query_nearby or openstreetmap_query_bbox instead — Nominatim search returns best matches, not all matching objects. Input parameters: - `city` (string): City name (structured query). - `country` (string): Country name or ISO 3166-1 alpha-2 code (structured query). - `countrycodes` (string): Restrict results to one or more countries. Comma-separated ISO 3166-1 alpha-2 codes (e.g., "us,ca"). Preferred over the structured country field when filtering. - `county` (string): County or district (structured query). - `exclude_place_ids` (array): OSM refs (N/W/R + id) or Nominatim place_ids to drop from results, forwarded as the exclude_place_ids parameter. Pass the nextExcludeIds value from a prior truncated response to page toward the next-… - `extratags` (boolean): Include extra OSM tags when available (e.g., phone, website, opening_hours, wikidata). Increases response size. - `featureType` (string): Restrict results to a geographic feature type. Automatically implies the address layer. - `language` (string): Preferred language for result names (BCP 47 code or Accept-Language string, e.g., "en", "de", "fr,en"). Defaults to local OSM language. - `layer` (string): Filter by data layer. Comma-separated values: address, poi, railway, natural, manmade. Default: no restriction. - `limit` (integer): Maximum results to return. Nominatim may return fewer when additional results do not sufficiently match. Max 40. - `postalcode` (string): Postal or ZIP code (structured query). - `query` (string): Free-form search string (e.g., "Space Needle Seattle" or "1600 Pennsylvania Ave NW, Washington DC"). Cannot be combined with structured address fields. Keep the query to a POI name plus its city or r… - `state` (string): State or province (structured query). - `street` (string): House number and street name (structured query). Use with city/state/country fields. Cannot be combined with query. Output parameters: - `attribution` (string): Required data attribution: Data © OpenStreetMap contributors, ODbL 1.0. - `cap` (number): The limit applied to this request. - `effectiveQuery` (string): The effective query sent to Nominatim — the free-form query string, or a reconstructed string from the provided structured address fields. - `nextExcludeIds` (array): Accumulated exclude tokens (prior excludes plus this page) to pass as exclude_place_ids on the next call, retrieving the next-best matches. Each token is a stable OSM ref (N/W/R + osm_id) when the re… - `notice` (string): Guidance for this page, covering two cases: results were capped at limit (truncated is true — keep paging with nextExcludeIds), or an exclude_place_ids paging walk is exhausted and the page came back… - `results` (array): Geocoding results, ordered by Nominatim relevance (importance score descending). - `shown` (number): Number of results returned. - `total` (number): Number of results returned. - `truncated` (boolean): True if the result count equals the requested limit (Nominatim may have more). ### `openstreetmap_reverse_geocode` (~272 tokens) Reverse geocode coordinates to an address Convert latitude/longitude coordinates to the nearest address or place name via Nominatim/OpenStreetMap. Returns the closest matching OSM object at the given coordinates. Note: Nominatim finds the nearest indexed OSM object — in dense areas this may differ from the address at the exact coordinate. Use zoom=18 for building-level accuracy, lower zoom values for coarser resolution (e.g., zoom=10 for city-level). Input parameters: - `extratags` (boolean): Include extra OSM tags when available (phone, website, opening_hours, wikidata, etc.). - `language` (string): Preferred language for the result (BCP 47 code or Accept-Language string). - `lat` (number, required): Latitude in WGS84 decimal degrees. - `layer` (string): Restrict which OSM layer is matched. Comma-separated: address, poi, railway, natural, manmade. Default: address,poi. - `lon` (number, required): Longitude in WGS84 decimal degrees. - `zoom` (integer): Address detail level, roughly corresponding to map zoom. 18=building, 16=street, 14=neighbourhood, 12=town, 10=city, 8=county, 5=state, 3=country. Output parameters: - `attribution` (string): Required data attribution. - `result` (object): The closest matching OSM object at the given coordinates. ### `openstreetmap_lookup_objects` (~232 tokens) Look up address details for OSM objects by ID Fetch address details for one or more known OSM objects by their IDs via Nominatim. Each ID must be prefixed with N (node), W (way), or R (relation), e.g., "N240109189", "W50637691", "R146656". Up to 50 IDs per call. Use when an OSM ID is already known from a prior openstreetmap_query_nearby or openstreetmap_query_bbox result — this is more efficient than a geocoding round trip to get the full Nominatim address record. Input parameters: - `extratags` (boolean): Include extra OSM tags (phone, website, wikidata, etc.). - `language` (string): Preferred language for names (BCP 47 code). - `osm_ids` (array, required): OSM IDs to look up, each prefixed with N (node), W (way), or R (relation). Always an array, including for a single ID: ["N240109189"], ["W50637691", "R146656"]. Up to 50 IDs per call. Output parameters: - `attribution` (string): Required data attribution: Data © OpenStreetMap contributors, ODbL 1.0. - `not_found` (array): OSM IDs from the request that returned no result. - `results` (array): Address details for the requested OSM IDs that were found. - `total` (number): Number of results returned. ### `openstreetmap_query_nearby` (~545 tokens) Find OSM features near a point Find OSM features within a radius around a geographic point via the Overpass API. The primary tool for "what's near X?" spatial queries. Use amenity for common POI types (hospital, pharmacy, restaurant, cafe, school, atm, etc.) or tag_key + tag_value for other OSM categories (leisure=park, shop=supermarket, natural=peak). Exactly one of amenity or tag_key/tag_value must be provided. Results include all element types specified (nodes cover standalone POIs, ways cover buildings and areas), each with its full OSM tag set, sorted nearest-first by distance_meters from the center point. The extratags flag is not needed here — it applies only to the Nominatim-backed openstreetmap_search_places, openstreetmap_reverse_geocode, and openstreetmap_lookup_objects tools. Input parameters: - `amenity` (string): OSM amenity tag value (e.g., "hospital", "pharmacy", "restaurant", "school", "atm"). Shortcut for tag_key="amenity". Cannot be combined with tag_key/tag_value. - `element_types` (array): OSM element types to search. Ways cover most buildings and areas; nodes cover most standalone POIs. Add "relation" for complex structures like large campuses. - `lat` (number, required): Center latitude in WGS84 decimal degrees. - `limit` (integer): Maximum results to return. Applied after the Overpass query — if the area has more features, they are truncated. - `lon` (number, required): Center longitude in WGS84 decimal degrees. - `offset` (integer): Number of matching features to skip before applying limit, for paging through a large result set. Features are distance-sorted before paging, so higher offsets return progressively farther matches; t… - `radius_meters` (number): Search radius in meters. Max 50,000m (50km). Keep under 5,000m for dense urban POI queries to avoid slow responses. - `tag_key` (string): OSM tag key for non-amenity queries (e.g., "leisure", "shop", "highway", "natural"). Use with tag_value. Cannot be combined with amenity. - `tag_value` (string): OSM tag value paired with tag_key (e.g., "park", "supermarket", "primary", "peak"). - `timeout_seconds` (integer): Overpass query timeout in seconds. Increase for large radius or dense areas. Output parameters: - `attribution` (string): Required data attribution: Data © OpenStreetMap contributors, ODbL 1.0. - `data_timestamp` (string): OSM data freshness timestamp from the Overpass response. Absent when the endpoint reported no freshness metadata. - `effectiveTag` (string): The OSM tag filter applied (key=value, e.g. "amenity=cafe" or "leisure=park"). - `elements` (array): Matching OSM features, up to the limit. - `nextOffset` (number): Offset to pass on the next call to retrieve the following page of features. Present only when more features remain beyond this page. - `notice` (string): Guidance when the page came back empty. Distinguishes a query that matched nothing (try a larger radius or different tag) from an offset past the end of a non-empty result set (retry at a lower offse… - `servingEndpoint` (string): Overpass endpoint that produced this response, as origin and path. Differs from the first configured endpoint when a mirror answered after the primary failed, and names the endpoint that served a cac… - `totalFound` (number): Total features returned by Overpass before limit truncation. - `truncated` (boolean): True if results were cut at the limit. Reduce radius, add more specific tags, or page with offset to retrieve the rest. ### `openstreetmap_query_bbox` (~543 tokens) Find OSM features within a bounding box Find OSM features within a rectangular geographic area (bounding box) via the Overpass API. Useful for area surveys where you want everything in a region, not proximity searches. Use amenity for common POI types (hospital, pharmacy, cafe, school, etc.) or tag_key + tag_value for other OSM categories (leisure=park, shop=supermarket, natural=peak). Exactly one of amenity or tag_key/tag_value must be provided. Every feature includes its full OSM tag set; the extratags flag (used by the Nominatim-backed openstreetmap_search_places, openstreetmap_reverse_geocode, and openstreetmap_lookup_objects tools) does not apply here. For proximity searches centered on a point, use openstreetmap_query_nearby instead. Input parameters: - `amenity` (string): OSM amenity tag value shortcut (e.g., "cafe", "bench", "hospital"). Cannot be combined with tag_key/tag_value. - `east` (number, required): Eastern boundary longitude (maximum longitude). A value below west describes an antimeridian crossing rather than an inverted box. - `element_types` (array): OSM element types to search. Ways cover most buildings and areas; nodes cover most standalone POIs. Add "relation" for complex structures. - `limit` (integer): Maximum results to return. Applied after the Overpass query — if the area has more features, they are truncated. - `north` (number, required): Northern boundary latitude (maximum latitude). - `offset` (integer): Number of matching features to skip before applying limit, for paging through a large result set. The full match set is fetched and cached ~10 minutes keyed by the query, so re-paging at a new offset… - `south` (number, required): Southern boundary latitude (minimum latitude). - `tag_key` (string): OSM tag key for non-amenity queries (e.g., "leisure", "shop", "natural"). Use with tag_value. Cannot be combined with amenity. - `tag_value` (string): OSM tag value paired with tag_key (e.g., "park", "supermarket", "peak"). - `timeout_seconds` (integer): Overpass query timeout in seconds. Increase for large bounding boxes or dense areas. - `west` (number, required): Western boundary longitude (minimum longitude). A west greater than east is valid, not an error: Overpass reads it as an antimeridian-crossing box and returns the union of west..180 and -180..east. Output parameters: - `attribution` (string): Required data attribution: Data © OpenStreetMap contributors, ODbL 1.0. - `data_timestamp` (string): OSM data freshness timestamp from the Overpass response. Absent when the endpoint reported no freshness metadata. - `effectiveTag` (string): The OSM tag filter applied (key=value, e.g. "amenity=cafe" or "leisure=park"). - `elements` (array): Matching OSM features within the bounding box, up to the limit. - `nextOffset` (number): Offset to pass on the next call to retrieve the following page of features. Present only when more features remain beyond this page. - `notice` (string): Guidance when the page came back empty. Distinguishes a query that matched nothing (try a different bounding box or tag) from an offset past the end of a non-empty result set (retry at a lower offset… - `servingEndpoint` (string): Overpass endpoint that produced this response, as origin and path. Differs from the first configured endpoint when a mirror answered after the primary failed, and names the endpoint that served a cac… - `totalFound` (number): Total features returned by Overpass before limit truncation. - `truncated` (boolean): True if results were cut at the limit. Reduce bbox area, add more specific tags, or page with offset to retrieve the rest. ### `openstreetmap_query_raw` (~462 tokens) Execute a raw Overpass QL query Execute a raw Overpass QL query for advanced spatial queries that the convenience tools do not cover. Use for multi-type queries, union queries, relation membership, historical queries, or any operation requiring full Overpass QL expressiveness. The query must include [out:json]. Example: "[out:json][timeout:15];node[\"natural\"=\"peak\"](47.5,-122.5,47.7,-122.2);out body;" Returns one page of the result set: use limit and offset to page through it, and read totalFound and truncated to see how much the query matched. Validate complex queries at overpass-turbo.eu before use. For simple "what's near X?" or "what's in this area?" queries, use openstreetmap_query_nearby or openstreetmap_query_bbox instead. Input parameters: - `limit` (integer): Maximum elements to return. Applied after the Overpass query — if the query matched more, they are truncated. - `offset` (integer): Number of matching elements to skip before applying limit, for paging through a large result set. The full match set is fetched and cached ~10 minutes keyed by the query, so re-paging at a new offset… - `query` (string, required): Overpass QL query string. Must include [out:json]. The server sets the endpoint and User-Agent; do not include those. Example: "[out:json][timeout:15];node[\"natural\"=\"peak\"](47.5,-122.5,47.7,-122… - `timeout_seconds` (integer): Query timeout in seconds, bounding how long Overpass itself spends on the query. The [timeout:N] directive in the query string takes precedence if present. The client waits for what is requested here… Output parameters: - `attribution` (string): Required data attribution: Data © OpenStreetMap contributors, ODbL 1.0. - `data_timestamp` (string): OSM data freshness timestamp from the Overpass response. Absent when the endpoint reported no freshness metadata. - `effectiveQuery` (string): The Overpass QL string as sent to the API (after any timeout injection). - `elements` (array): Raw Overpass API response elements for this page, up to the limit. Structure varies by query type — nodes have lat/lon, ways have nodes[], relations have members[]. - `nextOffset` (number): Offset to pass on the next call to retrieve the following page of elements. Present only when more elements remain beyond this page. - `notice` (string): Guidance when the page came back empty. Distinguishes a query that matched nothing (check syntax or broaden the filter) from an offset past the end of a non-empty result set (retry at a lower offset)… - `servingEndpoint` (string): Overpass endpoint that produced this response, as origin and path. Differs from the first configured endpoint when a mirror answered after the primary failed, and names the endpoint that served a cac… - `totalFound` (number): Total elements returned by Overpass before limit truncation. - `total_elements` (number): Number of elements returned on this page. See totalFound for the full match count. - `truncated` (boolean): True if elements were cut at the limit. Narrow the query, or page with offset to retrieve the rest. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cyanheads-nominatim-mcp-server/nominatim#diagnostics ## Score history - 2026-08-03: 67 - 2026-08-02: 67 - 2026-08-01: 66 - 2026-07-31: 66 - 2026-07-30: 64 - 2026-07-29: 63 - 2026-07-28: 62 - 2026-07-27: 62 - 2026-07-26: 61 ## Links - Remote endpoint: https://nominatim.caseyjhand.com/mcp - Changelog RSS feed: https://verifymcp.io/servers/cyanheads-nominatim-mcp-server/nominatim/changelog.xml - Changelog JSON feed: https://verifymcp.io/servers/cyanheads-nominatim-mcp-server/nominatim/changelog.json - HTML version of this page: https://verifymcp.io/servers/cyanheads-nominatim-mcp-server/nominatim