Legiscan MCP: MCP server, setup and security

What Legiscan MCP does

According to its repository: “Legislative data from all 50 US states and Congress via the LegiScan API: search bills, get full text, track votes and look up legislators.”

An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. Legiscan MCP is listed under Scientific research, a category of 35 servers in the directory, where it ranks #24 by stars.

Topics declared by the repository: legiscan, legislation, bills, congress, state-legislature, political-data.

Installing and connecting Legiscan MCP

No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.

Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: TypeScript.

Security: what to check

An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Legiscan MCP. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on December 23, 2025, the sh-patterson/legiscan-mcp repository has 12 stars and 4 forks, with 0 open issues. It has more stars than 29% of the servers in the directory. Last change 1 month ago.

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.