# io.github.capan/isochrone (npm · isochrone-mcp)

Berlin pedestrian isochrones: streets reachable on foot in N minutes (walk/stroller/wheelchair).

- Trust score: 71/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-17

## Components

- npm · `isochrone-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/capan-isochrone/isochrone-mcp.md), [page](https://verifymcp.io/servers/capan-isochrone/isochrone-mcp)

## Channel facts

- Registry: `npm`
- Package: `isochrone-mcp`
- Version: `0.1.4`
- 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-08-17.

- **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 95 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 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 481 tokens (~240/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add capan-isochrone -- npx -y isochrone-mcp
```

### Codex

```bash
codex mcp add capan-isochrone -- npx -y isochrone-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add capan-isochrone --command npx --arg -y --arg isochrone-mcp
```

### Hermes

```yaml
mcp_servers:
  capan-isochrone:
    command: "npx"
    args: ["-y", "isochrone-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "capan-isochrone": {
      "command": "npx",
      "args": [
        "-y",
        "isochrone-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-08-16 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-15 (score 70, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-08-11 (score 66, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-07 (score 67, +32)

- [security improvement] Known CVEs: partial → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 100
- [functional] Dependency health: partial → 0.85
- [functional] Package version: 0.1.3 → 0.1.4

### 2026-08-06 (score 35)

First indexed and scored.

## MCP tools (2)

### `reachable_area` (~229 tokens)

Reachable area on foot or by bike

Computes the street network reachable from a point within a time budget, for walk, stroller, wheelchair or bike profiles (steps and rough surfaces slow or block the middle two; cycle paths are bike-only). Returns a summary with total street length, extent, and a map link. Currently covers Berlin, Germany.

Input parameters:

- `include_geometry` (boolean): Also return the raw GeoJSON (10 arrival-time bands, large)
- `include_places` (boolean): Also summarise how many places of each group are reachable (food, shops, culture, health, learning, outdoors, money)
- `lat` (number, required): Origin latitude (WGS84)
- `lon` (number, required): Origin longitude (WGS84)
- `minutes` (integer): Time budget in minutes. Faster profiles allow fewer: walking allows up to 25, cycling up to 10, because the work grows with the area searched. Omit to use the profile's sensible default.
- `profile` (string): Mobility profile
- `target` (object): Optional destination: reports whether it's reachable in the time budget and the approximate arrival time

### `places_nearby` (~252 tokens)

Places reachable from a point

Lists actual places — cafes, shops, museums, pharmacies, parks — that can be reached from a point within a time budget, each with how long it takes to get there. Filter by group (food, shops, culture, health, learning, outdoors, money) or by specific kinds such as 'cafe' or 'pharmacy'. Called without group or kinds it returns a breakdown by group rather than an arbitrary mixture, so ask the user which they want. Use this for 'what can I get to', and reachable_area for 'how far can I get'. Currently covers Berlin, Germany.

Input parameters:

- `group` (string): Restrict to one group: food, shops, culture, health, learning, outdoors, money
- `kinds` (array): Restrict to specific kinds, e.g. ['cafe','bakery']. Takes precedence over group.
- `lat` (number, required): Origin latitude (WGS84)
- `limit` (integer): How many to list, nearest first
- `lon` (number, required): Origin longitude (WGS84)
- `minutes` (integer): Time budget in minutes. Omit for the profile's default.
- `profile` (string): Mobility profile

## Diagnostics

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

## Score history

- 2026-08-17: 71
- 2026-08-16: 71
- 2026-08-15: 70
- 2026-08-14: 66
- 2026-08-13: 66
- 2026-08-12: 66
- 2026-08-11: 66
- 2026-08-10: 67
- 2026-08-09: 67
- 2026-08-08: 67
- 2026-08-07: 67
- 2026-08-06: 35

## Links

- npm package: https://www.npmjs.com/package/isochrone-mcp
- Socket report: https://socket.dev/npm/package/isochrone-mcp
- Repository: https://github.com/capan/isochrone
- Changelog RSS feed: https://verifymcp.io/servers/capan-isochrone/isochrone-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/capan-isochrone/isochrone-mcp.json
- HTML version of this page: https://verifymcp.io/servers/capan-isochrone/isochrone-mcp