CongressMCP
REMOTE · WWW.CONGRESSMCP.COM · SCANNED SEP 29
Federal and 50-state legislative data for AI: bills, text, votes, members, and committees.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 661 tokens (~110/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the CongressMCP MCP server?
CongressMCP is a hosted endpoint at https://www.congressmcp.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.congressmcp.com
claude mcp add --transport http com-congressmcp-congressmcp 'https://www.congressmcp.com/mcp'
{
"mcpServers": {
"com-congressmcp-congressmcp": {
"url": "https://www.congressmcp.com/mcp"
}
}
} {
"servers": {
"com-congressmcp-congressmcp": {
"type": "http",
"url": "https://www.congressmcp.com/mcp"
}
}
} [mcp_servers.com-congressmcp-congressmcp] url = "https://www.congressmcp.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-congressmcp-congressmcp": {
"type": "remote",
"url": "https://www.congressmcp.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-congressmcp-congressmcp --url 'https://www.congressmcp.com/mcp' --transport streamable-http
mcp_servers:
com-congressmcp-congressmcp:
url: "https://www.congressmcp.com/mcp" {
"McpServers": {
"com-congressmcp-congressmcp": {
"Transport": "http",
"Url": "https://www.congressmcp.com/mcp"
}
}
} assistant mcp add com-congressmcp-congressmcp -t streamable-http -u 'https://www.congressmcp.com/mcp'
{
"mcpServers": {
"com-congressmcp-congressmcp": {
"type": "http",
"url": "https://www.congressmcp.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 −10
- Transport: pass → fail ▼ security
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Sept 26 75
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://www.congressmcp.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.congressmcp.com | CN=WE1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 4811b7d4ff4fd066139bf096bae18889 |
| SANs: www.congressmcp.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.congressmcp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| congressmcp.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.congressmcp.com/mcp | Unreachable | ||
| http (plaintext) | http://www.congressmcp.com/mcp | HTTPS enforced | 301 | https://www.congressmcp.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
connect_congressmcp_account Connect a CongressMCP account with OAuth ~70
Use this after subscription activation when the user wants this chat to access CongressMCP. It returns the MCP OAuth challenge so the host can open CongressMCP’s authorization and consent flow. Never ask the user to paste a password, API key, access token, or refresh token into chat.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_subscription_checkout Create a CongressMCP Stripe Checkout ~151
Use this only after email verification, a plan selection from list_subscription_plans, and explicit user confirmation. It creates an idempotent Stripe-hosted subscription Checkout tied to the verified account and returns the external checkout URL. Stripe collects card details outside chat, and creating the URL does not itself complete the purchase.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | True only after the user explicitly confirms creation of checkout for this exact plan and displayed price. |
| idempotency_key | string | yes | Fresh UUID for this checkout; reuse only for the identical retry. |
| onboarding_token | string | yes | Short-lived onboarding token returned by verify_email_signup. |
| plan_id | string | yes | Exact plan identifier returned by list_subscription_plans. |
No output schema declared.
No examples provided.
get_subscription_status Get CongressMCP subscription status ~75
Use this after checkout to check whether Stripe’s signed webhook has activated the verified account. It reads the current server-side entitlement and never retries payment or changes billing. When paid is true, use connect_congressmcp_account to authorize this chat.
| Name | Type | Req | Description |
|---|---|---|---|
| onboarding_token | string | yes | Short-lived onboarding token returned by verify_email_signup. |
No output schema declared.
No examples provided.
list_subscription_plans List CongressMCP subscription plans ~67
Use this before checkout to show the current CongressMCP plans and exact server-configured prices. Amounts are integer minor currency units, such as cents, and listing plans never starts a checkout or charge. Do not guess a price or use a plan identifier that is not returned here.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_email_signup Send a CongressMCP email verification code ~135
Use this when the user wants to create or recover a CongressMCP account in chat. It sends a six-digit, 15-minute code to the supplied email after explicit acceptance of the terms and privacy policy. It does not start a subscription, expose whether an account already exists, or charge anything.
| Name | Type | Req | Description |
|---|---|---|---|
| accepted_terms | boolean | yes | True only after the user explicitly accepts https://www.congressmcp.com/terms and https://www.congressmcp.com/privacy. |
| string | yes | Email address that will own the CongressMCP account. | |
| name | string | yes | Person or organization name for the account. |
No output schema declared.
No examples provided.
verify_email_signup Verify a CongressMCP email code ~107
Use this after start_email_signup when the user provides the six-digit code from their email. It verifies email control, activates the free account when needed, and returns a short-lived onboarding token for checkout and status calls. The token is not an OAuth token or API key and cannot access CongressMCP research or workspace data.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Six-digit code from the CongressMCP verification email. |
| string | yes | The same normalized account email used to request the code. |
No output schema declared.
No examples provided.
What is the CongressMCP MCP server?
CongressMCP is an MCP server listed in the public MCP registry as com.congressmcp/congressmcp. Federal and 50-state legislative data for AI: bills, text, votes, members, and committees. This page covers its hosted endpoint (https://www.congressmcp.com/mcp).
Is the CongressMCP MCP server safe to use?
CongressMCP scores 66 out of 100 on VerifyMCP. 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 CongressMCP MCP server expose?
CongressMCP exposes 6 tools: list_subscription_plans, start_email_signup, verify_email_signup, create_subscription_checkout, get_subscription_status, connect_congressmcp_account. Their descriptions and schemas cost roughly 605 tokens of context every time the server is loaded.
Does the CongressMCP MCP server require authentication?
No. We connected to CongressMCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CongressMCP MCP server still maintained?
CongressMCP is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.