who_reps-mcp

who_reps-mcp

Given a U.S. street address, returns the people who represent it (U.S. Senators, House member, Governor, and state legislators) using free public data, with no API keys required for federal officials.

Category
访问服务器

README

who_reps-mcp

Address → your elected officials, as an MCP server. A free, open replacement for the Google Civic Information Representatives API, which was shut down on April 30, 2025 and left a generation of civic apps broken.

Give it a U.S. street address and it returns the people who represent it — U.S. Senators, U.S. House member, Governor, and state legislators — by stitching together free public data: address → districts (Census) → officials (open congressional + state-legislator data).

Why this exists

When Google killed representativeInfoByAddress, the official guidance was: use our Divisions API for an OCD id, then go buy officeholder data from BallotReady, Cicero, or Ballotpedia. This rebuilds the free path so an agent can just answer "who represents this address?"

Quick start

The federal tier needs no API keys — the Census geocoder and the unitedstates/congress-legislators dataset are both free and key-less.

uv sync

# As an MCP server (stdio):
uv run whoreps-mcp

# Or try the data path from a terminal (no keys needed):
uv run whoreps-mcp lookup "1600 Pennsylvania Ave NW, Washington, DC 20500"
uv run whoreps-mcp lookup "2300 N Lincoln Blvd, Oklahoma City, OK 73105"
#  4 officials for 2300 N LINCOLN BLVD, ...: U.S. Senator James Lankford (R);
#  U.S. Senator Markwayne Mullin (R); U.S. Representative Stephanie I. Bice (R, 5);
#  Governor Kevin Stitt (R). State legislators omitted — set OPENSTATES_API_KEY ...

To add the state-legislator tier, get a free OpenStates key, cp .env.example .env, set OPENSTATES_API_KEY, and the same lookups will include state senators and representatives.

Use it as an MCP server

{
  "mcpServers": {
    "whoreps": {
      "command": "uv",
      "args": ["run", "whoreps-mcp"],
      "cwd": "/path/to/whoreps-mcp"
    }
  }
}

Tools

Tool What it does
lookup_officials(address) The headline tool. Address in, full slate out (federal + state where available), each official with party, contact, term, source, and as-of date, plus OCD divisions and coverage notes.
list_districts(address) Just the districts/divisions for an address — congressional + state-legislative districts and OCD-IDs (the piece Google's Divisions API gave, free and self-hosted).
lookup_by_district(state, chamber, district) Skip geocoding: senate/house (federal) or upper/lower (state).
get_official_details(official_id) Enriched detail for one official — committees + full contact where available.

Each tool returns structured JSON plus a concise text summary.

Graceful degradation

This is a civic tool, so correctness and honesty matter:

  • Federal always works, with zero keys. Missing tiers never fail the whole request — you get what's available plus coverage_notes explaining any gap.
  • DC and territories return the non-voting delegate (no senators), and note that DC has a Mayor rather than a Governor and no state legislature.
  • Bad/PO-box/new-construction addresses that don't geocode return an empty result with a note, not an error.
  • Freshness is visible. Every official carries its source and as_of date. Governors are a vendored, dated snapshot (see docs/governors.md); everything else is fetched live and cached.

How it works

address ─▶ Census geocoder ─▶ {lat/lon, congressional district, state-leg districts, OCD divisions}
                                     │
              ┌──────────────────────┼───────────────────────┐
              ▼                      ▼                         ▼
     congress-legislators     OpenStates people.geo      governors.json
     (U.S. Senate + House)    (state legislators)        (vendored)
              └──────────────────────┼───────────────────────┘
                                     ▼
                     merge + normalize -> OfficialsResponse  (SQLite-cached)

Sources live behind sources/ so the whole flow is tested against recorded fixtures — CI is fully offline.

Development

uv run pytest        # offline suite (recorded fixtures)
uv run ruff check .  # lint

If uv run whoreps-mcp ever reports No module named 'whoreps_mcp' (a known editable-install quirk on some setups, e.g. paths with spaces), run with PYTHONPATH=src uv run whoreps-mcp ....

See SPEC.md and BUILD_PLAN.md for the design.

License

MIT.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选