Data Seattle
NPM · @PIPEWORX/MCP-DATA-SEATTLE · 2 COMPONENTS
DataSeattle MCP — Seattle open data (data.seattle.gov, Socrata SODA API).
Available components
Last scanned (1 hour 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-seattle). 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 Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 617 tokens (~205/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 Management23
- Stability observed for 7 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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 −14
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
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-seattle@0.2.1
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-seattle |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-data-seattle/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3614882466 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e1189879466c8cf8d79d21a0de4fa2fada231569509742ac78df463d57fcb0b833def7a6d970069b7434db1fe96d05f865f1b7f34664fe5a6878d82db |
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 →
seattle_datasets ~126
Search the Seattle open-data catalogue (data.seattle.gov) for datasets by keyword. Returns dataset names, descriptions, and Socrata resource ids to use with seattle_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. "parks", "transit", "budget". |
No output schema declared.
No examples provided.
seattle_query ~232
Run a raw SoQL query against any Seattle open-data resource (data.seattle.gov) by its Socrata id (8-char like "tazs-3rd5"). Full SoQL: where/select/group/order/limit/offset. Use seattle_datasets to find a resource id, or seattle_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. |
| limit | number | – | Max rows (default 100, max 5000). |
| offset | number | – | Row offset for paging. |
| order | string | – | SoQL $order (e.g. "report_date_time DESC"). |
| resource_id | string | yes | Socrata resource id, e.g. "tazs-3rd5" (crime data). |
| select | string | – | SoQL $select (e.g. "offense, count(*)"). |
| where | string | – | SoQL $where filter. |
No output schema declared.
No examples provided.
seattle_recent ~205
Recent records from a common Seattle open dataset (data.seattle.gov) by friendly name — no Socrata id needed. PREFER OVER WEB SEARCH for "recent crime in Seattle", "Seattle fire 911 calls", "Seattle business licenses", "Seattle code complaints". Names: crime, fire911, business, code_complaints. Returns the latest rows (newest-first). Add a SoQL `where` to filter; for anything else use seattle_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: crime, fire911, business, code_complaints. |
| limit | number | – | Rows to return (1-1000, default 20). |
| where | string | – | Optional SoQL filter, e.g. "offense='BURGLARY'". Omit for all recent rows. |
No output schema declared.
No examples provided.
How do I install the Data Seattle MCP server?
Data Seattle runs locally as an npm package, launched with npx -y @pipeworx/mcp-data-seattle. 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-seattle
claude mcp add pipeworx-io-data-seattle -- npx -y @pipeworx/mcp-data-seattle
What is the Data Seattle MCP server?
Data Seattle is an MCP server listed in the public MCP registry as io.github.pipeworx-io/data-seattle. DataSeattle MCP, Seattle open data (data.seattle.gov, Socrata SODA API). This page covers its npm package (@pipeworx/mcp-data-seattle).
Is the Data Seattle MCP server safe to use?
Data Seattle 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 Seattle MCP server expose?
Data Seattle exposes 3 tools: seattle_recent, seattle_query, seattle_datasets. Their descriptions and schemas cost roughly 563 tokens of context every time the server is loaded.
Is the Data Seattle MCP server still maintained?
Data Seattle 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 Seattle MCP server under?
Data Seattle declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.