"OpenStreetMap" matching MCP tools:

• openstreetmap_query_nearby

  openstreetmap-mcp-server

  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 geocode/reverse/lookup tools.

  Connector

• lion_poi_business_search

  lion-x402

  Keyless POI / business directory search - the no-API-key, no-signup, pay-per-query alternative to Google Places / Foursquare / Yelp. Pass an area (?area=Soho, New York, or ?bbox=south,west,north,east) and a category (?category=food|cafe|restaurant|bar|retail|grocery|hotel|health|pharmacy|finance|bank|fuel|automotive|education|gym) or raw OSM tag (?tag=shop=bakery), and get ONE structured JSON list of matching businesses - each with name, category, full address, phone, website, opening_hours, brand and lat/lon. For lead-generation, local-business intelligence, retail/CPG distribution mapping, logistics and competitive-mapping agents. Source: OpenStreetMap Overpass + Nominatim (ODbL), keyless. Business/place/POI public commercial listings only, no people, no PII. $0.01 USDC on Base via x402. Coverage varies by region; not a verified business registry. [x402 paid tool: GET /api/x402/poi-business-search-json?src=mcp returns the 402 challenge with the canonical payTo; price 0.01 USDC on Base eip155:8453.]

  Connector

• openstreetmap_lookup

  openstreetmap-mcp-server

  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.

  Connector

• openstreetmap_geocode

  openstreetmap-mcp-server

  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.

  Connector

• nausika_get_place

  Nausika

  Fetch full detail for a single place given its 'id'. Accepts either a full UUID or the 8-char [xxxxxxxx] short-id shown by nausika_search_places. Returns canonical attributes (name/coords/category/type), localized i18n names+descriptions, wiki image URLs, ratings aggregates, plus extras only this tool provides: the raw OpenStreetMap tags of the primary OSM feature, and direct links to OSM, Wikidata, and Wikipedia. Use this after nausika_search_places returns a result you want to drill into. For proximity / text search, use nausika_search_places.

  Connector

• geo-osm

  geoagentic

  Find nearby places on OpenStreetMap (cafes, ATMs, shops, parks, etc.). CRITICAL: The 'tags' argument MUST be passed as a single stringified JSON text block, NOT a nested JSON object. Example: "{\"amenity\":\"cafe\"}" USE FOR: - "Find a cafe near X" - "Are there any ATMs close to Y?" - "Show me supermarkets near Z" NOT FOR: directions, geocoding, Wikipedia, isochrones. EXAMPLE: User: "Find cafes near Koper station" → --lat 45.548 --lon 13.730 --tags '{"amenity":"cafe"}' --dist 300 COMMON TAGS: amenity: cafe, restaurant, atm, pharmacy, parking shop: supermarket, bakery, convenience tourism: hotel, museum, attraction

  Connector

• query

  Overpass

  Run a raw Overpass QL query against OpenStreetMap. Use for complex spatial queries the helper tools can't express. Example: `[out:json][timeout:25]; area["name"="Berlin"][admin_level=4]->.a; node["amenity"="library"](area.a); out body;`. Returns the raw Overpass JSON (elements array with node/way/relation).

  Connector

• openstreetmap_query_bbox

  openstreetmap-mcp-server

  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 geocode/reverse/lookup) does not apply here. For proximity searches centered on a point, use openstreetmap_query_nearby instead.

  Connector

• osm_reverse_geocode

  CIPHER x402 — Paid Solana & Crypto Tools

  Reverse geocoding via OpenStreetMap Nominatim. lat/lon → normalized address + place class/type. Priced at $0.001 USDC on Base (x402). Pass a signed x402 v2 authorization as the '_payment' argument to unlock the paid response. Without it, the tool returns the 402 accept-list for your wallet to sign.

  Connector

• openstreetmap_reverse

  openstreetmap-mcp-server

  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).

  Connector

• openstreetmap_query_raw

  openstreetmap-mcp-server

  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;" 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.

  Connector

• isochrones

  Openrouteservice

  "Reachable area in [N] minutes" / "drive-time / walk-time / bike-time polygons" / "service area" / "catchment polygon" / "isochrone map" — generate isochrone polygons (area reachable from a point in time or distance) for car / truck / bike / foot / wheelchair profiles using OpenStreetMap. Use for delivery zones, commute sheds, site selection.

  Connector

• hikes-trails

  geoagentic

  Global Waymarked Trail & Mountain Route Explorer. Queries real-time OpenStreetMap relation networks for designated hiking, biking, and mountain trails anywhere in the world. USE FOR: - "How long does it take to hike up Črna Prst from Podbrdo?" - "Are there any marked mountain paths near this coordinate?" - "Find biking or mountain biking (MTB) trails around this area." - Discovering waymark symbols, route difficulty metrics, and trail networks. CRITICAL INSTRUCTIONS FOR AGENT: - Use this tool instead of standard street routers (`geo-route`) if the destination is a mountain peak, ridge, national park trail, or alpine hut. - Set a small buffer (e.g., 0.005 for 500m, up to 0.02 for ~2km) around coordinates to avoid massive data payloads. - Accept the features returned by this tool as complete. DO NOT iteratively search or run multiple tag queries sequentially. Read the returned trail distances, calculate speed profiles, and answer immediately. NOT FOR: Street-grid driving directions, finding urban shops/cafes, raw city geocoding.

  Connector

• osm_geocode

  CIPHER x402 — Paid Solana & Crypto Tools

  Forward geocoding via OpenStreetMap Nominatim. Address string → lat/lon + normalized address block (country_code, state, city, postcode, road) + match_quality label. Priced at $0.001 USDC on Base (x402). Pass a signed x402 v2 authorization as the '_payment' argument to unlock the paid response. Without it, the tool returns the 402 accept-list for your wallet to sign.

  Connector

• maps_geocode

  Google_maps

  "Geocode [address] via Google Maps" / "Google Maps coordinates of [place]" / "lat lng for [address] using Google" — convert an address to lat/lng + formatted address via Google Maps Platform. Premium-quality geocoding (highest accuracy for US addresses); requires Google Maps API key. Use when Mapbox/MapTiler/OpenStreetMap miss the address.

  Connector

• usaspending_spending_by_geography

  usaspending-mcp-server

  Aggregate federal spending by state, county, or congressional district. Useful for per-capita analysis, regional comparisons, and mapping federal investment patterns. Geographic filters accept FIPS codes and 2-letter state abbreviations — NOT place names. Resolve place names to FIPS codes using a geocoding server (Census or OpenStreetMap) before applying location filters. Chain per-capita results with Census population data for meaningful comparisons.

  Connector

• duvera__food_restaurant_search

  gateway

  [duvera · risk:low] Search for restaurants and food places by name or location using OpenStreetMap. Read-only, no account required.

  Connector

• geocode_search

  Openrouteservice

  "Geocode [address]" / "find [city] coordinates" / "search for places named [X]" / "where is [landmark]" — geocode an address or place name to coordinates via Pelias (OpenStreetMap-backed). Returns ranked candidates with lat/lng, address components, layer (venue/street/locality/region). Use as a free alternative to Mapbox/Google geocoding, or when you want OpenStreetMap-curated data.

  Connector

• directions

  Openrouteservice

  "Directions from A to B" / "how far is [X] from [Y]" / "hiking / cycling / wheelchair / walking route" / "truck routing" / "HGV directions" / "driving route" — turn-by-turn routing between coordinates with profile-specific routing. Profiles: driving-car, driving-hgv (trucks), foot-walking, foot-hiking, cycling-regular / mountain / road / electric, wheelchair. Returns geometry, distance, duration, turn-by-turn instructions, elevation. Uses OpenStreetMap data via OpenRouteService. Use for hiking/biking/wheelchair/truck cases where Mapbox/Google don't have the right profile.

  Connector

• matrix

  Openrouteservice

  "Distance matrix between locations" / "all-to-all travel times" / "N×M routing grid" / "drive / walk / bike times between [list]" — N×M distance and duration matrix between many points via OpenStreetMap routing. Use for traveling-salesman setup, multi-stop optimization, nearest-warehouse, fleet dispatch. Profile-aware (car / truck / bike / foot / wheelchair).

  Connector