@pipeworx/mcp-data-oakland
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Contacts while installing and starting: gateway.pipeworx.io
What it contacted
gateway.pipeworx.io
Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.
Starting it
npx -y @pipeworx/mcp-data-oakland@0.2.1
Installing a package runs its code. Use a sandbox for anything you have not read.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
data_oakland_datasets query, limit, offset
Search the Oakland Open Data catalog of open datasets by keyword. Returns each dataset's resource_id, name, description, category and update date — pass the resource_id to query/metadata.
data_oakland_query resource_id, where, select, group, order, limit, offset
Run a Socrata SoQL query against a Oakland Open Data dataset by resource_id (e.g. "ym6k-rx7a"). Filter with where/select/group/order (SoQL clauses, without the leading $) plus limit/offset. Returns matching rows as JSON.
data_oakland_metadata resource_id
Get a Oakland Open Data dataset's schema + metadata (columns, types, row count, category, last-updated) by resource_id, e.g. "ym6k-rx7a".
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=18 |
| Source | github.com/pipeworx-io/mcp-data-oakland |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-QyxUxDq1q4fUPd1siiI3oYmK0yIpEjhC1FgvdG2YdgiPb5vysUT3wUwTYeXgR9amj8tKj/u66IOWhQDg94kPNg== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40pipeworx/mcp-data-oakland)
New version out? Ask for a fresh report.