# Data Cambridge (npm · @pipeworx/mcp-data-cambridge)

DataCambridge MCP — Cambridge open data (data.cambridgema.gov, Socrata SODA API).

- Trust score: 83/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-data-cambridge/data-cambridge-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-data-cambridge/data-cambridge-mcp)
- npm · `@pipeworx/mcp-data-cambridge`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-data-cambridge/pipeworx-mcp-data-cambridge.md), [page](https://verifymcp.io/servers/pipeworx-io-data-cambridge/pipeworx-mcp-data-cambridge)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-data-cambridge`
- Version: `0.2.2`
- 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-data-cambridge).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 635 tokens (~211/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**: 20/100
  - Stability observed for 6 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Data Cambridge MCP server?

Data Cambridge runs locally as an npm package, launched with npx -y @pipeworx/mcp-data-cambridge. 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-data-cambridge -- npx -y @pipeworx/mcp-data-cambridge
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 83, +1)

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

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

### 2026-11-01 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 65, −15)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.2.1 → 0.2.2

### 2026-10-30 (score 80)

First indexed and scored.

## MCP tools (3)

### `cambridge_recent` (~201 tokens)

Recent records from a common Cambridge open dataset (data.cambridgema.gov) by friendly name — no Socrata id needed. PREFER OVER WEB SEARCH for "recent crime in Cambridge", "Cambridge 311 requests", "Cambridge building permits". Names: 311, crime, permits. Returns the latest rows (newest-first). Add a SoQL `where` to filter; for anything else use cambridge_query.

Input parameters:

- `_apiKey` (string): Optional — your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.
- `dataset` (string, required): One of: 311, crime, permits.
- `limit` (number): Rows to return (1-1000, default 20).
- `where` (string): Optional SoQL filter, e.g. "incident_category='Larceny Theft'" or "supervisor_district=6". Omit for all recent rows.

### `cambridge_query` (~252 tokens)

Run a raw SoQL query against any Cambridge open-data resource (data.cambridgema.gov) by its Socrata id (8-char like "2z9k-mv9g"). Full SoQL: where/select/group/order/limit/offset. Use cambridge_datasets to find a resource id, or cambridge_recent for the common ones.

Input parameters:

- `_apiKey` (string): Optional — your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.
- `group` (string): SoQL $group (e.g. "incident_category").
- `limit` (number): Max rows (default 100, max 5000).
- `offset` (number): Row offset for paging.
- `order` (string): SoQL $order (e.g. "incident_datetime DESC").
- `resource_id` (string, required): Socrata resource id, e.g. "2z9k-mv9g" (police incidents).
- `select` (string): SoQL $select (e.g. "incident_category, count(*)").
- `where` (string): SoQL $where filter (e.g. "incident_year=2025").

### `cambridge_datasets` (~126 tokens)

Search the Cambridge open-data catalogue (data.cambridgema.gov) for datasets by keyword. Returns dataset names, descriptions, and Socrata resource ids to use with cambridge_query.

Input parameters:

- `_apiKey` (string): Optional — your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.
- `limit` (number): Max datasets (1-100, default 20).
- `offset` (number): Offset for paging.
- `query` (string): Keyword(s), e.g. "parking", "housing", "tree".

## Diagnostics

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

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 65
- 2026-10-30: 80

## Common questions

### What is the Data Cambridge MCP server?

Data Cambridge is an MCP server listed in the public MCP registry as io.github.pipeworx-io/data-cambridge. DataCambridge MCP, Cambridge open data (data.cambridgema.gov, Socrata SODA API). This page covers its npm package (@pipeworx/mcp-data-cambridge).

### Is the Data Cambridge MCP server safe to use?

Data Cambridge scores 83 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 Data Cambridge MCP server expose?

Data Cambridge exposes 3 tools: cambridge_recent, cambridge_query, cambridge_datasets. Their descriptions and schemas cost roughly 579 tokens of context every time the server is loaded.

### Is the Data Cambridge MCP server still maintained?

Data Cambridge 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 Data Cambridge MCP server under?

Data Cambridge 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 Data Cambridge MCP server?

VerifyMCP ran 16 checks on Data Cambridge, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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-data-cambridge
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-data-cambridge
- Repository: https://github.com/pipeworx-io/mcp-data-cambridge
- Website: https://pipeworx.io/packs/data-cambridge
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-data-cambridge/pipeworx-mcp-data-cambridge.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-data-cambridge/pipeworx-mcp-data-cambridge/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-data-cambridge/pipeworx-mcp-data-cambridge.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-data-cambridge/pipeworx-mcp-data-cambridge