org.billcommons/bill-commons
REMOTE · MCP.BILLCOMMONS.ORG · SCANNED SEP 25
Search 209k+ US state bills, all 50 states + DC: full text, sponsors, votes, status. Free.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1365 tokens (~124/item across 11 items; 11 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
How do I install the org.billcommons/bill-commons MCP server?
org.billcommons/bill-commons is a hosted endpoint at https://mcp.billcommons.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.billcommons.org
claude mcp add --transport http org-billcommons-bill-commons 'https://mcp.billcommons.org/mcp'
{
"mcpServers": {
"org-billcommons-bill-commons": {
"url": "https://mcp.billcommons.org/mcp"
}
}
} {
"servers": {
"org-billcommons-bill-commons": {
"type": "http",
"url": "https://mcp.billcommons.org/mcp"
}
}
} [mcp_servers.org-billcommons-bill-commons] url = "https://mcp.billcommons.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-billcommons-bill-commons": {
"type": "remote",
"url": "https://mcp.billcommons.org/mcp",
"enabled": true
}
}
} openclaw mcp add org-billcommons-bill-commons --url 'https://mcp.billcommons.org/mcp' --transport streamable-http
mcp_servers:
org-billcommons-bill-commons:
url: "https://mcp.billcommons.org/mcp" {
"McpServers": {
"org-billcommons-bill-commons": {
"Transport": "http",
"Url": "https://mcp.billcommons.org/mcp"
}
}
} assistant mcp add org-billcommons-bill-commons -t streamable-http -u 'https://mcp.billcommons.org/mcp'
{
"mcpServers": {
"org-billcommons-bill-commons": {
"type": "http",
"url": "https://mcp.billcommons.org/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Aug 26 75
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 5 Aug 26 0
- Tool “search_legislation” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- New tool “list_topics” functional
- 4 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 87 → 107 ▼ functional
- Schema quality: good → excellent functional
- 3 Aug 26 0
- Tool “build_legislative_evidence_packet” rewrote its description, which is the text the model reads security
- Schema quality: 74 → 87 ▼ functional
- “build_legislative_evidence_packet” added an optional parameter “question” cosmetic
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 25 Sept 2026 · Probed https://mcp.billcommons.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.billcommons.org | CN=YE2,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 612ca3a2b05ba975415f02dac248a33256a |
| SANs: mcp.billcommons.org | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.billcommons.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| billcommons.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.billcommons.org/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.billcommons.org/mcp | HTTPS enforced | 301 | https://mcp.billcommons.org/mcp |
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 →
build_legislative_evidence_packet ~203
Compile a citation-ready evidence packet for a bill: full official record, legislative history timeline, votes with member-level detail, and hearings -- each explicitly labeled official vs. derived with source URLs. Returns a `how_to_cite` block with a one-line `cite_as` sentence, a human `permalink`, a JSON `download_url`, and a `snapshot_id` that changes if and only if a cited fact about the bill changes -- so a reader can check later whether the citation still holds. Snapshots are NOT archived; the id is a change detector, not a way to retrieve an older packet. Pass `question` to record what the packet was assembled to answer; it is echoed into the artifact so a filed packet carries its own scope.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_id | string | yes | – |
| include_full_text | boolean | – | – |
| question | – | – | – |
No output schema declared.
No examples provided.
compare_bill_versions ~102
Deterministic diff (unified + structured) between two versions of a bill's extracted text. Defaults to earliest vs. latest texted version if version ids are omitted. Errors if fewer than 2 versions have extracted text. Result is labeled 'derived' (computed by Bill Commons, not an official document).
| Name | Type | Req | Description |
|---|---|---|---|
| bill_id | string | yes | – |
| version_id_a | – | – | – |
| version_id_b | – | – | – |
No output schema declared.
No examples provided.
find_similar_bills ~58
Find bills with similar titles via deterministic trigram similarity, across jurisdictions. Labeled 'derived' -- not an official cross-reference or companion-bill designation.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_id | string | yes | – |
| limit | – | – | – |
No output schema declared.
No examples provided.
get_active_sessions ~35
List legislative sessions currently flagged active, optionally filtered by jurisdiction (two-letter state code or name).
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | – | – | – |
No output schema declared.
No examples provided.
get_bill_record ~89
Fetch the full record for one bill: metadata, sponsors, subjects, actions, versions, and vote-event summaries. Look up by canonical bill_id (UUID), or by jurisdiction + identifier (+ optional session to disambiguate).
| Name | Type | Req | Description |
|---|---|---|---|
| bill_id | – | – | – |
| identifier | – | – | – |
| include_full_text | boolean | – | – |
| jurisdiction | – | – | – |
| session | – | – | – |
No output schema declared.
No examples provided.
get_jurisdiction_coverage ~53
Return the jurisdiction_coverage state-machine status for one state (abbreviation or name), or the full 51-jurisdiction coverage matrix if state is omitted.
| Name | Type | Req | Description |
|---|---|---|---|
| state | – | – | – |
No output schema declared.
No examples provided.
get_upcoming_hearings ~49
List upcoming (future-dated) legislative hearings/events, optionally filtered by jurisdiction and/or bill.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_id | – | – | – |
| jurisdiction | – | – | – |
| limit | – | – | – |
No output schema declared.
No examples provided.
get_vote_details ~65
Fetch vote event(s) with member-level (yes/no/other/absent) vote records. Provide vote_event_id for one vote, or bill_id for all recorded votes on that bill.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_id | – | – | – |
| vote_event_id | – | – | – |
No output schema declared.
No examples provided.
list_topics ~144
List Bill Commons' curated cross-state topic trackers (e.g. artificial intelligence, youth online safety, platform accountability, cybersecurity, cryptocurrency, data privacy, local government & preemption) -- the entry point for "what subjects does Bill Commons track across all 50 states + DC" and "how do I get every bill in one". Each topic is a title/subject membership rule tuned for precision over recall, with a live bill_count and how_to_fetch_bills. This tool does not itself return bill rows -- pair it with search_legislation or the REST API's /topics/{slug} for the bills.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_legislation ~237
Search FULL BILL TEXT -- not just known-bill-number lookup. `q` is matched against titles, descriptions, AND ingested document text via Postgres websearch_to_tsquery (supports "quoted phrases", OR, and -exclusion, same syntax as a search engine), with a fuzzy pg_trgm title-similarity fallback when the exact query has no hits. `q` can ALSO be a bill number ("HB 123", "H.B. 123", "hb123" all match) and that fast path is tried first. Optionally filter by jurisdiction (two-letter state code or name), chamber, and status. For a curated cross-state slice of a subject (e.g. "every AI bill in the country") rather than an ad-hoc keyword search, call list_topics first -- its membership rules also match on structured subject tags this full-text search does not see.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | – | – | – |
| jurisdiction | – | – | – |
| limit | – | – | – |
| q | string | yes | – |
| status | – | – | – |
No output schema declared.
No examples provided.
trace_legislative_history ~46
Full chronological legislative history for a bill: merged timeline of actions, version publications, and votes, plus related-bill links.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_id | string | yes | – |
No output schema declared.
No examples provided.
What is the org.billcommons/bill-commons MCP server?
org.billcommons/bill-commons is an MCP server listed in the public MCP registry as org.billcommons/bill-commons. Search 209k+ US state bills, all 50 states + DC: full text, sponsors, votes, status. Free. This page covers its hosted endpoint (https://mcp.billcommons.org/mcp).
Is the org.billcommons/bill-commons MCP server safe to use?
org.billcommons/bill-commons scores 75 out of 100 on VerifyMCP. 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 org.billcommons/bill-commons MCP server expose?
org.billcommons/bill-commons exposes 11 tools: search_legislation, get_bill_record, compare_bill_versions, find_similar_bills, get_vote_details, and 6 more. Their descriptions and schemas cost roughly 1,081 tokens of context every time the server is loaded.
Does the org.billcommons/bill-commons MCP server require authentication?
No. We connected to org.billcommons/bill-commons without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the org.billcommons/bill-commons MCP server still maintained?
org.billcommons/bill-commons is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.