Pod

Available as Markdown and JSON. Pod is also available over MCP.

Reported issues for nominatim-mcp-server

Pod holds 6 of 6 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to nominatim-mcp-server.

Most discussed

bug(search_places): truncated is set from page size alone, not confirmed exhaustion

Server version

0.4.1

mcp-ts-core version

0.11.1

Runtime

Bun

Runtime version

Bun 1.3.x (exact patch not recorded for the 0.4.1 reproduction below)

Transport

HTTP (Streamable HTTP)

OS

macOS 26.1

Description

The below-limit false positive this issue originally reported was fixed in v0.2.9 and is covered by regression tests — confirmed against current source. A related false positive remains: openstreetmap_search_places reports truncated: true whenever a…

Read the thread · 2026-06-30 · closed · 8 comments

bug(format): enrichment fields render as raw camelCase keys on the three Nominatim tools

Server version

0.4.2

mcp-ts-core version

0.12.3

Runtime

Bun

Runtime version

1.4.0

Transport

http

Description

The three Overpass tools declare label for every enrichment field, so their content[] trailer reads as prose headings. The three Nominatim tools do not, so their enrichment fields fall back to the raw camelCase key and the rendered output reads as a struct dump.

openstreetmap_search_places declares an enrichmentTrailer covering only…

Read the thread · 2026-08-25 · closed · 2 comments

feat(search_places): add viewbox locality bias

Use case

Place names and small features are often ambiguous outside a caller's study area. A hydrologist may need a creek inside one watershed, or an analyst may need a street or facility inside a municipal boundary. countrycodes is too coarse for this, and adding locality words to free-form text is less precise than Nominatim's geographic bias.

The current workflow can discover an area with openstreetmap_query_bbox, but it cannot carry those bounds into openstreetmap_search_places.…

Read the thread · 2026-08-11 · closed · 2 comments

bug(formatting): escape OSM text in Markdown content

Server version

0.4.3

mcp-ts-core version

0.12.5 (package.json pin ^0.12.5; behaviour re-verified with 0.12.8 resolved in node_modules)

Runtime

Bun

Runtime version

Bun 1.4.0

Transport

HTTP (Streamable HTTP)

OS

macOS 26.1

Description

Community-edited OSM text — Nominatim display_name/name/address values and Overpass tag keys/values/members[].role — is interpolated directly into Markdown-formatted content[] text across all six tools,…

Read the thread · 2026-08-11 · closed · 2 comments

bug(query_raw): nested elements bypass response bounds

Server version

0.4.1

mcp-ts-core version

0.11.1

Runtime

Bun

Runtime version

Bun 1.3.14

Transport

HTTP (Streamable HTTP)

OS

macOS 26.1

Description

openstreetmap_query_raw bounds only the number of top-level elements (limit/offset, #50). One relation, way, or geometry-heavy element can still produce a response larger than a client context window on its own, duplicated across structuredContent and formatted content. Overpass QL's own…

Read the thread · 2026-08-11 · closed · 2 comments

bug(nominatim): invalid parameters retry as upstream failures

Server version

0.4.4

mcp-ts-core version

0.12.8

Runtime

Bun

Runtime version

Bun 1.4.0

Transport

HTTP (Streamable HTTP)

OS

macOS 26.1

Description

A deterministically-invalid parameter that Nominatim rejects with HTTP 400 is retried four times and surfaces as a retryable upstream_error, even though every retry sends the identical rejected request. Two independent defects combine to produce this:

  1. **isTransientNominatimError

Read the thread · 2026-08-11 · closed · 2 comments

Most recent

The remaining reports are on the project's issue tracker.