@geocoding-ai/mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @geocoding-ai/mcp@1.0.1
Installing a package runs its code. Use a sandbox for anything you have not read.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
2 tools with commands in capitals or very long text
- Very long description in
geocode:3000 characters or more
- Very long description in
reverse_geocode:3000 characters or more
Common and usually harmless: it is how many makers stress how a tool should be used.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
geocode q, format, addressdetails, extratags, namedetails, layer, polygon_geojson, polygon_kml, polygon_svg, polygon_text, polygon_threshold, countrycodes, featureType
Geocoding generates a coordinate from an address.
The search API allows to look up a location from a textual description or address. Nominatim supports structured and free-form search queries.
The search query may also contain special phrases which are translated into specific OpenStreetMap (OSM) tags (e.g. Pub => amenity=pub). This can be used to narrow down the kind of objects to be returned.
Note: Special phrases are not suitable to query all objects of a certain type in an area. Nominatim will always just return a collection of the best matches.
Input:
- query: Free-form string to search for. In this form, the query can be unstructured. Free-form queries are processed first left-to-right and then right-to-left if that fails.
Commas are optional, but improve performance by reducing the complexity of the search. The free-form may also contain special phrases to describe the type of place to be returned or a coordinate to search close to a position.
- format: Format of the response. One of: xml, json, jsonv2, geojson, geocodejson. Default: jsonv2
- addressdetails: When set to 1, include a breakdown of the address into elements. The exact content of the address breakdown depends on the output format.
- extratags: When set to 1, the response include any additional information in the result that is available in the Nominatim database.
- namedetails: When set to 1, include a full list of names for the result. These may include language variants, older names, references and brand.
- countrycodes: Filter that limits the search results to one or more countries. The country code must be the ISO 3166-1alpha2 code of the country.
Each place in Nominatim is assigned to one country code based on OSM country boundaries. In rare cases a place may not be in any country at all, for example, when it is in international waters. These places are also excluded when the filter is set.
- layer: The layer filter allows to select places by themes. Comma-separated list of: address, poi, railway, natural, manmade
address: The address layer contains all places that make up an address: address points with house numbers, streets, inhabited places (suburbs, villages, cities, states etc.) and administrative boundaries.
poi: The poi layer selects all point of interest. This includes classic points of interest like restaurants, shops, hotels but also less obvious features like recycling bins, guideposts or benches.
railway: The railway layer includes railway infrastructure like tracks. Note that in Nominatim's standard configuration, only very few railway features are imported into the database.
natural: The natural layer collects features like rivers, lakes and mountains while the manmade layer functions as a catch-all for features not covered by the other layers.
manmade: The manmade layer collects features that are man-made.
- featureType: Allows to have a more fine-grained selection for places frreverse_geocode lat, lon, zoom, format, addressdetails, extratags, namedetails, layer, polygon_geojson, polygon_kml, polygon_svg, polygon_text, polygon_threshold
Reverse geocoding generates an address from a coordinate given as latitude and longitude.
This tool finds the closest suitable OpenStreetMap (OSM) object and returns its address information.
The tool uses the Nominatim API to perform the reverse geocoding and returns the address information in a JSON object.
Input:
- lat: Latitude of the coordinate in WGS84 projection.
- lon: Longitude of the coordinate in WGS84 projection.
- zoom: Level of detail required for the address.
This is a number that corresponds roughly to the zoom level used in XYZ tile sources in frameworks like Leaflet.js, Openlayers etc.
In terms of address details the zoom levels are as follows:
3: country
5: state
8: county
10: city
12: town / borough
13: village / suburb
14: neighbourhood
15: any settlement
16: major streets
17: major and minor streets
18: buildings
- format: Format of the response. One of: xml, json, jsonv2, geojson, geocodejson. Default: jsonv2
- addressdetails: When set to 1, include a breakdown of the address into elements. The exact content of the address breakdown depends on the output format.
- extratags: When set to 1, the response include any additional information in the result that is available in the Nominatim database.
- namedetails: When set to 1, include a full list of names for the result. These may include language variants, older names, references and brand.
- layer: The layer filter allows to select places by themes. Comma-separated list of: address, poi, railway, natural, manmade
address: The address layer contains all places that make up an address: address points with house numbers, streets, inhabited places (suburbs, villages, cities, states etc.) and administrative boundaries.
poi: The poi layer selects all point of interest. This includes classic points of interest like restaurants, shops, hotels but also less obvious features like recycling bins, guideposts or benches.
railway: The railway layer includes railway infrastructure like tracks. Note that in Nominatim's standard configuration, only very few railway features are imported into the database.
natural: The natural layer collects features like rivers, lakes and mountains while the manmade layer functions as a catch-all for features not covered by the other layers.
manmade: The manmade layer collects features that are man-made.
- polygon_geojson: Add the full geometry of the place to the result output. Output formats in GeoJSON, KML, SVG or WKT are supported. Only one of these options can be used at a time.
- polygon_kml: Add the full geometry of the place to the result output. Output formats in GeoJSON, KML, SVG or WKT are supported. Only one of these options can be used at a time.
- polygon_svg: Add the full geometry of the place to the result output. Output formats in GeoJSON, KML, SVG or WKT are supported. Only one of these opDescriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | not stated |
|---|---|
| Needs | not stated |
| Source | not stated |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-CAhjakY2/drQFbsY1tB6WEMZAfm8jJKqFrim5GB12tjlFnrbrEZZKHnBi4kDWrewwgb56IcGgZUGUS9USumrCg== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40geocoding-ai/mcp)
New version out? Ask for a fresh report.