
Legislens
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
US state bills and hearing transcripts: search bills, testimony, speakers, hearings.
Overview
Legislens's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Legislens in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
legislens
legislens gives you a window onto US state lawmaking: bills moving through legislatures in all 50 states and DC, and what was actually said about them in committee hearings, attributed to the person who said it. One binary serves a command-line interface and a stdio MCP server.
legislens does not hold the archive itself. It is a forwarding client for a hosted API: each request is sent to that service and its answer is returned. The bills, testimony segments, transcripts, and coverage are the hosted service's; if it is unavailable or its coverage changes, legislens reflects that.
An API key is required. Set GAVELIN_API_KEY before use;
when it is missing or blank, every tool fails with an error
naming it before any request is made. The key is sent as
Authorization: Bearer <key>. The API base URL can be
overridden with LEGISLENS_API_URL; when it is not set, calls
go to https://api.gavelin.ai (a reconstruction of the wire
address, labelled as such).
Install
Or run the container image:
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
CLI
The subcommands mirror the MCP tool names:
Results print the upstream JSON payload. Exit codes: 0 on
success, 1 when a call fails (including a missing key or an
upstream API error), 2 for usage errors.
MCP server
One bin serves both faces. The mcp subcommand starts a stdio
MCP server:
MCP client configuration:
Tools
Dates use YYYY-MM-DD form as from_date / to_date. All
inputs are strings.
Development
License
MIT — see LICENSE.
Source: README.md at commit 2e81ff4
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts