@pipeworx/mcp-openstates
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 0 of 2 tools tried
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-openstates@0.2.1
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
2 tools that take no input and look read-only were called once with nothing. 0 returned a result.
openstates_get_bill | No usable answer tool reported an error: {"error":"tool_error","message":"Pass either openstates_id, OR all three of jurisdiction + session + identifier.","retry_hint":"Retry th |
search_legislators | No usable answer tool reported an error: {"error":"tool_error","message":"OpenStates error: 400 either 'jurisdiction', 'name', or 'id' is required","retry_hint":"Retry the same |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
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
openstates_search_bills jurisdiction, query, session, classification, sponsor, sort, per_page, page
Search bills in any US statehouse. Pass jurisdiction as a 2-letter state code (e.g., "CA", "NY", "TX") or full name. Returns bill identifiers, titles, classifications, last action, sponsors, and OpenStates IDs for use with get_bill.
openstates_get_bill openstates_id, jurisdiction, session, identifier
Fetch a single bill with full detail: versions, sponsorships, related/companion bills, actions, and votes. Pass the OpenStates ID (e.g., "ocd-bill/abc...") or a state/session/identifier triple.
search_legislators jurisdiction, name, org_classification, district, party, per_page, page
Find state legislators. Filter by jurisdiction, name, chamber (upper/lower), party, or district. Returns name, current/prior roles, party, contact details, OpenStates IDs.
get_legislator person_id
Fetch a single legislator by OpenStates person ID. Returns biographical info, current roles, prior offices, contact methods, sources.
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-openstates |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-A9urN9MosGtoN/Cow8JUcl/+AGyPmWZG5GPjiZMX+0TwgAueughc9t2NN5SuBlZbg7GQybOOSZbTOA8j8pO2fg== |
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-openstates)
New version out? Ask for a fresh report.