Data Cambridge
NPM · @PIPEWORX/MCP-DATA-CAMBRIDGE · 2 COMPONENTS
DataCambridge MCP — Cambridge open data (data.cambridgema.gov, Socrata SODA API).
Available components
Last scanned (9 hours ago)
Scores higher than 76% of npm servers
Category Data and Analytics
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 → Why this is hard to score →
Supply Chain Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-data-cambridge). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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 supported MCP spec version (2025-11-25); the latest is 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.
- 5 Nov 26 +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.
- 3 Nov 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.
- 1 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.2.1 → 0.2.2 functional
- 30 Oct 26 80
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-data-cambridge@0.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-data-cambridge |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-data-cambridge/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3614858653 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:fc856d07438bf5f06f6b4e6bceed05f8731f7423a4938657e137d13f6312dbccb854b675687e2f96fc66ef786177a7cf56f8fb663c57203c4f42b28aa |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
cambridge_datasets ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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". |
No output schema declared.
No examples provided.
cambridge_query ~252
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | 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"). |
No output schema declared.
No examples provided.
cambridge_recent ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Optional — your own Socrata app token for higher rate limits. Omit to use the keyless endpoint. |
| dataset | string | yes | 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. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-data-cambridge
claude mcp add pipeworx-io-data-cambridge -- npx -y @pipeworx/mcp-data-cambridge
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.