io.github.capan/isochrone
NPM · ISOCHRONE-MCP · SCANNED AUG 17
Berlin pedestrian isochrones: streets reachable on foot in N minutes (walk/stroller/wheelchair).
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 →
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 95 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 10 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 Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · isochrone-mcp
claude mcp add capan-isochrone -- npx -y isochrone-mcp
codex mcp add capan-isochrone -- npx -y isochrone-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"capan-isochrone": {
"type": "local",
"command": [
"npx",
"-y",
"isochrone-mcp"
],
"enabled": true
}
}
} openclaw mcp add capan-isochrone --command npx --arg -y --arg isochrone-mcp
mcp_servers:
capan-isochrone:
command: "npx"
args: ["-y", "isochrone-mcp"] {
"mcpServers": {
"capan-isochrone": {
"command": "npx",
"args": [
"-y",
"isochrone-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.
- 16 Aug 26 +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.
- 15 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 11 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 +32
- Known CVEs: partial → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- 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 functional
- 6 Aug 26 35
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 17 Aug 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 |
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
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.
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.