io.github.geowire/geowire
NPM · @GEOWIREHQ/MCP · SCANNED SEP 20
Place search, directions, isochrones & area analysis across 10 map providers. No API key to start.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 44 of 109 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 55 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1465 tokens (~146/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.geowire/geowire MCP server?
io.github.geowire/geowire runs locally as an npm package, launched with npx -y @geowirehq/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @geowirehq/mcp
claude mcp add geowire-geowire -- npx -y @geowirehq/mcp
{
"mcpServers": {
"geowire-geowire": {
"command": "npx",
"args": [
"-y",
"@geowirehq/mcp"
]
}
}
} {
"servers": {
"geowire-geowire": {
"command": "npx",
"args": [
"-y",
"@geowirehq/mcp"
]
}
}
} codex mcp add geowire-geowire -- npx -y @geowirehq/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"geowire-geowire": {
"type": "local",
"command": [
"npx",
"-y",
"@geowirehq/mcp"
],
"enabled": true
}
}
} openclaw mcp add geowire-geowire --command npx --arg -y --arg @geowirehq/mcp
mcp_servers:
geowire-geowire:
command: "npx"
args: ["-y", "@geowirehq/mcp"] {
"McpServers": {
"geowire-geowire": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@geowirehq/mcp"
]
}
}
} assistant mcp add geowire-geowire -t stdio -c npx -a -y @geowirehq/mcp
{
"mcpServers": {
"geowire-geowire": {
"command": "npx",
"args": [
"-y",
"@geowirehq/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@geowirehq/mcp@0.6.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 109 packages
| Packages resolved | 109 |
|---|---|
| Stale | 31 |
| No linked repository | 13 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_area ~200
Analyze a commercial area / neighborhood: given a center point, radius, and business types, return how many of each exist nearby, their density (per km²), rating landscape, and top places. Use this for market/competition questions — 'how saturated is coffee here', 'is this a good spot for a bakery', 'what's the dining scene within 1km'. Example: {"center": {"latitude": 37.4979, "longitude": 127.0276}, "radiusMeters": 1000, "categories": ["cafe", "restaurant", "convenience store"]}. Works with any configured providers; richer with Google/Foursquare (ratings). Not demographic data — it's a place-density/competition view built from live search.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | – |
| center | object | yes | – |
| limitPerCategory | integer | – | – |
| options | object | – | – |
| radiusMeters | number | yes | – |
No output schema declared.
No examples provided.
distance_matrix ~179
Compute a matrix of travel distances and times from each origin to each destination (N origins × M destinations) in one call. No API key needed. Use this to rank/compare many candidates by drive time — e.g. 'which of these 5 stores is closest to the customer' or delivery/logistics assignment. Example: {"origins": [{"latitude": 37.57, "longitude": 126.98}], "destinations": [{"latitude": 37.49, "longitude": 127.02}, {"latitude": 37.51, "longitude": 127.05}]}. rows[i][j] is origins[i] → destinations[j]. Public OSRM supports driving only.
| Name | Type | Req | Description |
|---|---|---|---|
| destinations | array | yes | – |
| mode | string | – | – |
| options | object | – | – |
| origins | array | yes | – |
No output schema declared.
No examples provided.
geocode_address ~97
Convert a street address or place name into geographic coordinates and a normalized address. Use this when you have an address string and need latitude/longitude. Example: {"address": "1600 Amphitheatre Parkway, Mountain View, CA"}. To search for businesses by name/category, use search_places.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| country | string | – | – |
| limit | integer | – | – |
| options | object | – | – |
No output schema declared.
No examples provided.
get_demographics ~122
Get demographics (population, median age, median household income, households) for the area containing a coordinate. Use this for market context — 'who lives around here', income/age of an area. Requires a demographics provider: US Census (free key, US only). Returns null outside coverage. Example: {"location": {"latitude": 37.7749, "longitude": -122.4194}}. For a full commercial picture combine with analyze_area, which folds this in automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| location | object | yes | – |
| options | object | – | – |
No output schema declared.
No examples provided.
get_directions ~198
Get a route (driving directions) between two or more waypoints, with total distance, travel time, and per-leg breakdown. Works with no API key (OpenStreetMap routing via OSRM). Use this for 'how do I get from A to B', 'how far by car', or 'how long to drive' questions. Waypoints are {latitude, longitude} in order (start, [via...], end). Example: {"waypoints": [{"latitude": 37.5665, "longitude": 126.9780}, {"latitude": 37.4979, "longitude": 127.0276}]}. Set geometry:true to also get the route polyline. Note: the public OSRM server supports driving only.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | boolean | – | – |
| geometry | boolean | – | – |
| mode | string | – | – |
| options | object | – | – |
| waypoints | array | yes | – |
No output schema declared.
No examples provided.
get_isochrone ~185
Compute a travel-time reachability area (isochrone): from an origin, the region reachable within N minutes of driving/walking/cycling, as a GeoJSON polygon + area in km². No API key (OpenStreetMap routing). Use for site selection / catchment questions — 'what's within a 15-minute drive', 'how big is this store's 10-min catchment'. Example: {"origin": {"latitude": 37.7749, "longitude": -122.4194}, "minutes": 15, "mode": "driving"}. It's an approximation (sampled bearings scored by a distance matrix), not a routing-engine isochrone.
| Name | Type | Req | Description |
|---|---|---|---|
| bearings | integer | – | – |
| minutes | number | yes | – |
| mode | string | – | – |
| options | object | – | – |
| origin | object | yes | – |
No output schema declared.
No examples provided.
get_place ~169
Fetch full details for a single place by its provider reference id, in the form 'provider:providerPlaceId' (e.g. 'google:ChIJN1t_tDeuEmsRUsoyG83frY4'), as found in a place's `sources`. Only providers that support getPlace can resolve a reference — currently Google (needs an API key). OpenStreetMap/Nominatim does not, so a 'nominatim:...' reference returns nothing; use search_places or geocode_address for OSM instead. Internal 'gwp_' ids cannot be resolved directly. Example: {"id": "google:ChIJN1t_tDeuEmsRUsoyG83frY4"}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| options | object | – | – |
No output schema declared.
No examples provided.
list_geo_providers ~61
List the geo data providers currently configured, with their capabilities, enabled state, priority, and required attribution. Use this to understand which data sources are available (e.g. whether Google is configured) before choosing a strategy or explaining coverage. Takes no arguments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reverse_geocode ~57
Convert geographic coordinates into the nearest address / place. Example: {"location": {"latitude": 37.5665, "longitude": 126.9780}}.
| Name | Type | Req | Description |
|---|---|---|---|
| location | object | yes | – |
| options | object | – | – |
No output schema declared.
No examples provided.
search_places ~197
Search for places (businesses, points of interest, landmarks) by a natural-language query, optionally biased to a coordinate (`near`) and/or restricted to a country. Returns places ranked by relevance/distance, each with location, address, contact, opening hours, and its data source(s). Use this for 'find X near Y' requests. Example: {"query": "24-hour pharmacy", "near": {"latitude": 10.7769, "longitude": 106.7009}, "radiusMeters": 2000}. To turn an address into coordinates use geocode_address instead; to look up one known place use get_place.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | – |
| country | string | – | – |
| limit | integer | – | – |
| near | object | – | – |
| openNow | boolean | – | – |
| options | object | – | – |
| query | string | yes | – |
| radiusMeters | number | – | – |
No output schema declared.
No examples provided.
What is the io.github.geowire/geowire MCP server?
io.github.geowire/geowire is an MCP server listed in the public MCP registry as io.github.geowire/geowire. Place search, directions, isochrones & area analysis across 10 map providers. No API key to start. This page covers its npm package (@geowirehq/mcp).
Is the io.github.geowire/geowire MCP server safe to use?
io.github.geowire/geowire scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.geowire/geowire MCP server expose?
io.github.geowire/geowire exposes 10 tools: search_places, get_place, geocode_address, reverse_geocode, get_directions, and 5 more. Their descriptions and schemas cost roughly 1,465 tokens of context every time the server is loaded.
Is the io.github.geowire/geowire MCP server still maintained?
io.github.geowire/geowire is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.geowire/geowire MCP server under?
io.github.geowire/geowire declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.