Skip to content

bill-commons MCP server

org.billcommons/bill-commonsbillcommons.orgstreamable-httpv1.0.0Scanned

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

13 tools: 3 change things and 10 only read.

Tools: 0 delete, 0 irreversible, 3 write, 10 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the bill-commons MCP server can do

The bill-commons MCP server is published by billcommons.org, a domain the MCP Registry verified. It has 13 tools. It can create or change data (3 tools: trace_legislative_history, build_legislative_evidence_packet and build_policy_brief), but cannot delete data. 10 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Changes things 3Claude Code: ask
  • build_legislative_evidence_packetCompile a citation-ready evidence packet for a bill: full official record, legislative history timeline, votes with member-level detail, and hearings -- each explicitly labeled off…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • build_policy_briefBuild a citation-first comparison of one to twelve registry records.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Build a citation-first comparison of one to twelve registry records. The brief preserves the registry's methodology and limitations and does not produce legal advice, compliance determinations, or a claim that the selected set is exhaustive. Supply stable slugs returned by `search_policy_developments`.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • trace_legislative_historyFull chronological legislative history for a bill: merged timeline of actions, version publications, and votes, plus related-bill links.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Full chronological legislative history for a bill: merged timeline of actions, version publications, and votes, plus related-bill links.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 10Show 10 read-only tools
  • compare_bill_versionsDeterministic diff (unified + structured) between two versions of a bill's extracted text.No findings

    Why it is in this group

    • The name "compare_bill_versions" says "compare": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • find_similar_billsFind bills with similar titles via deterministic trigram similarity, across jurisdictions.No findings

    Why it is in this group

    • The name "find_similar_bills" says "find": a word for reading.
    Description, as the server wrote it
    Find bills with similar titles via deterministic trigram similarity, across jurisdictions. Labeled 'derived' -- not an official cross-reference or companion-bill designation.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_active_sessionsList legislative sessions currently flagged active, optionally filtered by jurisdiction (two-letter state code or name).No findings

    Why it is in this group

    • The name "get_active_sessions" says "get": a word for reading.
    Description, as the server wrote it
    List legislative sessions currently flagged active, optionally filtered by jurisdiction (two-letter state code or name).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_bill_recordFetch the full record for one bill: metadata, sponsors, subjects, actions, versions, and vote-event summaries.No findings

    Why it is in this group

    • The name "get_bill_record" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_jurisdiction_coverageReturn the jurisdiction_coverage state-machine status for one state (abbreviation or name), or the full stored coverage matrix if state is omitted.No findings

    Why it is in this group

    • The name "get_jurisdiction_coverage" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_policy_developmentRetrieve one full, source-labelled policy development by its stable slug.No findings

    Why it is in this group

    • The name "get_policy_development" says "get": a word for reading.
    Description, as the server wrote it
    Retrieve one full, source-labelled policy development by its stable slug. The response can include cited sources, normalized obligations, explicit analysis-only verification mappings, and recorded change history. A null response means only that the slug is absent from this bounded registry; it does not establish that the underlying policy development is absent.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_vote_detailsFetch vote event(s) with member-level (yes/no/other/absent) vote records.No findings

    Why it is in this group

    • The name "get_vote_details" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_topicsList Bill Commons' curated cross-state topic trackers (e.g.No findings

    Why it is in this group

    • The name "list_topics" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_legislationSearch FULL BILL TEXT -- not just known-bill-number lookup.No findings

    Why it is in this group

    • The name "search_legislation" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_policy_developmentsSearch Bill Commons' bounded, source-labelled frontier-AI policy registry.No findings

    Why it is in this group

    • The name "search_policy_developments" says "search": a word for reading.
    Description, as the server wrote it
    Search Bill Commons' bounded, source-labelled frontier-AI policy registry. This is not a comprehensive global or federal legislative database. It returns only the curated records currently held by the registry, including its coverage statement and retrieval timestamps. Use `jurisdiction`, `instrument_type`, `status`, or an exact topic; use `q` for a title, summary, or topic substring. `since` filters source publication dates and `changed_since` filters source-check activity on or after an ISO date; a retrieval or changed source body does not establish a policy change.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:17 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.billcommons.org/mcp: tools/list returned 13 tools to an anonymous client, including trace_legislative_history (write), build_legislative_evidence_packet (write), build_policy_brief (write)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 2 to 3

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
    • Tools that change things, listed without credentials: 2 to 3
  2. Tools3 added.+3 addedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http bill-commons https://mcp.billcommons.org/mcp
claude mcp add --transport http bill-commons https://mcp.billcommons.org/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__bill-commons__search_legislation",
      "mcp__bill-commons__get_bill_record",
      "mcp__bill-commons__compare_bill_versions",
      "mcp__bill-commons__find_similar_bills",
      "mcp__bill-commons__get_vote_details",
      "mcp__bill-commons__get_jurisdiction_coverage",
      "mcp__bill-commons__get_active_sessions",
      "mcp__bill-commons__list_topics",
      "mcp__bill-commons__search_policy_developments",
      "mcp__bill-commons__get_policy_development"
    ],
    "ask": [
      "mcp__bill-commons__trace_legislative_history",
      "mcp__bill-commons__build_legislative_evidence_packet",
      "mcp__bill-commons__build_policy_brief"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bill-commons. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/org.billcommons/bill-commons/verify?hash=d26e0ed9eb861a68643f17ef722fd9fec9f363c59d8070519c4c0868d485b7da" | jq -e '.changed == false'

Pinned hash d26e0ed9eb86, from Nov 18, 2026, 02:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/org.billcommons/bill-commons/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for org.billcommons/bill-commons
[![Anlyon Radar](https://radar.anlyon.com/badge/org.billcommons/bill-commons.svg)](https://radar.anlyon.com/servers/org.billcommons/bill-commons)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:54 UTC.

bill-commons MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the bill-commons MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the bill-commons MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the bill-commons MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the bill-commons MCP server have?

13 tools: 3 write, 10 read. trace_legislative_history, build_legislative_evidence_packet, build_policy_brief, search_legislation, get_bill_record, compare_bill_versions, find_similar_bills, get_vote_details and 5 more.

Does the bill-commons MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the bill-commons MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the bill-commons MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 4, 2026. Every change is on this page and in its Atom feed.