Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Georgia Civic Data is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Georgia education, Census, and immigration data: query, filter, aggregate, and link datasets.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http georgia-civic-data-mcp https://mcp.georgiacivicdata.org/mcp/
# 2 — ask your agent for something these tools do
# list_datasets, search_datasets, describe_dataset and 10 more
Georgia Civic Data costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http georgia-civic-data-mcp https://mcp.georgiacivicdata.org/mcp/Reconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Enumerate every approved Georgia dataset (topic) and the shared dimensions. Each topic entry is a LEAN summary — name/keys, year coverage (year_min/year_max + year_gaps), detail levels + default detail, a has_demographic flag (false = no demographic axis, so there is no all-students demographic row to filter), tags, contract version, and a one-line description — enough to pick a topic; call descri
No parameter schema on file.
Keyword search over the catalog metadata (topic names, descriptions, tags, AND column names/descriptions) — the discovery entry point when you don't know the exact topic name. Returns lean topic summaries per hit with a relevance score and which fields matched, plus a dimension_matches list when the query also hits a dimension (e.g. 'district'). Most acronyms work; the short ones ap/el/ib
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| limit | integer | no | — |
Full schema for one topic: every column (name/type/role/unit/value range/null-meaning), the exact filters list with enum values (read this before query_dataset — it is the authoritative set of filter keys), the FK→dimension join shape (foreign_keys), example queries, usage, limitations, null semantics, tags, and schema_hash (for cache/drift detection). The top-level key_metric names the si
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | — |
| main_topic | string | no | — |
| verbosity | string | no | 'full' (default) or 'schema' (drops prose; keeps columns/filters/enums/key_metric/recommended_query). |
Query one topic's gold facts with dimension labels joined in (the district/school/county/demographic names come back on every row). filters is a dict of column → value or list-of-values: FK codes (district_code, school_code, county_fips, demographic) and any categorical column — see describe_dataset's filters for the exact keys and enum values. Use year (exact) OR year_min/year_max (rang
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Topic name, e.g. 'act_scores'. |
| main_topic | string | no | Main topic: 'education', 'census', or 'immigration'. |
| filters | no | Column → value (or list of values) filters. Keys are FK columns (district_code, school_code, county_fips, demographic) and categorical columns; read describe_dataset's filters for the exact keys and | |
| year | no | Exact year. Use this OR year_min/max. | |
| year_min | no | Inclusive lower year bound (range). | |
| year_max | no | Inclusive upper year bound (range). | |
| detail | no | Grain (e.g. schools/districts/states); default finest. | |
| limit | no | Page size (default 100, max 500). | |
| offset | integer | no | Row offset for paging (>= 0). |
| columns | no | Project only these output columns (fact columns + joined label columns). Smaller pages / fewer column reads. Omit for all columns. | |
| include_labels | boolean | no | Join district/school/county/demographic name columns (default true); false = codes only (faster, leaner). |
| order_by | no | Order by one fact column or joined label column (for server-side top-N). Default order is the row grain. NULL (suppressed) cells sort LAST in either direction, so a metric top-N is never polluted by s | |
| order | string | no | Sort direction for order_by: 'asc' or 'desc'. |
List the distinct values of ONE filterable column of a topic — the fast way to learn valid filter values before query_dataset, especially for FREE categoricals and FK codes (district_code/school_code/county_fips/demographic) that carry no enum in describe_dataset (a wrong guess otherwise returns an empty page with no error). column must be a filterable column (see describe_dataset's filters).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | — |
| column | string | yes | — |
| prefix | no | — | |
| limit | integer | no | — |
| main_topic | string | no | — |
| detail | no | — |
Compute a grouped aggregate over one topic — the aggregation-first path. agg is one of avg/sum/min/max/count/weighted_rate; metric is a metric column (DEFAULTS to the topic key_metric; ignored for count); group_by is a list of grain columns (year, FK codes like district_code or county_fips, or categoricals — see describe_dataset). weighted_rate computes a true population-weighted SUM(numer
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | — |
| metric | no | — | |
| agg | string | no | — |
| group_by | no | — | |
| filters | no | — | |
| year | no | — | |
| year_min | no | — | |
| year_max | no | — | |
| detail | no | — | |
| limit | no | — | |
| offset | integer | no | — |
| order_by | no | — | |
| order | string | no | — |
| main_topic | string | no | — |
Resolve a place or demographic NAME or CODE to its stable keys + labels — the right way to turn 'Atlanta Public Schools' / 'Fulton' / a raw code into the district_code / school_code / county_fips / demographic to filter by (a wrong code guess otherwise returns an empty query_dataset page). kind is district / school / county / demographic ('Fulton' as kind='county' → the county; as kind='district
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | — |
| query | string | yes | — |
| limit | integer | no | — |
Schema for one dimension (districts / schools / counties / demographics): the (possibly composite) primary key, the attribute columns a join attaches, the cross-dataset link_keys (e.g. districts.district_census_id → Census via the crosswalk — a 5-digit school-district code, NOT a county FIPS), and demographics semantics (within a category the values are mutually exclusive; all is the denomin
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
Paginated read of a dimension table — the label lookups (district names, school names, county names, demographic labels). Rows are ordered by the dimension's primary key so paging is stable. Use describe_dimension for the schema and link keys. Small page defaults; truncated + a bulk_export pointer signal when to pull the full table elsewhere.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| limit | no | — | |
| offset | integer | no | — |
Return the authoritative ODCS v3.2 data contract for a topic (kind='topic') or a dimension (kind='dimension') so you can consume the machine-readable schema without cloning the repo. fmt='yaml' (default) returns the document verbatim as text; fmt='json' returns it parsed. Only approved topics and loaded dimensions expose a contract.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| main_topic | string | no | — |
| kind | string | no | — |
| fmt | string | no | — |
Which Georgia public school attendance zones (elementary, middle, high) contain a place, or (attendance_rules=true) how attendance zones work in Georgia. Give exactly one of: lat + lon; an address (geocoded by the U.S. Census Geocoder); a 2020 census tract_geoid (returns every zone covering the tract with the share of its 2020 population in each, or, when none does, a coverage_reason saying why);
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lat | no | — | |
| lon | no | — | |
| address | no | — | |
| tract_geoid | no | — | |
| grade | no | — | |
| year | no | — | |
| attendance_rules | boolean | no | — |
| lang | string | no | — |
List the tables link_query can read (curated gold paths only) and the join keys that bridge facts → dimensions → Census geography. Call this BEFORE writing a link_query. Two-tier to stay context-cheap: with NO arguments it returns a LEAN index — every table's name, grain, detail levels, default read_parquet(...) snippet, and join keys (enough to pick tables and write a single-detail join). To ge
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tables | no | — |
Run a cross-dataset / cross-topic analytical SQL query that the per-topic query_dataset filters can't express — e.g. join education, Census, or immigration facts to a dimension (or another dataset) on shared geography (immigration and Census county topics share county_fips directly). READ-ONLY, SANDBOXED DuckDB: one SELECT (or WITH … SELECT); no DDL/DML/COPY/ATTACH/INSTALL/PRAGMA/SET/CALL; you may
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sql | string | yes | — |
| limit | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Georgia Civic Data or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Georgia Civic Data can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.