termdat-mcp
Related Servers
Alternatives to termdat-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP 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.1327 PyPIMIT
- AlicenseAqualityBmaintenanceMCP server for Swiss federal legislation metadata via Fedlex, enabling search and retrieval of act details with ELI URIs, SR numbers, and multilingual support.3Apache 2.0
- AlicenseBqualityDmaintenanceMCP server exposing all major Swiss official public APIs as native tools for any MCP-compatible AI agent.3412 npmMIT
- AlicenseAqualityBmaintenanceMCP server for querying Swiss intellectual property data (trademarks, patents, supplementary protection certificates) from the Swissreg register via natural language.1179 PyPIMIT
- AlicenseAqualityBmaintenanceMCP 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.1134 PyPIMIT
- AlicenseBqualityBmaintenanceAn MCP server that rolls 66 Swiss public data sources into 151 tools covering transport, weather, geodata, companies, sanctions, law, votes, tenders and statistics, with no API keys needed. Every answer is returned with licence, attribution and the exact upstream requests so results can be verified and cited.15195 npm2MIT
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes: searching, retrieving by ID, translating, batch QA, listing metadata, and status. search_terms and translate_term overlap somewhat since both query designations, but the descriptions make the intended use cases distinct enough for an agent to choose correctly.
Most tools follow a clear verb_noun pattern: search_terms, get_entries, translate_term, check_terms, list_collections, list_classifications. api_status is the one outlier, breaking the pattern by using noun_only style instead of something like get_status.
Seven tools is well-scoped for a read-only terminology lookup server. Each tool has a distinct role: search, retrieval, translation, QA checking, filter metadata, and API status, without redundant utilities.
The domain is Swiss administrative terminology lookup, and the tool surface covers the full lifecycle: discover entries, retrieve by ID, translate, validate batches, enumerate filters, and check API availability. There are no obvious dead ends or missing operations for a read-only API.