# Walkably (remote · mcp.walkably.org)

Real walking minutes to eight daily needs and a 0-100 score for any address.

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

## Components

- remote · `mcp.walkably.org`: 72/100 (this document), [markdown](https://verifymcp.io/servers/org-walkably-walkably/mcp.md), [page](https://verifymcp.io/servers/org-walkably-walkably/mcp)

## Channel facts

- Endpoint: `https://mcp.walkably.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

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

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

### Claude

```bash
claude mcp add --transport http org-walkably-walkably 'https://mcp.walkably.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-walkably-walkably": {
      "url": "https://mcp.walkably.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-walkably-walkably": {
      "type": "http",
      "url": "https://mcp.walkably.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-walkably-walkably]
url = "https://mcp.walkably.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-walkably-walkably": {
      "type": "remote",
      "url": "https://mcp.walkably.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-walkably-walkably --url 'https://mcp.walkably.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-walkably-walkably:
    url: "https://mcp.walkably.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-walkably-walkably": {
      "Transport": "http",
      "Url": "https://mcp.walkably.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-walkably-walkably -t streamable-http -u 'https://mcp.walkably.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-walkably-walkably": {
      "type": "http",
      "url": "https://mcp.walkably.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-05 (score 72, +1)

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

### 2026-11-03 (score 71, +1)

- [security] 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
- [functional regression] Schema quality: 300 → 332

### 2026-11-01 (score 70, +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.

### 2026-10-31 (score 69, 0)

- [security] 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

### 2026-10-30 (score 69, 0)

- [security] Tool “city_ranking” rewrote its description, which is the text the model reads

### 2026-10-29 (score 69, +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.

### 2026-10-28 (score 68, 0)

- [security] 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
- [functional regression] Schema quality: 239 → 291
- [functional regression] Schema quality: 239 → 292

### 2026-10-27 (score 68, +1)

- [security] Tool “district_ranking” rewrote its description, which is the text the model reads

## MCP tools (3)

### `walkability_score` (~297 tokens)

Walkability score for an address or point

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.

Input parameters:

- `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).

### `city_ranking` (~242 tokens)

City walkability and its best and least served areas

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.

Input parameters:

- `city` (string, required): 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.

### `district_ranking` (~237 tokens)

A city's districts ranked, or its best and least served areas

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.

Input parameters:

- `city` (string, required): 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).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-walkably-walkably/mcp#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 69
- 2026-10-30: 69
- 2026-10-29: 69
- 2026-10-28: 68
- 2026-10-27: 68
- 2026-10-26: 67
- 2026-10-25: 67
- 2026-10-24: 66
- 2026-10-23: 66
- 2026-10-22: 66
- 2026-10-21: 65

## Common questions

### 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 72 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.walkably.org/mcp
- Website: https://walkably.org/
- Changelog RSS feed: https://verifymcp.io/servers/org-walkably-walkably/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-walkably-walkably/mcp.json
- HTML version of this page: https://verifymcp.io/servers/org-walkably-walkably/mcp