swiss-cultural-heritage-mcp
Related Servers
Alternatives to swiss-cultural-heritage-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI models to search and retrieve bibliographic and digitized records from Swiss academic libraries (swisscovery, e-rara, e-periodica, e-manuscripta) via open protocols without requiring API keys.161MIT
- AlicenseAqualityAmaintenanceMCP server for Switzerland's national metadata catalogue, enabling AI agents to discover datasets, APIs, public services, and publishers through free-text search and structured queries.13MIT
- AlicenseAqualityAmaintenanceMCP server giving AI models direct access to 30M+ resources at ETH Library Zurich – books, maps, images, archival material, and linked-data person records.71MIT
- AlicenseAqualityFmaintenanceEnables querying Swiss data protection regulations, FDPIC/EDOB decisions, and guidelines directly from MCP-compatible clients like Claude.6Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables querying the Historisches Grundbuch Basel corpus, including full-text search, person lookups, and property dossier retrieval, through MCP-compatible clients like Claude.-
- AlicenseBqualityDmaintenanceMCP server exposing all major Swiss official public APIs as native tools for any MCP-compatible AI agent.342 npmMIT
TDQS
Scored across 11 tools
Most tools are clearly separated by source (SIKART, SNM, NB, Memobase/Dodis) and action (search vs. get), but `heritage_cross_search` and `search_heritage` both perform multi-source federated searches, which could cause an agent to pick the wrong one. The detailed descriptions clarify the different source sets, but the names alone are not sufficiently distinct.
Naming conventions are inconsistent: some tools use `heritage_<verb>_<object>` (e.g., `heritage_search_artists`, `heritage_get_publication`), while others use `<verb>_heritage_<object>` (e.g., `search_heritage`, `get_heritage_item`, `list_heritage_collections`). The position of 'heritage' varies, and `heritage_cross_search` is an odd compound that doesn't follow the verb_noun pattern. This makes the tool set harder to navigate predictably.
The 11 tools map cleanly to the three main institutions (SIKART, SNM, National Library) plus the federated facade for Memobase/Dodis. Each source has search and detail tools, plus discovery tools for collections. The count is well-scoped for the domain and there is no bloat.
The tool set covers search, retrieval, and collection discovery for each integrated source, with the ability to browse objects in SNM datasets. Missing are a unified cross-search across all five institutions (only grouped subsets exist) and any write operations, but those are not expected for a read-only heritage data API. Minor gaps, such as no SIKART collection listing, are workable.