contexte
OfficialRelated Servers
Alternatives to contexte
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAccess to many public datasets right from your LLM application.155MIT
- AlicenseAqualityCmaintenanceConnects LLMs to over 2,850 datasets from 13 Catalan and Spanish open data portals, enabling natural language search and real-time queries of public data.8112 npm22MIT
- AlicenseNot gradedqualityBmaintenanceEnables searching and accessing EU open datasets from data.europa.eu, including metadata discovery and dataset retrieval.20 npmMIT
- AlicenseAqualityCmaintenanceEnables querying and analyzing over 90,000 public datasets from the Spanish Government Open Data Portal (datos.gob.es) using natural language, with tools for search, filtering, metadata access, and SPARQL queries.105MIT
- AlicenseNot gradedqualityAmaintenanceEnables natural language search and discovery of open-access scientific datasets through the EOSC Data Commons OpenSearch service. Provides tools to search datasets and retrieve file metadata using LLM-assisted queries.15MIT
- AlicenseAqualityBmaintenanceConnect your ads, shop, analytics, social, CRM and finance platforms once, then let Claude, ChatGPT, Cursor or any MCP client read, join and explain your numbers. Public statistics from the World Bank, IMF, Eurostat, OECD, WHO and SEC filings come as context, searchable and chartable from the same tools. Read-only by design, every number carries its source.57340 npm2MIT
TDQS
Scored across 5 tools
Each tool targets a clearly distinct action: search_resources finds resources, load_resource inspects one, fill_prompt renders prompt templates, download_dataset persists full datasets, and estimate_cost computes pricing. Boundaries are sharp — even the superficially similar load_resource vs download_dataset differ (preview/first rows vs full file export), so an agent can select confidently.
All five names follow a strict snake_case verb_noun pattern (search_resources, load_resource, fill_prompt, download_dataset, estimate_cost). The only variation is plural vs singular nouns, which reflects the actual cardinality semantics rather than an inconsistency.
Five tools is well-scoped for a resource-catalogue server covering discovery, inspection, prompt rendering, dataset export and cost estimation. Every tool earns its place with no redundancy.
The surface covers the core catalogue lifecycle: discover, inspect, use (fill prompts), export datasets and estimate cost. Minor gaps exist — no explicit browse/list-by-type or metadata filtering beyond free search, and no way to fetch a model or MCP server artifact directly — but agents can work around these via search.