{"id":"nervsystems-osmmcp","name":"osmmcp","af_score":76.8,"security_score":47.5,"reliability_score":35.0,"what_it_does":"An MCP (Model Context Protocol) server written in Go that exposes OpenStreetMap-related geospatial tools to LLM/MCP clients. It provides primitives such as geocoding/reverse geocoding, distance calculations, bounding box/centroid utilities, OSM tag-based queries and nearby place search, routing via OSRM (including route directions and sampling), route enrichment (e.g., emissions/cost/calories), and additional domain tools like EV charging station lookup and neighborhood/livability-style analysis.","best_when":"You want an agent-friendly, self-hosted MCP toolset that combines OpenStreetMap data querying with routing and additional geospatial enrichment for interactive LLM workflows.","avoid_when":"You cannot tolerate reliance on external geospatial services (e.g., OSM/Nominatim/Overpass/OSRM) or you require robust access control, strong security guarantees around data flows, or a documented reliability/SLA.","last_evaluated":"2026-03-30T15:36:21.832495+00:00","has_mcp":true,"has_api":false,"auth_methods":[],"has_free_tier":false,"known_gotchas":["Upstream rate limits apply (Nominatim/Overpass/OSRM). The README mentions configurable rps/burst, but agents may still need backoff/retry strategies.","Some tools accept bounding boxes/radii/limits; overly broad parameters can cause large upstream queries and slow responses.","Because it depends on external services for OSM data and routing, transient upstream failures can occur; no explicit retry/backoff guidance is shown in the provided excerpt.","The MCP server appears to run over stdin/stdout for MCP requests; some MCP clients require exact process configuration."],"error_quality":null}