# Walkscore (npm · @pipeworx/mcp-walkscore)

Walk Score MCP — wraps the Walk Score API (walkscore.com)

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

## Components

- remote · `gateway.pipeworx.io`: 63/100, [markdown](https://verifymcp.io/servers/pipeworx-io-walkscore/walkscore-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-walkscore/walkscore-mcp)
- npm · `@pipeworx/mcp-walkscore`: 78/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-walkscore/pipeworx-mcp-walkscore.md), [page](https://verifymcp.io/servers/pipeworx-io-walkscore/pipeworx-mcp-walkscore)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-walkscore`
- Version: `0.2.0`
- 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-11-05.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-walkscore).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 312 tokens (~312/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Walkscore MCP server?

Walkscore runs locally as an npm package, launched with npx -y @pipeworx/mcp-walkscore. 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 pipeworx-io-walkscore -- npx -y @pipeworx/mcp-walkscore
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-walkscore": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-walkscore"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-walkscore": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-walkscore"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-walkscore -- npx -y @pipeworx/mcp-walkscore
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-walkscore --command npx --arg -y --arg @pipeworx/mcp-walkscore
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-walkscore:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-walkscore"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-walkscore": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-walkscore"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-walkscore -t stdio -c npx -a -y @pipeworx/mcp-walkscore
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-walkscore": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-walkscore"
      ]
    }
  }
}
```

## 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-10-29 (score 78)

First indexed and scored.

## MCP tools (1)

### `walkscore_score` (~259 tokens)

How walkable is <address> — Walk/Transit/Bike Score (0-100) plus a human-readable description of walkability, transit, and biking. NOTE: the Walk Score API requires lat AND lon AND address to all be provided — the coordinates locate the point and the address disambiguates it. Example: walkscore_score({ address: "1119 8th Avenue, Seattle, WA 98101", lat: 47.6085, lon: -122.3295, transit: true, bike: true, _apiKey: "your-key" })

Input parameters:

- `_apiKey` (string, required): Walk Score API key (get one free at walkscore.com/professional/api.php)
- `address` (string, required): Full street address, e.g. "1119 8th Avenue, Seattle, WA 98101"
- `bike` (boolean): Set true to also return the Bike Score (bikeability)
- `lat` (number, required): Latitude of the location, e.g. 47.6085
- `lon` (number, required): Longitude of the location, e.g. -122.3295
- `transit` (boolean): Set true to also return the Transit Score (public transit availability)

## Diagnostics

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

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Walkscore MCP server?

Walkscore is an MCP server listed in the public MCP registry as io.github.pipeworx-io/walkscore. Walk Score MCP, wraps the Walk Score API (walkscore.com). This page covers its npm package (@pipeworx/mcp-walkscore).

### Is the Walkscore MCP server safe to use?

Walkscore scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Walkscore MCP server expose?

Walkscore exposes 1 tool: walkscore_score. Their descriptions and schemas cost roughly 259 tokens of context every time the server is loaded.

### Is the Walkscore MCP server still maintained?

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

### What licence is the Walkscore MCP server under?

Walkscore declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Walkscore MCP server?

VerifyMCP ran 15 checks on Walkscore, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Walkscore: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-walkscore
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-walkscore
- Repository: https://github.com/pipeworx-io/mcp-walkscore
- Website: https://pipeworx.io/packs/walkscore
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-walkscore/pipeworx-mcp-walkscore.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-walkscore/pipeworx-mcp-walkscore/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-walkscore/pipeworx-mcp-walkscore.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-walkscore/pipeworx-mcp-walkscore