io.github.capan/isochrone
NPM · ISOCHRONE-MCP
Berlin pedestrian isochrones: streets reachable on foot in N minutes (walk/stroller/wheelchair).
Available components
Last scanned (19 hours ago)
Scores higher than 73% 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 89 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
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.
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Stability: pass → 0.97 functional
- 31 Oct 26 +5
- Source repository: unverified → pass ▲ security
- 30 Oct 26 −5
- Provenance: pass → unverified ▼ security
- 23 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 22 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 19 Oct 26 +1
- Security disclosure: fail → unverified ▼ functional
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 4 Nov 2026 · Analysed npm/isochrone-mcp@0.1.4
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 →
places_nearby Places reachable from a point ~252
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Origin latitude (WGS84) |
| limit | integer | – | How many to list, nearest first |
| lon | number | yes | Origin longitude (WGS84) |
| minutes | integer | – | Time budget in minutes. Omit for the profile's default. |
| profile | string | – | Mobility profile |
No output schema declared.
No examples provided.
reachable_area Reachable area on foot or by bike ~229
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Origin latitude (WGS84) |
| lon | number | yes | 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 |
No output schema declared.
No examples provided.
How do I install the io.github.capan/isochrone MCP server?
io.github.capan/isochrone runs locally as an npm package, launched with npx -y isochrone-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 · isochrone-mcp
claude mcp add capan-isochrone -- npx -y isochrone-mcp
What is the io.github.capan/isochrone MCP server?
io.github.capan/isochrone is an MCP server listed in the public MCP registry as io.github.capan/isochrone. Berlin pedestrian isochrones: streets reachable on foot in N minutes (walk/stroller/wheelchair). This page covers its npm package (isochrone-mcp).
Is the io.github.capan/isochrone MCP server safe to use?
io.github.capan/isochrone scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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.capan/isochrone MCP server expose?
io.github.capan/isochrone exposes 2 tools: reachable_area, places_nearby. Their descriptions and schemas cost roughly 481 tokens of context every time the server is loaded.
Is the io.github.capan/isochrone MCP server still maintained?
io.github.capan/isochrone is still listed as active in the MCP registry. We last reached this channel on 4 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.capan/isochrone MCP server under?
io.github.capan/isochrone declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.