Open Reach
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USER_AGENT | Yes | Required by Nominatim policy - set to a descriptive value identifying your application | open-reach-mcp/0.1.0 (...) |
| CACHE_MAXSIZE | No | TTL cache maximum size | 2048 |
| OSRM_BASE_URL | No | Routing upstream URL | https://router.project-osrm.org |
| CACHE_TTL_SECONDS | No | TTL cache time-to-live in seconds | 86400 |
| OVERPASS_BASE_URL | No | POI upstream URL | https://overpass-api.de |
| NOMINATIM_BASE_URL | No | Geocoding upstream URL | https://nominatim.openstreetmap.org |
| HTTP_TIMEOUT_SECONDS | No | Upstream call timeout in seconds | 15.0 |
| RATE_LIMIT_MIN_INTERVAL_SECONDS | No | Per-host request spacing in seconds | 1.0 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Health-check tool. Returns Example: ping() -> {"status": "ok"} |
| geocodeA | Forward geocode a place name to a WGS84 coordinate (decimal degrees). Units: latitude/longitude in decimal degrees. Example: geocode(query="KLCC") -> GeoPoint(lat=3.1579, lon=101.7116) |
| reverse_geocodeA | Reverse geocode a coordinate to a human-readable address. Units: lat/lon in decimal degrees; returns a display-name string. Example: reverse_geocode(lat=3.15, lon=101.71) -> "Bukit Bintang, ..." |
| isochroneA | Reachable-area polygon within a travel-time budget. Units: lat/lon in decimal degrees; |
| catchment_poisA | Points of interest inside a site's catchment, grouped by category. Units: lat/lon decimal degrees; |
| site_reach_scoreA | Composite reach score in [0, 1] for a single OOH site. Combines gravity-weighted POI density, junction density, and category
diversity (public urban-analytics methodology). Returns the score plus an
auditable breakdown.
Units: lat/lon decimal degrees; |
| compare_sitesA | Rank candidate sites by reach score (server-side, deterministic). Ranking is computed here, not by the client model. Tie-break chain:
score desc, POI density desc, category diversity desc, name asc.
Units: lat/lon decimal degrees; |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/abangbroy/ooh_reach_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server