# org.billcommons/bill-commons

> Search 209k+ US state bills, all 50 states + DC: full text, sponsors, votes, status. Free.

- name: org.billcommons/bill-commons
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 93/100
- quality: 75/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/org.billcommons%2Fbill-commons
- tools: https://api.protogrid.dev/v1/servers/org.billcommons%2Fbill-commons/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "bill-commons": {
      "type": "http",
      "url": "https://mcp.billcommons.org/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 85
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-99% ~updated-84d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 75/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 10 of 10 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,931 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 36 tool changes in 30 days
- fail `stability.rug_pull`: 3 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 10, about 1,931 tokens to load them all
- tool set hash: aa2239adbae675b3fb50ef1574d6c9ed
- tools last changed: 2026-10-08T09:41:42.818Z
- badge: [![protogrid quality](https://protogrid.dev/badge/org.billcommons/bill-commons.svg)](https://protogrid.dev/servers/org.billcommons/bill-commons)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-08 `get_upcoming_hearings` removed
  - List upcoming (future-dated) legislative hearings/events, optionally filtered by jurisdiction and/or bill.
- 2026-10-08 `list_topics` changed (annotations)
- 2026-10-08 `get_active_sessions` changed (annotations)
- 2026-10-08 `get_jurisdiction_coverage` changed (description, annotations) **meaning changed**
  - before: Return the jurisdiction_coverage state-machine status for one state (abbreviation or name), or the full 51-jurisdiction coverage matrix if state is omitted.
  - after: Return the jurisdiction_coverage state-machine status for one state (abbreviation or name), or the full stored coverage matrix if state is omitted. Public-registry and unlisted row counts are explicit. Includes bounded retained official-source observation health and evidence links. Coverage status measures stored bill/text availability; local coverage timestamps can advance on count recomputation. Statewide semantic freshness remains unverified, including for GREEN coverage.
- 2026-10-08 `build_legislative_evidence_packet` changed (annotations)
- 2026-10-08 `trace_legislative_history` changed (annotations)
- 2026-10-08 `get_vote_details` changed (annotations)
- 2026-10-08 `find_similar_bills` changed (annotations)
- 2026-10-08 `compare_bill_versions` changed (annotations)
- 2026-10-08 `get_bill_record` changed (description, annotations)
  - before: 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).
  - after: 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). For a human bill number like HB 123, use jurisdiction="NC", identifier="HB 123"; bill_id is for UUIDs.

Full history: https://api.protogrid.dev/v1/servers/org.billcommons%2Fbill-commons/changes

## Remotes

- https://mcp.billcommons.org/mcp (streamable-http, auth none, reachable true, uptime30d 0.9917355)

## Packages

_none_

## Tools (10)

- `build_legislative_evidence_packet`: 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.
- `compare_bill_versions`: 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).
- `find_similar_bills`: Find bills with similar titles via deterministic trigram similarity,
    across jurisdictions. Labeled 'derived' -- not an official
    cross-reference or companion-bill designation.
- `get_active_sessions`: List legislative sessions currently flagged active, optionally
    filtered by jurisdiction (two-letter state code or name).
- `get_bill_record`: 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). For a human bill number like HB 123, use
    jurisdiction="NC", identifier="HB 123"; bill_id is for UUIDs.
- `get_jurisdiction_coverage`: Return the jurisdiction_coverage state-machine status for one state
    (abbreviation or name), or the full stored coverage matrix if
    state is omitted. Public-registry and unlisted row counts are explicit. Includes bounded retained official-source observation health
    and evidence links. Coverage status measures stored bill/text availability;
    local coverage timestamps can advance on count recomputation. Statewide
    semantic freshness remains unverified, including for GREEN coverage.
- `get_vote_details`: 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.
- `list_topics`: 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.
- `search_legislation`: 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.
- `trace_legislative_history`: Full chronological legislative history for a bill: merged timeline of
    actions, version publications, and votes, plus related-bill links.
