# Georgiacivicdata Georgia Civic Data MCP server

Source: https://glimind.com/server/mcp-registry%2Forg.georgiacivicdata%2Fgeorgia-civic-data
Registry id: `mcp-registry/org.georgiacivicdata/georgia-civic-data`
Status: live (checked 2026-10-27T09:16:34.584Z)

## Verdict

Georgiacivicdata Georgia Civic Data MCP server answered 99.98% of Glimind's liveness checks over 30 days, better than 41% of MCP servers, with 1037 ms median handshake and 1 outage in 90 days. Its agent-readiness grade is A (96/100) across 13 tools, costing an agent about 5,708 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.98% | 41% of MCP servers |
| Median handshake latency | 1037 ms | 16% of MCP servers |
| p95 handshake latency | 3147 ms | — |
| Checks in 30 days | 5,015 | — |
| Outages, 90 days | 1 | — |
| Median recovery | 7 min | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 13 | — |
| Tool-list size for an agent | ~5,708 tokens | 37% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "georgiacivicdata-georgia-civic-data-mcp-": {
      "type": "http",
      "url": "https://mcp.georgiacivicdata.org/mcp/"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http georgiacivicdata-georgia-civic-data-mcp- https://mcp.georgiacivicdata.org/mcp/
```

## Tools (13)

- `aggregate`: A summary of one dataset computed on the server: one small row per group instead of raw rows. `agg` is avg, sum, min, max, count, or weighted_rate. `metric` is 
- `describe_dataset`: The full schema of one dataset: every column (type, role, unit, value range, what a NULL means), the exact `filters` with their valid values (the keys query_dat
- `describe_dimension`: The schema of one shared lookup table (a dimension: districts, schools, counties, tracts, block_groups, or demographics): its key columns (schools use district_
- `distinct_values`: The distinct values of one filter column of a dataset, to learn valid filter values before query_dataset. Most useful for code columns (district_code, school_co
- `get_contract`: The full data contract of one dataset (kind='topic') or lookup table (kind='dimension'): the machine-readable document, in the Open Data Contract Standard (ODCS
- `get_dimension`: The rows of one shared lookup table: district, school, county, census tract, or demographic codes with their names and attributes, in key order so paging is sta
- `link_query`: Runs one read-only SQL query across datasets, for analysis the per-dataset filters cannot express, such as joining education, Census, or immigration figures to 
- `link_tables`: The tables link_query can read and the keys that join them: datasets to lookup tables to Census geography. With no arguments, a short index: each dataset's `tab
- `list_datasets`: The catalog: every published Georgia dataset and the shared lookup tables (district, school, county, census tract, and demographic names). By default each datas
- `lookup_school_zone`: Which Georgia public school attendance zones (elementary, middle, high) contain a place, or (attendance_rules=true) how attendance zones work in Georgia. Give e
- `query_dataset`: Rows of one dataset, filtered, with the district, school, county, and demographic names joined in. `filters` takes code columns and category columns (describe_d
- `resolve_entity`: Turns a place or demographic name or code into the code the data uses (district_code, school_code, county_fips, or demographic) with its label, e.g. 'Atlanta Pu
- `search_datasets`: Keyword search over the catalog: dataset names, titles, descriptions, tags, and column names and descriptions. Returns short dataset summaries ranked by relevan

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.