Data Piercecounty
Server Details
Pierce County Open Data (internal.open.piercecountywa.gov) Socrata MCP.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-data-piercecounty
- GitHub Stars
- 0
- Server Listing
- mcp-data-piercecounty
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 47 tools
Several clusters are near-indistinguishable: ask_pipeworx, ask_pipeworx_beta (admittedly identical right now), ask_pipeworx_grounded and deep_research all answer questions over the same 7,212-tool catalog, and bet_research / polymarket_edges / polymarket_arbitrage / polymarket_fill_risk all fan out over prediction markets with overlapping intent. Company lookups (entity_profile, company_facts, compare_entities, resolve_entity, recent_changes) and discovery (discover_tools vs suggest_questions) also overlap. Descriptions are exhaustive and often disambiguate in prose, but the sheer number of similar entry points makes misselection likely.
Casing is uniformly snake_case, which is good, but the verb/noun convention is mixed: verb_noun tools (query, remember, forget, subscribe, validate_claim, generate_llms_txt) sit alongside bare nouns and noun phrases (datasets, metadata, entity_profile, company_facts, deep_research, bet_research, prediction_calibration, release_calendar_markets, kalshi_weather_edge). Readable, but not a predictable pattern an agent can infer from.
47 tools is well past the point where a single server is scannable, and the surface mixes three unrelated domains (Pierce County open data, the Pipeworx research gateway, and a large Polymarket/Kalshi trading suite). The three Pierce County tools look like a vestigial appendage rather than an earned part of the set.
The set references tools it does not expose: resolution_audit tells callers to fetch markets via polymarket_market / kalshi_market / polymarket_us_search, research_row and resolution_audit depend on fetch_url, and release_calendar_markets cites fomc_calendar and pdufa_catalysts — none are present, creating dead ends. Raw market lookup, generic fetch, and any batch/parallel execution primitive are missing from an otherwise sprawling surface.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
King County Open Data (data.kingcounty.gov) Socrata MCP.
Sonoma County Open Data (data.sonomacounty.ca.gov) Socrata MCP.
Santa Clara County Open Data (data.sccgov.org) Socrata MCP.
Howard County Open Data (opendata.howardcountymd.gov) Socrata MCP.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for accessing Prince William County, Virginia geospatial data (ArcGIS). Enables searching datasets, querying layers, and retrieving schema information.57 npmMIT
- AlicenseNot gradedqualityBmaintenanceDataCambridge MCP — Cambridge open data (data.cambridgema.gov, Socrata SODA API).157 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for accessing data.ny.gov datasets via the Socrata Open Data API, enabling search, query, metadata retrieval, and column value exploration.81 npm1MIT

open-signalsofficial
AlicenseNot gradedqualityBmaintenancePublic hazard, water, weather and EPA data with source, age and licence on every reading, as MCP tools, REST and GeoJSON layers.Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.