io.github.mrfentmen/stadiamaps-mcp
NPM · STADIAMAPS-MCP
Stadia Maps: geocoding, routing, isochrones, static maps and elevation lookups.
Available components
Last scanned (10 hours ago)
Scores higher than 35% of npm servers
Category Maps and Location
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
- 30 of 92 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 (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 833 tokens (~69/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 52
First indexed and scored.
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 5 Nov 2026 · Analysed npm/stadiamaps-mcp@1.0.0
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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
stadia_autocomplete ~29
As-you-type place suggestions for partial input.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | partial place name |
No output schema declared.
No examples provided.
stadia_directions ~88
Route between 2+ waypoints ("lat,lon lat,lon ..." separated by spaces or semicolons). Returns trip summary plus per-leg summaries (length, time) — no raw geometry.
| Name | Type | Req | Description |
|---|---|---|---|
| costing | string | – | – |
| units | string | – | – |
| waypoints | string | yes | "lat,lon" points in order, separated by spaces or semicolons |
No output schema declared.
No examples provided.
stadia_directions_summary ~67
The same route call reduced to one line: total distance, total time, leg count.
| Name | Type | Req | Description |
|---|---|---|---|
| costing | string | – | – |
| units | string | – | – |
| waypoints | string | yes | "lat,lon" points in order, separated by spaces or semicolons |
No output schema declared.
No examples provided.
stadia_elevation ~67
Elevation along a path of 2+ points; with range=true the answer includes cumulative distance at each sample.
| Name | Type | Req | Description |
|---|---|---|---|
| range | boolean | – | include cumulative distance per sample |
| waypoints | string | yes | "lat,lon" points, separated by spaces or semicolons |
No output schema declared.
No examples provided.
stadia_elevation_point ~51
Elevation at a single coordinate (one height call, range off).
| Name | Type | Req | Description |
|---|---|---|---|
| coordinates | string | yes | "lat, lon", e.g. "40.7128, -74.0060" |
No output schema declared.
No examples provided.
stadia_geocode ~59
Forward geocode a place name or address; returns compact rows (label, lat/lon, region, country).
| Name | Type | Req | Description |
|---|---|---|---|
| size | integer | – | max results (default 10) |
| text | string | yes | place name or address to search |
No output schema declared.
No examples provided.
stadia_isochrone ~80
Reachable-area polygons from one point within 1-120 minute contours (per travel mode).
| Name | Type | Req | Description |
|---|---|---|---|
| contours | array | yes | minutes, e.g. [10, 20] |
| coordinates | string | yes | "lat, lon", e.g. "40.7128, -74.0060" |
| costing | string | – | – |
No output schema declared.
No examples provided.
stadia_isochrone_contours ~73
The same isochrone call reduced to the per-contour metadata (which contour covers how far).
| Name | Type | Req | Description |
|---|---|---|---|
| contours | array | yes | – |
| coordinates | string | yes | "lat, lon", e.g. "40.7128, -74.0060" |
| costing | string | – | – |
No output schema declared.
No examples provided.
stadia_reverse ~88
Reverse geocode a coordinate: what place is at this lat/lon. Returns compact rows.
| Name | Type | Req | Description |
|---|---|---|---|
| coordinates | string | yes | "lat, lon", e.g. "40.7128, -74.0060" |
| layers | string | – | optional layer filter, e.g. "address,street" |
| zoom | integer | – | Pelias zoom granularity (18 = building) |
No output schema declared.
No examples provided.
stadia_route_matrix ~94
Time/distance matrix between many sources and targets (each "lat,lon lat,lon ...") — pick the nearest of N places.
| Name | Type | Req | Description |
|---|---|---|---|
| costing | string | – | – |
| sources | string | yes | "lat,lon" points, separated by spaces or semicolons |
| targets | string | yes | "lat,lon" points, separated by spaces or semicolons |
| units | string | – | – |
No output schema declared.
No examples provided.
stadia_structured ~68
Structured geocoding: give separate country/region/city/address/postalcode parts instead of one string.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| city | string | – | – |
| country | string | – | – |
| postalcode | string | – | – |
| region | string | – | – |
No output schema declared.
No examples provided.
stadia_timezone ~69
IANA timezone and offsets for a coordinate; pass timestamp (epoch seconds) for the offset at that instant.
| Name | Type | Req | Description |
|---|---|---|---|
| coordinates | string | yes | "lat, lon", e.g. "40.7128, -74.0060" |
| timestamp | integer | – | epoch seconds to ask about |
No output schema declared.
No examples provided.
How do I install the io.github.mrfentmen/stadiamaps-mcp server?
io.github.mrfentmen/stadiamaps-mcp runs locally as an npm package, launched with npx -y stadiamaps-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 · stadiamaps-mcp
claude mcp add mrfentmen-stadiamaps-mcp -- npx -y stadiamaps-mcp
What is the io.github.mrfentmen/stadiamaps-mcp server?
io.github.mrfentmen/stadiamaps-mcp is listed in the public MCP registry as io.github.mrfentmen/stadiamaps-mcp. Stadia Maps: geocoding, routing, isochrones, static maps and elevation lookups. This page covers its npm package (stadiamaps-mcp).
Is the io.github.mrfentmen/stadiamaps-mcp server safe to use?
io.github.mrfentmen/stadiamaps-mcp scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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.mrfentmen/stadiamaps-mcp server expose?
io.github.mrfentmen/stadiamaps-mcp exposes 12 tools: stadia_geocode, stadia_autocomplete, stadia_reverse, stadia_structured, stadia_directions, and 7 more. Their descriptions and schemas cost roughly 833 tokens of context every time the server is loaded.
Is the io.github.mrfentmen/stadiamaps-mcp server still maintained?
io.github.mrfentmen/stadiamaps-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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.mrfentmen/stadiamaps-mcp server under?
io.github.mrfentmen/stadiamaps-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.mrfentmen/stadiamaps-mcp server?
VerifyMCP ran 15 checks on io.github.mrfentmen/stadiamaps-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.mrfentmen/stadiamaps-mcp: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.