Places
Places, points of interest and geocoding
Calling it
Metered methods answer an unauthenticated call with 402 and an x402 challenge — pay it and the same request succeeds, with no account at all. A token works too.
curl -H "Authorization: Bearer $MU_TOKEN" \ https://mu-mcp.yvangodard.me/api/v1/places/list
Methods
GET /api/v1/places/addressName the place at a latitude and longitude — the reverse of places_geocode. Use it whenever you have coordinates and need to say where that is
| Argument | Type | Description |
|---|---|---|
lat * | number | Latitude, e.g. 51.5308 |
lon * | number | Longitude, e.g. -0.1238 |
curl \ "https://mu-mcp.yvangodard.me/api/v1/places/address?lat=1.5&lon=1.5"
GET /api/v1/places/elevationHow high a place is above sea level, in metres and feet. Sampled from a 90-metre global elevation model, so a summit reads a little under its surveyed height
| Argument | Type | Description |
|---|---|---|
place | string | A place name or address, e.g. 'Denver' or 'Ben Nevis' |
lat | number | Optional latitude, if the location is already known |
lon | number | Optional longitude, if the location is already known |
curl \ "https://mu-mcp.yvangodard.me/api/v1/places/elevation"
GET /api/v1/places/geocodeResolve a place name or address to coordinates
| Argument | Type | Description |
|---|---|---|
address | string | A place name or address to locate |
curl \ "https://mu-mcp.yvangodard.me/api/v1/places/geocode"
GET /api/v1/places/nearbyList points of interest near a location
| Argument | Type | Description |
|---|---|---|
near | string | Place to look around, e.g. 'Camden, London' (or give lat/lon) |
lat | number | Optional latitude |
lon | number | Optional longitude |
query | string | Optional keyword to filter by, e.g. 'cafe' |
radius | number | Optional radius in metres (default 1000) |
curl \ -H "Authorization: Bearer $MU_TOKEN" \ "https://mu-mcp.yvangodard.me/api/v1/places/nearby"
GET /api/v1/places/searchFind places by name or category, optionally near a location
| Argument | Type | Description |
|---|---|---|
query * | string | What to look for, e.g. 'ramen', 'pharmacy', 'Blue Bottle Coffee' |
near | string | Optional place to search near, e.g. 'Shoreditch, London' or 'SF' |
lat | number | Optional latitude, if the location is already known |
lon | number | Optional longitude, if the location is already known |
radius | number | Optional search radius in metres (default 2000) |
curl \ -H "Authorization: Bearer $MU_TOKEN" \ "https://mu-mcp.yvangodard.me/api/v1/places/search?query=query"
The same methods are tools over MCP, and every service on this instance is in one reference. Same method, same answer, same price.


