OpenDataMCP
Related Servers
Alternatives to OpenDataMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceSearch, preview, and analyze datasets from 20+ platforms and millions of datasets via a single MCP connector. Works with Claude instantly7 npm29MIT
- AlicenseNot gradedqualityDmaintenanceUnified MCP server for discovering open datasets across Hugging Face, Zenodo, and Kaggle, with ranked search results and one-click Colab starter code generation.1MIT
- AlicenseNot gradedqualityDmaintenanceAccess to many public datasets right from your LLM application.155MIT
- AlicenseAqualityBmaintenanceAn MCP server that puts open data on tap, enabling LLM clients to search, inspect, and query 30,000+ civic datasets from Socrata portals with built-in guardrails like row caps and actionable error messages.4MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that connects to open data portals like CKAN and Socrata, enabling natural language querying of datasets via Claude.MIT
- AlicenseNot gradedqualityBmaintenanceProvides queryable access to official UAE open data through MCP tools, resources, and prompts, with bilingual support and multiple data connectors.6 npm3MIT
TDQS
Scored across 3 tools
Each tool targets a reasonably distinct resource: traffic information, railway lines, and rolling stock. However, rail-traffic-info and railway-lines could be confused in situations involving line status or operations, since both could plausibly return similar operational information.
All tool names use lowercase hyphenated noun phrases, which gives the set a consistent overall style. The minor inconsistency between 'rail', 'railway', and 'rolling-stock' is noticeable but does not cause significant confusion.
Three tools is on the lean side, but each one covers a meaningful area of rail open data: traffic, infrastructure, and vehicles. The count is reasonable for a specialized read-only data server, though it could be expanded.
The set covers several core rail datasets, but there are obvious gaps such as stations, schedules, departures, and disruptions unless they are implicitly included in traffic info. Agents working with broader rail queries would likely need additional tools.