Lobbywatch Mcp

io.github.malkreide由 GitHub 账号 malkreide 发布v0.3.8更新于 Oct 24, 2026

Lobbywatch.ch transparency data on parliamentarians, interests, access badges

已验证STDIO仅桌面知识与记忆数据与分析

概览

AI 生成的概览

本地 MCP 服务器,提供 Lobbywatch.ch 关于瑞士联邦议员、申报利益关系、游说团体与透明度评分的数据。

可以做什么
按姓名或 ID 模糊查找议员,查看完整档案及全部申报利益冲突,可只筛选主要职业或仍有效的委托。按行业领域和委员会交叉检索议员,并获取游说团体及其关联议员与组织。按标准、党派或委员会获取排名前列名单,以及各委员会的报酬透明度评分分布。通过刷新工具和状态工具管理本地每周数据转储。
适用场景
适合研究瑞士联邦政治:议员与委员会的利益冲突、游说关系、行业委托或报酬透明度。可与官方议会记录配合,回答某议员正式履职内容及其关联对象的问题。
运行要求
需要 Python 3.11 或更高版本,通过 uvx 或 pip 在本地运行;需要联网下载每周 Lobbywatch JSON 导出(压缩后约 17 MB)。无需认证或 API 密钥。可选环境变量控制传输方式、主机、端口、缓存目录与有效期、陈旧缓存时限、超时、CORS 来源、日志与 OpenTelemetry。
安装前请注意
会在本地下载并缓存约 17 MB 的公开数据集,并访问 Lobbywatch.ch 接口;响应可能来自最长 7 天的缓存并标记为陈旧。数据采用 CC BY-SA 4.0 许可,需署名。仅在认证网关之后才建议将 HTTP 绑定主机设为 0.0.0.0。当前转储未包含出入证数据。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Lobbywatch Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

🏛️ lobbywatch-mcp

[CI] [PyPI version] [Python] [License: MIT] [Data: CC BY-SA 4.0] [Swiss Public Data MCP Portfolio]

An MCP server that connects AI models to Lobbywatch.ch, the largest lobby database of the Swiss Federal Parliament — conflicts of interest, lobby groups, access badges, and transparency scores.

🇩🇪 Deutsche Version

Part of the Swiss Public Data MCP Portfolio — connecting AI models to Swiss public data sources.


🎯 Anchor Demo Query

"Welche Mitglieder der WBK-N haben Interessenbindungen zu Bildungsverlagen oder privaten Bildungsträgern, und wie ist ihre Transparenz-Bewertung?"

Which members of the National Council's Education Commission have declared conflicts of interest with educational publishers or private education providers, and how does their compensation transparency score compare?

→ More use cases by audience →

Demo

[Demo: Claude using lobbywatch_search_parlamentarier_nach_branche and lobbywatch_get_transparenzquote]


Overview

Lobbywatch.ch maintains the largest public database on Swiss federal parliamentarians and their connections to lobby organisations: 245 parliamentarians, ~7'800 interessenbindungen (declared mandates), 139 lobby groups, 368 access-badge holders, updated weekly, licensed CC BY-SA 4.0.

lobbywatch-mcp exposes this data to Large Language Models via the Model Context Protocol. It is designed to be used alongside parlament-mcp (the official Swiss Parliament's Curia Vista data): the pair makes it possible to ask what a parliamentarian did officially and who they are connected to — in a single conversation.

Features

  • Dump-first, API-fallback architecture. The weekly JSON dump is the primary source (stable, verified in production); the live dataIF REST API is used only where it returns reliable data (lobby groups, search).
  • Stale-cache fallback, never silent. If the dump cannot be refreshed, a cached copy up to 7 days old answers instead, and every dump-backed response then carries a stale block with its download time, age and the reason the refresh failed. The source is retried every 15 minutes; lobbywatch_refresh_dump never falls back.
  • Seven Phase 1 tools — parliamentarian lookup, conflict-of-interest listing, branche search, lobby group fetch, rankings, transparency quota, cache control.
  • CC BY-SA 4.0 attribution baked into every response via Pydantic envelopes.
  • Dual transport — stdio for Claude Desktop, streamable-http / sse for cloud deployments.
  • Fuzzy name matching via rapidfuzz for natural LLM input like "Jositsch" or "Wehrli".
  • No authentication required (Phase 1 — No-Auth-First).

Architecture

                    ┌─────────────────────────────┐   LLM client       │     LobbywatchClient        │  (Claude Desktop,  │                             │   Inspector, …)    │   ┌───────────────────┐     │        │           │   │  Dump cache       │     │      cms.lobbywatch.ch        │  MCP      │   │  (24 h TTL,       │     │      ┌──────────────────┐        ▼  stdio /  │   │   ~80 MB resident)├─────┼─────►│ weekly JSON      │   ┌─────────┐ HTTP │   └───────────────────┘     │      │ export (~17 MB)  │   │ FastMCP │◄────►│                             │      └──────────────────┘   │ server  │      │   ┌───────────────────┐     │      ┌──────────────────┐   └─────────┘      │   │  dataIF REST      ├─────┼─────►│ /interface/v1/   │                    │   │  (live fallback)  │     │      │   json/…         │                    │   └───────────────────┘     │      └──────────────────┘                    └─────────────────────────────┘

Outbound HTTP runs through a single httpx.AsyncClient with follow_redirects=False, an SSRF guard that blocks RFC1918 / link-local / metadata IPs, and an httpx event hook that re-resolves on every request. The dump path is the primary source of truth for parliamentarian queries; dataIF is only used for lobby group lookups and the search endpoint.

Prerequisites

  • Python 3.11 or newer
  • Internet access to download the weekly Lobbywatch JSON export (~17 MB zipped)

Installation

From PyPI (after first release):

bash
pip install lobbywatch-mcp

From source:

bash
git clone https://github.com/malkreide/lobbywatch-mcp.gitcd lobbywatch-mcppip install -e ".[dev]"

Usage

Standalone

bash
lobbywatch-mcp

This starts the server in stdio mode. For HTTP:

bash
LOBBYWATCH_MCP_TRANSPORT=http LOBBYWATCH_MCP_PORT=8000 lobbywatch-mcp

Container

A hardened multi-stage Dockerfile ships with the repo (non-root, read-only-rootfs compatible). See docs/deployment.md and deploy/docker-compose.example.yml for resource limits, sticky-LB guidance and egress hardening.

bash
docker build -t lobbywatch-mcp:0.2.0 .docker run --rm -p 127.0.0.1:8000:8000 lobbywatch-mcp:0.2.0

Claude Desktop

Add to your claude_desktop_config.json:

json
{  "mcpServers": {    "lobbywatch": {      "command": "uvx",      "args": ["lobbywatch-mcp"]    }  }}

A full example is provided in claude_desktop_config.json.

Example Queries

Once connected, try prompts such as:

  • "Give me the top 10 parliamentarians by number of interessenbindungen in the SP party."
  • "Which WBK-N members have mandates in the publishing or education industry?"
  • "Look up the lobby group 'economiesuisse' and list its connected parliamentarians."
  • "What is the compensation-transparency score distribution for the finance commission (FK-N)?"

Tools

All tool names use the lobbywatch_ namespace prefix (since 0.2.0) to avoid collisions with sibling portfolio servers.

ToolPurposeSource
lobbywatch_get_parlamentarier(name_or_id)Full profile + all conflicts of interestDump
lobbywatch_list_interessenbindungen(name_or_id, nur_hauptberuflich, nur_aktiv)Filtered mandate listDump
lobbywatch_search_parlamentarier_nach_branche(branche_query, kommission, limit)Cross-filter by industry and commissionDump
lobbywatch_get_lobbygruppe(name_or_id)Lobby group with connected MPs and organisationsLive dataIF
lobbywatch_get_ranking(kriterium, kommission, partei, limit)Top-N by criterionDump
lobbywatch_get_transparenzquote(kommission)Distribution of compensation transparency labelsDump
lobbywatch_refresh_dump() / lobbywatch_dump_status()Cache controlDump

Configuration

All behaviour is controlled via environment variables:

VariableDefaultPurpose
LOBBYWATCH_MCP_TRANSPORTstdioTransport (stdio, http, sse)
LOBBYWATCH_MCP_HOST127.0.0.1HTTP bind host (set to 0.0.0.0 only behind an auth gateway)
LOBBYWATCH_MCP_PORT8000HTTP bind port
LOBBYWATCH_MCP_CACHE_DIR~/.cache/lobbywatch-mcpDump cache location
LOBBYWATCH_MCP_CACHE_TTL86400 (24h)Cache time-to-live in seconds
LOBBYWATCH_MCP_STALE_MAX_AGE604800 (7 days)Oldest cached dump that may answer when the refresh fails, in seconds; 0 disables the fallback
LOBBYWATCH_MCP_HTTP_TIMEOUT60HTTP timeout in seconds
LOBBYWATCH_MCP_CORS_ORIGINS(unset)Comma-separated origin allow-list for HTTP/SSE; when set, exposes Mcp-Session-Id to browsers
LOBBYWATCH_MCP_LOG_FORMATtexttext (stdlib formatter) or json (structured via structlog)
LOBBYWATCH_MCP_LOG_LEVELINFODEBUG / INFO / WARNING / ERROR
LOBBYWATCH_MCP_OTEL_ENABLED0Set to 1 to enable OpenTelemetry tracing (requires pip install 'lobbywatch-mcp[obs]')
LOBBYWATCH_MCP_OTEL_ENDPOINT(unset)OTLP/HTTP collector endpoint (e.g. http://localhost:4318/v1/traces)

Project Structure

lobbywatch-mcp/├── src/lobbywatch_mcp/│   ├── __init__.py│   ├── __main__.py        # CLI + transport selection│   ├── config.py          # URLs, cache paths, attribution│   ├── client.py          # Dump download + dataIF client│   ├── models.py          # Pydantic v2 response envelopes│   └── server.py          # FastMCP tool registrations├── tests/│   ├── conftest.py        # Fixture parliamentarians│   ├── test_client.py     # Respx-mocked unit tests│   ├── test_server.py     # Tool integration tests│   └── test_live.py       # @pytest.mark.live — excluded from CI├── .github/workflows/│   ├── ci.yml             # Test matrix + ruff│   └── publish.yml        # PyPI OIDC Trusted Publisher├── claude_desktop_config.json├── pyproject.toml└── ...

Data License & Attribution

The code is released under the MIT License.

The data served through this MCP is © Lobbywatch.ch and licensed under CC BY-SA 4.0. Every response envelope includes the attribution string. Downstream users must:

  1. Credit Lobbywatch.ch as the data source.
  2. Share derivative datasets under the same CC BY-SA 4.0 terms.
  3. Understand that Lobbywatch is a community-researched database — not an official register. It is authoritative for transparency research but should not be confused with the Federal Parliament's own declarations.

Known Limitations

  • The upstream /table/parlamentarier/... dataIF REST endpoint currently returns empty result sets. The server works around this by using the weekly JSON dump instead.
  • zutrittsberechtigungen (access badges) are not populated in the "essential" dump variant used here. A future release will add a dedicated tool using the non-essential dump.

Contributing

See CONTRIBUTING.md.

Security

See SECURITY.md for the security posture, accepted-risk decisions, and how to report a vulnerability.

MCP Protocol Version

This server speaks two protocol eras over the same endpoint. The client's first request on a connection decides which one applies; a later claim from the other era is refused.

EraRevisionWho reaches it
initialize handshake2024-11-05 … 2025-11-25What today's clients speak. The server answers with the revision asked for, or with the 2025-11-25 ceiling when the request asks for something newer.
Per-request envelope2026-07-28A request carrying the 2026-07-28 _meta envelope opens a modern connection.

Both revisions are pinned in tests/test_protocol_version.py and asserted against the installed SDK, so a Dependabot bump of mcp cannot move either one silently. The constants alone are the weaker form, so tests/test_spec_2026_07_28.py measures both eras through the assembled ASGI app: server/discover without a session, an initialize asking for a future revision capped at 2025-11-25, and every tool called over a 2026-07-28 connection with SDK deprecations raised as errors.

Native to 2026-07-28. lobbywatch_refresh_dump reports its progress as notifications/progress, which both eras deliver to any client that sends a progressToken. It used to log via notifications/message; logging is deprecated in 2026-07-28 (SEP-2577) and only delivered on requests that opt in with a log level, so modern clients silently received nothing. serverInfo now carries the package version — under 2026-07-28 it is stamped into the _meta of every response.

Note that the SDK's LATEST_PROTOCOL_VERSION is an alias for the modern era, not for the handshake era — pinning against it alone would leave the era that current clients actually negotiate free to drift.

Update policy. When the gate fails, do not edit the constant blindly: read the spec changelog between the two revisions, verify the server still behaves, then move the constant, this section, README.de.md and CHANGELOG.md together.

Changelog

See CHANGELOG.md.

License

MIT License — see LICENSE. Data CC BY-SA 4.0 — see NOTICE.md.

Author

malkreide · GitHub


Part of the Swiss Public Data MCP Portfolio.

Installation

Run via uv's uvx — no clone or manual install needed. Add to your MCP client config (mcpServers for Claude Desktop, Cursor and Windsurf; use a top-level servers key for VS Code in .vscode/mcp.json):

json
{  "mcpServers": {    "lobbywatch-mcp": {      "command": "uvx",      "args": [        "lobbywatch-mcp"      ]    }  }}

来源:README.md,提交 5219951

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

3
  1. v0.3.8最新Oct 14, 2026
  2. v0.3.7Sep 27, 2026
  3. v0.3.6Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分