Congress.gov API MCP Server

Created By
bsmi021a year ago
This is a Model Context Protocol (MCP) server designed to provide access to the official Congress.gov API (v3) using a hybrid approach.
Overview

What is Congress.gov API MCP Server?

The Congress.gov API MCP Server is a Model Context Protocol (MCP) server that provides access to the official Congress.gov API (v3) using a hybrid approach, allowing users to query U.S. legislative data easily.

How to use Congress.gov API MCP Server?

To use the server, install the dependencies, set your Congress.gov API key in a .env file, build the server, and run it. Connect your MCP client to the server to access resources.

Key features of Congress.gov API MCP Server?

  • Direct lookups of legislative entities (Bills, Members, Committees) using standardized URIs.
  • Tools for complex operations like searching across collections and retrieving related data lists.
  • Supports a two-step process for finding entities and getting related data.

Use cases of Congress.gov API MCP Server?

  1. Accessing detailed information about specific bills and members of Congress.
  2. Searching for legislation based on keywords or member names.
  3. Retrieving related data such as actions taken on bills or legislation sponsored by members.

FAQ from Congress.gov API MCP Server?

  • What is the purpose of the server?

The server acts as a bridge for MCP clients to query and utilize U.S. legislative data efficiently.

  • How do I get an API key?

You can obtain an API key from https://api.data.gov/signup/.

  • What programming language is used?

The server is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bsmi021
Star
0
Language
TypeScript
License
MIT license
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago