Walkably
REMOTE · MCP.WALKABLY.ORG
Real walking minutes to eight daily needs and a 0-100 score for any address.
Available components
Last scanned (22 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 998 tokens (~332/item across 3 items; 3 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 Management47
- Stability observed for 14 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 3 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “city_ranking” rewrote its description, which is the text the model reads security
- Tool “district_ranking” rewrote its description, which is the text the model reads security
- Tool “walkability_score” rewrote its description, which is the text the model reads security
- Schema quality: 300 → 332 ▼ functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “city_ranking” rewrote its description, which is the text the model reads security
- Tool “district_ranking” rewrote its description, which is the text the model reads security
- 30 Oct 26 0
- Tool “city_ranking” rewrote its description, which is the text the model reads security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “city_ranking” rewrote its description, which is the text the model reads security
- Tool “district_ranking” rewrote its description, which is the text the model reads security
- Tool “walkability_score” rewrote its description, which is the text the model reads security
- Schema quality: 239 → 291 ▼ functional
- Schema quality: 239 → 292 ▼ functional
- 27 Oct 26 +1
- Tool “district_ranking” rewrote its description, which is the text the model reads security
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
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 · Probed https://mcp.walkably.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=walkably.org | CN=WE1,O=Google Trust Services,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | cf0c7786b03a0d080e755670e45c3a26 |
| SANs: walkably.org, mcp.walkably.org, *.mcp.walkably.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.walkably.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| walkably.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.walkably.org/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.walkably.org/mcp | Inconclusive | 405 |
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 →
city_ranking City walkability and its best and least served areas ~242
A city's typical Walkably score (0 to 100, for where people live), its rank among the cities of the same country with a Walkably page (for example rank 1 of 36 cities in Spain), the median walk to each of eight daily needs, and up to five best and five least served areas of the city (on a greater-city page, the nearby towns outside the city in their own list), exactly as on its walkably.org city page. 528 cities in 31 European countries. This server is for single places in a conversation. Lists of addresses and bulk use go through the Walkably API: https://walkably.org/business/api/. The US and Canada are not covered yet; to ask for them: https://walkably.org/business/#us-request.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City name in English or the local language, e.g. "Barcelona", "München", "Hamburg". A country can follow after a comma: "Valencia, Spain". |
| country | string | – | Optional: country name or two-letter code (es, de, gb ...) when a city name exists in several countries. |
No output schema declared.
No examples provided.
district_ranking A city's districts ranked, or its best and least served areas ~237
For a city with a district ranking page (today Vienna, Berlin, Hamburg, Munich and Rome): every district that has a score on that page, ranked by Walkably score, with reach, street quality and minutes on foot to eight daily needs for each. For any other city: up to five best and five least served areas from its city page, and it says so. This server is for single places in a conversation. Lists of addresses and bulk use go through the Walkably API: https://walkably.org/business/api/. The US and Canada are not covered yet; to ask for them: https://walkably.org/business/#us-request.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City name in English or the local language, e.g. "Barcelona", "München", "Hamburg". A country can follow after a comma: "Valencia, Spain". |
| country | string | – | Optional: country name or two-letter code (es, de, gb ...) when a city name exists in several countries. |
| limit | integer | – | Optional: return only the first N districts of the ranking (1 to 100). |
No output schema declared.
No examples provided.
walkability_score Walkability score for an address or point ~297
How walkable one street spot in Europe is (31 countries). Give an address, or lat and lon. Returns the Walkably score from 0 to 100 (60% reach, 40% street quality; a very unpleasant street keeps the score from being high, and a place with nothing in walking distance scores low), the reach and street-quality parts, the share of the country's places it beats, minutes on foot along real streets to each of eight daily needs (groceries, food and drink, shops, health, school, parks, culture, transit) with the nearest place and a Europe-wide verdict, and a link to the spot on the map. Each score covers a six-sided street cell about 95 m across. Addresses are found with a place search service in the EU that uses OpenStreetMap data. This server is for single places in a conversation. Lists of addresses and bulk use go through the Walkably API: https://walkably.org/business/api/. The US and Canada are not covered yet; to ask for them: https://walkably.org/business/#us-request.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address or place, e.g. "Carrer de Blai 20, Barcelona". Use this or lat and lon. |
| lat | number | – | Latitude in degrees (WGS84). Use with lon instead of address. |
| lon | number | – | Longitude in degrees (WGS84). |
No output schema declared.
No examples provided.
How do I install the Walkably MCP server?
Walkably is a hosted endpoint at https://mcp.walkably.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.walkably.org
claude mcp add --transport http org-walkably-walkably 'https://mcp.walkably.org/mcp'
What is the Walkably MCP server?
Walkably is an MCP server listed in the public MCP registry as org.walkably/walkably. Real walking minutes to eight daily needs and a 0-100 score for any address. This page covers its hosted endpoint (https://mcp.walkably.org/mcp).
Is the Walkably MCP server safe to use?
Walkably scores 71 out of 100 on VerifyMCP. 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 Walkably MCP server expose?
Walkably exposes 3 tools: walkability_score, city_ranking, district_ranking. Their descriptions and schemas cost roughly 776 tokens of context every time the server is loaded.
Does the Walkably MCP server require authentication?
No. We connected to Walkably without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Walkably MCP server still maintained?
Walkably 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.