MCP.Market

Charlotte Open City Data MCP server

online · 43% uptime
by ajwann·io.github.ajwann/queensestate·v1.0.1
No reviews yet

Charlotte and Mecklenburg County open data: addresses, crime, 311, zoning, budget, and services

A94/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A94/100

full report

Adoption
Growing

0 stars20 downloads/wk

Reviews

Write one

Nobody has reviewed Charlotte Open City Data yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Charlotte Open City Data tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings
  • Code scan15 source files scanned25/25
  • Live reliabilityremote reachable in 192ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 42 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 94/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Charlotte Open City Data compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
94/100
higher than 96% of 48,243 servers
Uptime
43%
of our recent checks; the typical remote server answers 100%
Response time
199 ms
faster than 67% of 30,027 servers
Downloads a week
20
more than 7% of 12,306 servers with a package

Release history: 2 versions in the registry since 2026-09-19, latest 2026-09-20, typically one every 1 day.

Install Charlotte Open City Data in Claude Code, Cursor or VS Code

claude mcp add --transport http queensestate https://queensestate.adamwanninger.com/mcp
Add to Cursor

What the publisher says

From the Charlotte Open City Data repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.ajwann/queensestate -->

QueensEstate ♔⛫

An MCP server that lets an LLM answer Charlotte residents' everyday questions with official public data from the City of Charlotte Open Data Portal — .

The portal lives at data.charlottenc.gov.

It is an ArcGIS Hub site; its ~380 datasets are ArcGIS REST layers run by the City of

Charlotte and Mecklenburg County. No API key is required.

What's on the portal

A survey of the catalog (/api/feed/dcat-us/1.1.json) shows these main themes:

Tools

The tools are chosen for the questions residents actually ask. Every tool is read-only, and every location parameter accepts either an address ("600 E 4th St, Charlotte") or "latitude,longitude".

My address

Safety

City services and neighborhood change

Places and transit

Government transparency

Anything else in the catalog

Setup

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-11-01restoreC → Ascore 94
  • 2026-10-25downgradeA → Cscore 67: Remote endpoint did not respond
  • 2026-10-09restoreB → Ascore 98
  • 2026-10-02downgradeA → Bscore 71: Remote endpoint did not respond

Charlotte Open City Data: common questions

Is Charlotte Open City Data MCP server safe?
Yes, by our scan: it is graded A (94/100). Read the Charlotte Open City Data safety report
How do I install Charlotte Open City Data?
It runs remotely at queensestate.adamwanninger.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Charlotte Open City Data need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Charlotte Open City Data maintained?
The last commit was 46 days ago (2026-09-20). The latest release is v1.0.1.
Is Charlotte Open City Data up?
43% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Charlotte Open City Data compare with other MCP servers?
safety score 94/100 (higher than 96% of 48,243 servers); uptime 43% (of our recent checks; the typical remote server answers 100%); response time 199 ms (faster than 67% of 30,027 servers). Full comparison.