Georgia Commons
REMOTE · MCP.GEORGIACOMMONS.ORG · SCANNED SEP 24
Georgia's Code, bills, and Supreme Court opinions as source text. Independent, not the State.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3391 tokens (~147/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (13% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Georgia Commons MCP server?
Georgia Commons is a hosted endpoint at https://mcp.georgiacommons.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.georgiacommons.org
claude mcp add --transport http org-georgiacommons-georgia-commons 'https://mcp.georgiacommons.org/mcp'
{
"mcpServers": {
"org-georgiacommons-georgia-commons": {
"url": "https://mcp.georgiacommons.org/mcp"
}
}
} {
"servers": {
"org-georgiacommons-georgia-commons": {
"type": "http",
"url": "https://mcp.georgiacommons.org/mcp"
}
}
} [mcp_servers.org-georgiacommons-georgia-commons] url = "https://mcp.georgiacommons.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-georgiacommons-georgia-commons": {
"type": "remote",
"url": "https://mcp.georgiacommons.org/mcp",
"enabled": true
}
}
} openclaw mcp add org-georgiacommons-georgia-commons --url 'https://mcp.georgiacommons.org/mcp' --transport streamable-http
mcp_servers:
org-georgiacommons-georgia-commons:
url: "https://mcp.georgiacommons.org/mcp" {
"McpServers": {
"org-georgiacommons-georgia-commons": {
"Transport": "http",
"Url": "https://mcp.georgiacommons.org/mcp"
}
}
} assistant mcp add org-georgiacommons-georgia-commons -t streamable-http -u 'https://mcp.georgiacommons.org/mcp'
{
"mcpServers": {
"org-georgiacommons-georgia-commons": {
"type": "http",
"url": "https://mcp.georgiacommons.org/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: excellent → good functional
- 19 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: good → excellent functional
- 17 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 16 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “fetch” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- 15 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “bills_lookup” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- 14 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “opinions_lookup” rewrote its description, which is the text the model reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://mcp.georgiacommons.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.georgiacommons.org | CN=YR1,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | RSA 2048 | SHA256-RSA | 54993a09d9d0e4a4a8c85d59876640d23c0 |
| SANs: mcp.georgiacommons.org | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.georgiacommons.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| georgiacommons.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.georgiacommons.org/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.georgiacommons.org/mcp | HTTPS enforced | 301 | https://mcp.georgiacommons.org/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bills_get_text ~68
The stored text of a bill alone, windowed by `start` and `max_chars` (default 60,000), with a pointer to continue.
| Name | Type | Req | Description |
|---|---|---|---|
| bill | string | yes | – |
| max_chars | integer | – | – |
| session | – | – | – |
| start | integer | – | – |
No output schema declared.
No examples provided.
bills_list ~131
The bills of a session (the newest when `session` is omitted), in number order, 25 a page: `id, title, status, URL`. Filter by `kind` (hb, sb, hr, sr), `chamber` (H or S), LegiScan `status` code, a caption `subject` (a headings search), or words `q`.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | – | – | – |
| kind | – | – | – |
| limit | integer | – | – |
| q | – | – | – |
| session | – | – | – |
| start | integer | – | – |
| status | – | – | – |
| subject | – | – | – |
No output schema declared.
No examples provided.
bills_lookup ~163
One bill or resolution of the Georgia General Assembly by number in any written form (HB 136, H.B. 136, House Bill 136, 2025-2026/hb136, a LegiScan id), as the same Markdown twin the site serves: frontmatter (cite_as, canonical_url, source_url, status), the verbatim text, the summaries Georgia Commons wrote under a heading that says so, and status. With no `session`, a number means the newest regular session that has it; name the session (2026-special) for a special session's bill that shares its number. `full` adds history, votes, and amendments.
| Name | Type | Req | Description |
|---|---|---|---|
| bill | string | yes | – |
| full | boolean | – | – |
| session | – | – | – |
No output schema declared.
No examples provided.
bills_search ~91
Full-text search over bill text, titles, and the labeled summaries. A bare bill number is a direct lookup. Search matches the words of the document: ask in the words the bill would use. `in_headings` searches only titles, topic tags, and subjects.
| Name | Type | Req | Description |
|---|---|---|---|
| in_headings | boolean | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| session | – | – | – |
No output schema declared.
No examples provided.
code_browse ~53
The hierarchy: the titles (no argument), a title's chapters ('36'), or a chapter's sections ('36-60'), one line each with counts, citation spans, and twin URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| node | – | – | – |
No output schema declared.
No examples provided.
code_describe_structure ~52
Call first for the Code. The citation grammar, how to find a section without its citation, how versions and statuses work, what is and is not in the text, and the list of titles. Cheap.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
code_find_act ~46
Laws by the short title the statute states ('Joshua's Law', 'Georgia Lemonade Stand Act'): the citing section and the unit the name covers.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
code_find_chapter ~53
For 'I know the topic but not the citation': the titles, chapters, articles, and parts whose headings carry the words, with the code_browse call that lists each.
| Name | Type | Req | Description |
|---|---|---|---|
| words | string | yes | – |
No output schema declared.
No examples provided.
code_get_chapter ~93
Every section of a chapter with its text, in order, windowed by max_sections (default 40) and max_chars (default 100,000); the output ends with a pointer to continue or 'End of chapter.'
| Name | Type | Req | Description |
|---|---|---|---|
| chapter | string | yes | – |
| max_chars | integer | – | – |
| max_sections | integer | – | – |
| start | integer | – | – |
| title | integer | yes | – |
No output schema declared.
No examples provided.
code_lookup_section ~139
One Code section by citation in any written form (44-7-34, 'O.C.G.A. § 44-7-34', 'Title 44, Chapter 7, Section 34'), as the same Markdown twin the site serves: frontmatter (cite_as, canonical_url, source_url, status, version), the verbatim text, then the notes capped. `version` picks a printed version by its qualifier; `subsection` ('a', 'a-1') renders one part. A 404 names the neighboring sections.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | – |
| subsection | – | – | – |
| version | – | – | – |
No output schema declared.
No examples provided.
code_lookup_sections ~83
Several sections at once: a list ('44-7-30, 44-7-31 and 44-7-34') or a range ('44-7-30 through 44-7-35'), up to 40 sections under a 150,000-character cap, with a trailer naming anything not rendered.
| Name | Type | Req | Description |
|---|---|---|---|
| citations | string | yes | – |
No output schema declared.
No examples provided.
code_search ~170
Full-text search of the Code: words, or a citation, or both. A citation among words returns that section first; a query that names an act returns the section stating its short title first; a query that is a passage of a provision word for word returns that provision first. Search matches the words of the document: ask in the words the statute would use. `in_headings` searches only headings and catchlines and adds the matching units. `scheme` picks the collection: `ocga` (default), `ga` for the Georgia constitution, `us` for the United States constitution.
| Name | Type | Req | Description |
|---|---|---|---|
| chapter | – | – | – |
| in_headings | boolean | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| scheme | string | – | – |
| title | – | – | – |
No output schema declared.
No examples provided.
constitution_browse ~48
The articles and sections of a constitution ('ga' or 'us'), or one article's provisions, one line each with twin URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| node | – | – | – |
| scheme | string | yes | – |
No output schema declared.
No examples provided.
constitution_lookup ~84
One provision of the Georgia ('ga') or United States ('us') constitution as printed in the O.C.G.A., by citation ('Art. I, Sec. I, Para. I', 'Amend. XIV', 'Preamble') or slug, as its Markdown twin with the case annotations capped.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | – |
| scheme | string | yes | – |
No output schema declared.
No examples provided.
describe_site ~42
Call first. What Georgia Commons holds, which collections this server has loaded, the id and URL grammar, which tool to call next, and the independence statement. Cheap.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fetch ~146
The full document for an id from search (code:44-7-34, ga-const:art-i-sec-i-para-i, bill:2025-2026/hb136, opinion:S26A0060): the same Markdown twin the site serves at url plus .md (frontmatter, verbatim text, any summaries under a heading that names them), with url the canonical page for citation and metadata from the frontmatter. `full` adds the optional material, or for the Code and constitutions the first 60,000-character page of the notes, whose frontmatter names the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | – |
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | yes | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_coverage ~36
Exactly what is loaded, computed from the stores now: coverage sentences, corpus versions, counts, sessions, years, dates, licenses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
opinions_get_text ~63
The stored text of an opinion alone, windowed by `start` and `max_chars` (default 60,000), with a pointer to continue.
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | – |
| opinion | string | yes | – |
| start | integer | – | – |
No output schema declared.
No examples provided.
opinions_list ~104
The opinions filed in a year (the newest year when omitted), in filing order, 25 a page: `docket, date, case name, case type, URL`. Filter by `case_type` (criminal appeal, civil, bar discipline, habeas, certified question, election, other) or words `q`.
| Name | Type | Req | Description |
|---|---|---|---|
| case_type | – | – | – |
| limit | integer | – | – |
| q | – | – | – |
| start | integer | – | – |
| year | – | – | – |
No output schema declared.
No examples provided.
opinions_lookup ~171
One Supreme Court of Georgia opinion by docket in any case (S23A0421), reporter citation (317 Ga. 528, 883 S.E.2d 746), record id (a CourtListener cluster id, or ga- and the docket for a record read from the court's own website), or case name, as the same Markdown twin the site serves: frontmatter (cite_as, canonical_url, source_url, record_source, date, status), the verbatim opinion, then the summaries Georgia Commons wrote under a heading that says so. When several opinions share a docket this is the most recent and the frontmatter lists the others. `full` adds the summarized reasoning, checked quotes, and the upstream opinion records.
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | – |
| opinion | string | yes | – |
No output schema declared.
No examples provided.
opinions_search ~101
Full-text search over opinion text, case names, and the labeled summaries. A bare docket or citation is a direct lookup. Search matches the words of the document: ask in the words the court would use. `in_headings` searches only case names, legal areas, and case types.
| Name | Type | Req | Description |
|---|---|---|---|
| case_type | – | – | – |
| in_headings | boolean | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| year | – | – | – |
No output schema declared.
No examples provided.
search ~99
Search every loaded collection (or one, with `collection` = code, bills, or opinions) and return up to ten results as {id, title, url}. A Code or constitution citation, bill number, or docket in the query comes first. Search matches the words of the document. Ask in the words the document would use, not the words of the question. Follow with fetch(id).
| Name | Type | Req | Description |
|---|---|---|---|
| collection | – | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
verify_quote ~72
Whether a quote appears verbatim in the stored text of a document (after normalizing quotes, dashes, whitespace, and [T]he-style alterations, as the ingestion filter does). Deterministic; use it before relying on a quotation.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| quote | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| chars | integer | yes | – |
| id | string | yes | – |
| occurrences | integer | yes | – |
| source_field | – | yes | – |
| url | string | yes | – |
| verified | boolean | yes | – |
No examples provided.
What is the Georgia Commons MCP server?
Georgia Commons is an MCP server listed in the public MCP registry as org.georgiacommons/georgia-commons. Georgia's Code, bills, and Supreme Court opinions as source text. Independent, not the State. This page covers its hosted endpoint (https://mcp.georgiacommons.org/mcp).
Is the Georgia Commons MCP server safe to use?
Georgia Commons scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Georgia Commons MCP server expose?
Georgia Commons exposes 23 tools: describe_site, get_coverage, search, fetch, verify_quote, and 18 more. Their descriptions and schemas cost roughly 2,108 tokens of context every time the server is loaded.
Does the Georgia Commons MCP server require authentication?
No. We connected to Georgia Commons without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Georgia Commons MCP server still maintained?
Georgia Commons is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.