io.github.cyanheads/socrata-mcp-server

It requires SOCRATA_APP_TOKEN and a default domain configuration; the app token is sensitive and could be abused to make Socrata API requests or consume quota if exposed. The materials do not show requests for unrelated extra credentials.

It declares access to socrata.caseyjhand.com, which is broadly consistent with its stated purpose of querying Socrata open-data portals. Network use means query content and related inputs may be sent remotely, but the provided materials do not indicate exfiltration to unrelated or unknown third-party endpoints.

The system checks indicate it executes code/processes locally, which is a common MCP tool capability. The available materials do not show any need for high-privilege system actions, shell-injection style behavior, or execution scope clearly inconsistent with its stated function.

The materials do not specify which local files it reads/writes or what data it persists, so visibility is limited; at minimum, it will handle user query inputs and data exchanged with the Socrata API. There is no stated request for broad filesystem access or other obvious over-privileging, but it is prudent to assume it can access runtime inputs and configuration.

It comes from an official registry and has an auditable open-source repository with updates in the last year, which are strong positive signals. Low community stars and an unspecified license add some uncertainty, but without other red flags the supply-chain posture is overall low risk.