civic-library-mcp
Related Servers
Alternatives to civic-library-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI agents grounded access to US natural-hazard data — weather alerts, forecasts, earthquakes, and FEMA flood zones — from free, keyless US government APIs.MIT
- AlicenseAqualityCmaintenanceNode.js MCP server enabling AI agents to access comprehensive U.S. Census Bureau demographic and economic data, including ACS, decennial census, and business patterns.1738 npmMIT
- FlicenseNot gradedqualityCmaintenanceRemote MCP server exposing US Census (ACS 5-year) and FEMA flood data. Works as a connector in both Claude and ChatGPT.-
- AlicenseAqualityDmaintenanceOpen-source MCP server providing real estate regulatory intelligence (zoning, permits, entitlements, deal scoring) for US properties, enabling AI agents to access 10 callable tools.129 npmMIT

city-data-mcpofficial
FlicenseAqualityDmaintenanceAn MCP server that gives Claude deep access to US public data -- demographics, economics, crime, employment, weather, housing, transit, schools, budgets, and more across 30+ cities for government intelligence workflows.28-- AlicenseAqualityBmaintenanceMCP server giving agents canonical access to 180M+ US parcels with ownership, valuation, permits, deeds, hazard, and market data.857 npmApache 2.0
TDQS
Scored across 5 tools
Most tools are clearly distinct, but geocode_address and lookup_census_tract overlap in that geocode_address can already provide tract information for an address, while lookup_census_tract does so for coordinates. check_opportunity_zone also accepts multiple input types, potentially causing confusion about which tool to use for a given input.
All tool names follow a consistent verb_noun pattern: geocode_address, lookup_census_tract, check_opportunity_zone, get_tract_demographics, check_flood_zone. There is no mixing of styles or ambiguous naming.
With exactly 5 tools, the server is well-scoped for a civic data lookup library. Each tool serves a distinct purpose and there are no redundant or filler tools.
The tool set covers the key workflows: address to coordinates/tract, reverse geocoding, opportunity zone checks, demographics, and flood zones. A minor gap is the lack of a 2010 census tract lookup for compatibility with check_opportunity_zone, but since that tool can accept addresses/coordinates directly, it's not a dead end.