Home / MCP registry index / com.openpublica/civic-meetings
OpenPublica
com.openpublica/civic-meetings in the official MCP registry.
Endpoint https://api.openpublica.com/mcp.
The registry describes it as: Search US local-government meetings: AI summaries, transcripts, and adopted plan documents.
We read its 16 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_meeting_content search_meetings_semantic list_recent_meetings get_meeting search_meeting_transcript find_local_governments find_governments_by_name find_governments_by_zip get_government_info get_government_stats discover_meeting_vocabulary list_government_documents get_document read_document_pages search_documents get_coverage_overview
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-openpublica-civic-meetings)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.