Home / MCP registry index / org.georgiacommons/georgia-commons
Georgia Commons
org.georgiacommons/georgia-commons in the official MCP registry.
Endpoint https://mcp.georgiacommons.org/mcp. Source: github.com/shanejorr/georgiacommons.
The registry describes it as: Georgia's Code, bills, and Supreme Court opinions as source text. Independent, not the State.
We read its 23 tools on 2026-10-21. 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
describe_site get_coverage search fetch verify_quote opinions_lookup opinions_get_text opinions_list opinions_search bills_lookup bills_get_text bills_list bills_search code_describe_structure code_lookup_section code_lookup_sections code_browse code_get_chapter code_search code_find_chapter code_find_act constitution_lookup constitution_browse
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/org-georgiacommons-georgia-commons)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.