A
licenseB
qualityD
maintenanceMCP server exposing all major Swiss official public APIs as native tools for any MCP-compatible AI agent.
34
14 npm
MIT
i14y-mcp
by malkreide
Related Servers
Alternatives to i14y-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceAn MCP server providing AI-powered access to Open Data from the City of Zurich, enabling queries to 900+ datasets, real-time environmental and mobility data, geodata, parliamentary proceedings, and more.26166 PyPI8MIT
- AlicenseAqualityFmaintenanceMCP server that connects AI models to Swiss federal geodata, offering tools for spatial queries like layer discovery, coordinate identification, building zones, and terrain heights.9MIT
- AlicenseAqualityAmaintenanceMCP server connecting AI models to Swiss Federal Food Safety and Veterinary Office open data, enabling queries about food recalls, animal disease surveillance, food control results, and more.1126 PyPIMIT
- AlicenseAqualityDmaintenanceSwiss open data MCP server — transport, weather, geodata, companies, etc,. Zero API keys.76179 npm22MIT
- AlicenseAqualityAmaintenanceMCP server for TERMDAT, the terminology database of the Swiss Federal Administration, giving AI agents officially validated designations of Swiss authorities, departments, and legal acts across DE/FR/IT/EN with source references and validation status.7125 PyPI1MIT
TDQS
A4.3/5.0
Scored across 13 tools
Disambiguation5/5
Each tool targets a distinct resource or action: listing vs. fetching individual entities, plus search, status, and code-list lookup. Even the overlapping get_dataset and get_dataset_distributions are clearly differentiated by the description noting get_dataset returns distributions alongside the full record, making get_dataset_distributions a focused convenience tool. No two tools appear to do the same thing.
Naming Consistency5/5
Tool names follow a consistent verb_noun pattern: list_* for collections, get_* for single entities, search_* for search operations, and api_status for health. The pattern is uniform across all 13 tools with no mixed conventions or vague verbs.
Tool Count5/5
13 tools is well within the ideal 3-15 range for a domain-specific server. Each tool covers a distinct aspect of the I14Y metadata catalog (datasets, data services, public services, concepts, publishers, catalogs, status), and none feel redundant or superfluous.
Completeness4/5
The tool surface covers the core read-only workflows for a catalog: listing and retrieving datasets, data services, concepts, and code-list entries, plus search, publishers, catalogs, and status. Minor gaps exist—there is no get_public_service or get_catalog, so those entities can only be listed, not fetched individually. This is a minor gap that agents can work around, but it does not break the primary use cases.
Maintenance
ActivityActive
ResponsivenessNo issues