mcp-registry/com.delilahusa/legislation · v0.8.0
As of 2026-10-21 11:15 UTC, the Delilahusa Legislation MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
U.S. bills, roll-call votes, legislators and 2026 elections for all 50 states, D.C. and Congress.
Claude Code
claude mcp add --transport http delilahusa-legislation-mcp-server https://mcp.delilahusa.com/
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"delilahusa-legislation-mcp-server": {
"type": "http",
"url": "https://mcp.delilahusa.com/"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
41 of 41 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
41 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
6 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.delilahusa%2Flegislation/fixes
{
"name": "get_ballot_measure",
"description": "Ballot measures (GET /v1/measures): the list for a state, or one measure by its number (e.g. 'Amendment 1') with full text, summary and official source URL. Use for 'what's on the ballot in X' and 'what does Amendment N do'.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"state"
],
"properties": {
"q": {
"type": "string",
"description": "Title search."
},
"type": {
"type": "string",
"description": "Measure type filter."
},
"limit": {
"type": "integer",
"maximum": 200,
"minimum": 1
},
"state": {
"type": "string",
"maxLength": 2,
"minLength": 2,
"description": "Postal code."
},
"number": {
"type": "string",
"description": "Exact measure number (e.g. 'Amendment 1') to fetch one measure."
},
"offset": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Statewide ballot measures"
}{
"name": "get_bill",
"description": "Fetch a single bill by its numeric bill_id (GET /v1/bills/{bill_id}), optionally merging in sub-resources: votes (roll calls with tallies), sponsors, history (action timeline), texts (version metadata), amendments, subjects, analyses (staff analyses), calendar (scheduled events), citations (statutes the bill touches), referrals (committee referrals), sast (same-as / similar-to companion bills in the other chamber or other states), supplements (fiscal notes and summaries). analyses and citations ",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"bill_id"
],
"properties": {
"detail": {
"type": "boolean",
"description": "true = one request to /v1/bills/{id}/detail with every sub-resource merged (the cheapest way to get everything). Ignores include."
},
"bill_id": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Numeric bill_id from a search result."
},
"include": {
"type": "array",
"items": {
"enum": [
"votes",
"sponsors",
"history",
"texts",
"amendments",
"subjects",
"analyses",
"calendar",
"citations",
"referrals",
"sast",
"supplements"
],
"type": "string"
},
"description": "Sub-resources to merge into the result: votes, sponsors, history, texts, amendments, subjects, analyses, calendar, citations, referrals, sast, supplements."
},
"max_items": {
"type": "integer",
"maximum": 200,
"minimum": 1,
"description": "Cap on items per included list (default 50)."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Get one bill"
}{
"name": "get_bill_diff",
"description": "Compare two versions of a bill's text (GET /v1/bills/{bill_id}/diff): a unified diff plus similarity, added/removed line and character counts, and changed-section highlights. Get the two version ids from get_bill with include:['texts'] — each text row's `text_id`. Pass them as `from` (the earlier version) and `to` (the later version). Diffs are precomputed, so only bills that have more than one text version return one.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"bill_id",
"from",
"to"
],
"properties": {
"to": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991
},
{
"type": "string"
}
],
"description": "Text-version id of the later version to compare against."
},
"from": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991
},
{
"type": "string"
}
],
"description": "Text-version id of the earlier version (the baseline)."
},
"bill_id": {
"anyOf": [
{
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991
},
{
"type": "string"
}
],
"description": "bill_id the two texts belong to."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Diff two bill-text versions"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.delilahusa/legislation"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.delilahusa/legislation"}) over MCP.
search_bills ~640 tokensmanage_webhooks ~416 tokensget_bill ~411 tokenslist_candidates ~401 tokensget_session_sponsor_stats ~388 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.delilahusa%2Flegislation?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.delilahusa%2Flegislation?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.delilahusa%2Flegislation.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.delilahusa%2Flegislation.svg :target: https://glimind.com/server/mcp-registry%2Fcom.delilahusa%2Flegislation?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7f6b29efa5fa4421…, first seen 2026-10-17, included at leaf 406 of 39,214. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable retrieval servers · most reliable media servers · most reliable data servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 11:15 UTC, the Delilahusa Legislation MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Delilahusa Legislation MCP server advertises 41 tools, including get_ballot_measure, get_bill, get_bill_diff, get_bill_statutes, get_bill_text.
Point your MCP client at this streamable-http endpoint: https://mcp.delilahusa.com/
Glimind scanned all 41 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.