org.billcommons/bill-commons
REMOTE · MCP.BILLCOMMONS.ORG · SCANNED AUG 3
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 →
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 10 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
- Tool/resource definitions use about 872 tokens (~87/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.billcommons.org
claude mcp add --transport http org-billcommons-bill-commons 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": {
"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.
- 3 Aug 26 +1
- 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
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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
- 29 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
- 28 Jul 26 57
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 3 Aug 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 | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5a39a929555ce39496f8e24934851ce88dc |
| 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 |
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 |
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.
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.
search_legislation ~95
Search bills by keyword/phrase (full-text) or normalized bill number (e.g. "HB 123", "H.B. 123", "hb123" all match). Optionally filter by jurisdiction (two-letter state code or name), chamber, and status.
| 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.