# io.github.mrfentmen/stadiamaps-mcp (npm · stadiamaps-mcp)

Stadia Maps: geocoding, routing, isochrones, static maps and elevation lookups.

- Trust score: 67/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `stadiamaps-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/mrfentmen-stadiamaps-mcp/stadiamaps-mcp.md), [page](https://verifymcp.io/servers/mrfentmen-stadiamaps-mcp/stadiamaps-mcp)

## Channel facts

- Registry: `npm`
- Package: `stadiamaps-mcp`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 833 tokens (~69/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 85/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 56% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

## Install

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

### Claude

```bash
claude mcp add mrfentmen-stadiamaps-mcp -- npx -y stadiamaps-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mrfentmen-stadiamaps-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "stadiamaps-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrfentmen-stadiamaps-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "stadiamaps-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mrfentmen-stadiamaps-mcp -- npx -y stadiamaps-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrfentmen-stadiamaps-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "stadiamaps-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mrfentmen-stadiamaps-mcp --command npx --arg -y --arg stadiamaps-mcp
```

### Hermes

```yaml
mcp_servers:
  mrfentmen-stadiamaps-mcp:
    command: "npx"
    args: ["-y", "stadiamaps-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mrfentmen-stadiamaps-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "stadiamaps-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrfentmen-stadiamaps-mcp -t stdio -c npx -a -y stadiamaps-mcp
```

### Other

```json
{
  "mcpServers": {
    "mrfentmen-stadiamaps-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "stadiamaps-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-28 (score 67, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-27 (score 52)

First indexed and scored.

## MCP tools (12)

### `stadia_geocode` (~59 tokens)

Forward geocode a place name or address; returns compact rows (label, lat/lon, region, country).

Input parameters:

- `size` (integer): max results (default 10)
- `text` (string, required): place name or address to search

### `stadia_autocomplete` (~29 tokens)

As-you-type place suggestions for partial input.

Input parameters:

- `text` (string, required): partial place name

### `stadia_reverse` (~88 tokens)

Reverse geocode a coordinate: what place is at this lat/lon. Returns compact rows.

Input parameters:

- `coordinates` (string, required): "lat, lon", e.g. "40.7128, -74.0060"
- `layers` (string): optional layer filter, e.g. "address,street"
- `zoom` (integer): Pelias zoom granularity (18 = building)

### `stadia_structured` (~68 tokens)

Structured geocoding: give separate country/region/city/address/postalcode parts instead of one string.

Input parameters:

- `address` (string)
- `city` (string)
- `country` (string)
- `postalcode` (string)
- `region` (string)

### `stadia_directions` (~88 tokens)

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.

Input parameters:

- `costing` (string)
- `units` (string)
- `waypoints` (string, required): "lat,lon" points in order, separated by spaces or semicolons

### `stadia_directions_summary` (~67 tokens)

The same route call reduced to one line: total distance, total time, leg count.

Input parameters:

- `costing` (string)
- `units` (string)
- `waypoints` (string, required): "lat,lon" points in order, separated by spaces or semicolons

### `stadia_isochrone` (~80 tokens)

Reachable-area polygons from one point within 1-120 minute contours (per travel mode).

Input parameters:

- `contours` (array, required): minutes, e.g. [10, 20]
- `coordinates` (string, required): "lat, lon", e.g. "40.7128, -74.0060"
- `costing` (string)

### `stadia_isochrone_contours` (~73 tokens)

The same isochrone call reduced to the per-contour metadata (which contour covers how far).

Input parameters:

- `contours` (array, required)
- `coordinates` (string, required): "lat, lon", e.g. "40.7128, -74.0060"
- `costing` (string)

### `stadia_route_matrix` (~94 tokens)

Time/distance matrix between many sources and targets (each "lat,lon lat,lon ...") — pick the nearest of N places.

Input parameters:

- `costing` (string)
- `sources` (string, required): "lat,lon" points, separated by spaces or semicolons
- `targets` (string, required): "lat,lon" points, separated by spaces or semicolons
- `units` (string)

### `stadia_elevation` (~67 tokens)

Elevation along a path of 2+ points; with range=true the answer includes cumulative distance at each sample.

Input parameters:

- `range` (boolean): include cumulative distance per sample
- `waypoints` (string, required): "lat,lon" points, separated by spaces or semicolons

### `stadia_elevation_point` (~51 tokens)

Elevation at a single coordinate (one height call, range off).

Input parameters:

- `coordinates` (string, required): "lat, lon", e.g. "40.7128, -74.0060"

### `stadia_timezone` (~69 tokens)

IANA timezone and offsets for a coordinate; pass timestamp (epoch seconds) for the offset at that instant.

Input parameters:

- `coordinates` (string, required): "lat, lon", e.g. "40.7128, -74.0060"
- `timestamp` (integer): epoch seconds to ask about

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mrfentmen-stadiamaps-mcp/stadiamaps-mcp#diagnostics

## Score history

- 2026-11-05: 67
- 2026-11-04: 67
- 2026-11-03: 67
- 2026-11-02: 67
- 2026-11-01: 67
- 2026-10-31: 67
- 2026-10-30: 67
- 2026-10-29: 67
- 2026-10-28: 67
- 2026-10-27: 52

## Common questions

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

## Links

- npm package: https://www.npmjs.com/package/stadiamaps-mcp
- Socket report: https://socket.dev/npm/package/stadiamaps-mcp
- Repository: https://github.com/mrfentmen/awesome-servers
- Changelog RSS feed: https://verifymcp.io/servers/mrfentmen-stadiamaps-mcp/stadiamaps-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrfentmen-stadiamaps-mcp/stadiamaps-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mrfentmen-stadiamaps-mcp/stadiamaps-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mrfentmen-stadiamaps-mcp/stadiamaps-mcp