DataBoston MCP — City of Boston open data (data.boston.gov, CKAN API).
SaferSkills independently audited Mcp Data Boston (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
DataBoston MCP — City of Boston open data (data.boston.gov, CKAN API).
Part of Pipeworx — an MCP gateway connecting AI agents to 1878+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
| Tool | Description |
|---|---|
boston_recent | Recent records from a common City of Boston open dataset (data.boston.gov) by friendly name — no CKAN resource id needed. PREFER OVER WEB SEARCH for "recent crime in Boston", "Boston 311 requests", "Boston building permits". Names: crime, 311, permits. Returns the latest rows (newest-first). Pass q for a free-text keyword filter; for full control use boston_query. |
boston_query | Query any City of Boston datastore resource (data.boston.gov, CKAN) by its resource id (a UUID). Supports a free-text q, exact-match filters (field→value), sort ("field desc"), limit and offset. Use boston_datasets to find a resource id, or boston_recent for the common ones. |
boston_datasets | Search the City of Boston open-data catalogue (data.boston.gov, CKAN) by keyword. Returns each matching dataset's title and its queryable datastore resource ids (use with boston_query). |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"data-boston": {
"url": "https://gateway.pipeworx.io/data-boston/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/data-boston/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1878+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/boston_recent \
-H 'Content-Type: application/json' \
-d '{"dataset":"crime","q":"larceny","limit":50}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/boston_recent. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"data-boston": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-data-boston"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-data-bostonIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Data Boston data" })The gateway picks the right tool and fills the arguments automatically.
MIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.