# Legiscan (npm · @pipeworx/mcp-legiscan)

LegiScan MCP — wraps the LegiScan API (api.legiscan.com)

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-legiscan/legiscan-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-legiscan/legiscan-mcp)
- npm · `@pipeworx/mcp-legiscan`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-legiscan/pipeworx-mcp-legiscan.md), [page](https://verifymcp.io/servers/pipeworx-io-legiscan/pipeworx-mcp-legiscan)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-legiscan`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-legiscan).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 481 tokens (~160/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Legiscan MCP server?

Legiscan runs locally as an npm package, launched with npx -y @pipeworx/mcp-legiscan. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-legiscan -- npx -y @pipeworx/mcp-legiscan
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-legiscan": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-legiscan"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-legiscan": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-legiscan"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-legiscan -- npx -y @pipeworx/mcp-legiscan
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-legiscan": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-legiscan"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-legiscan --command npx --arg -y --arg @pipeworx/mcp-legiscan
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-legiscan:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-legiscan"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-legiscan": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-legiscan"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-legiscan -t stdio -c npx -a -y @pipeworx/mcp-legiscan
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-legiscan": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-legiscan"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 83, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 67, −13)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 80, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (3)

### `search_bills` (~210 tokens)

Full-text search US state (and federal) legislation to find out what bills are about a given topic. Searches one state or nationwide (ALL) and returns matching bills with number, title, state, last action, and a LegiScan bill_id you can pass to get_bill. Example: search_bills({ query: "data privacy", state: "CA" })

Input parameters:

- `_apiKey` (string): Optional — your own LegiScan API key for higher limits; omit to use the shared Pipeworx key.
- `query` (string, required): Search terms, e.g. "data privacy", "minimum wage", "abortion"
- `state` (string): 2-letter state abbreviation (e.g. "CA", "TX") or "ALL" to search every state. Default "ALL".
- `year` (number): LegiScan year code: 1 = all years, 2 = current + prior session (default), or a specific year like 2024.

### `get_bill` (~113 tokens)

Get the full detail for a single US legislative bill — status, sponsors (name/party/role), subjects, and links to the bill text. Use the bill_id returned by search_bills. Example: get_bill({ bill_id: 1234567 })

Input parameters:

- `_apiKey` (string): Optional — your own LegiScan API key for higher limits; omit to use the shared Pipeworx key.
- `bill_id` (number, required): LegiScan bill_id (obtained from search_bills results).

### `list_sessions` (~105 tokens)

List the legislative sessions for a US state (regular and special), with start/end years and session IDs. Useful to scope which session to track bills in. Example: list_sessions({ state: "NY" })

Input parameters:

- `_apiKey` (string): Optional — your own LegiScan API key for higher limits; omit to use the shared Pipeworx key.
- `state` (string, required): 2-letter state abbreviation, e.g. "NY", "FL", "CA".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-legiscan/pipeworx-mcp-legiscan#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 67
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the Legiscan MCP server?

Legiscan is an MCP server listed in the public MCP registry as io.github.pipeworx-io/legiscan. LegiScan MCP, wraps the LegiScan API (api.legiscan.com). This page covers its npm package (@pipeworx/mcp-legiscan).

### Is the Legiscan MCP server safe to use?

Legiscan scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Legiscan MCP server expose?

Legiscan exposes 3 tools: search_bills, get_bill, list_sessions. Their descriptions and schemas cost roughly 428 tokens of context every time the server is loaded.

### Is the Legiscan MCP server still maintained?

Legiscan is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Legiscan MCP server under?

Legiscan declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-legiscan
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-legiscan
- Repository: https://github.com/pipeworx-io/mcp-legiscan
- Website: https://pipeworx.io/packs/legiscan
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-legiscan/pipeworx-mcp-legiscan.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-legiscan/pipeworx-mcp-legiscan.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-legiscan/pipeworx-mcp-legiscan