Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.malkreide/termdat-mcp

PYPI · TERMDAT-MCP

MCP server for TERMDAT — the terminology database of the Swiss Federal Administration

Available components

−15 this week 76 Trust /100

Last scanned (3 hours ago)

Scores higher than 73% of PyPI servers

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to malkreide/termdat-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 46 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1030 tokens (~147/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 1 Nov 26 +14
    • Malware scan: unverified → pass ▲ security
    • Stability: pass → 0.97 functional
  • 31 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 29 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 26 Oct 26 +1
    • Stability: 0.97 → pass security
  • 25 Oct 26 −1
    • Stability: pass → 0.97 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed pypi/termdat-mcp@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo malkreide/termdat-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/malkreide/termdat-mcp/.github/workflows/publish.yml@refs/tags/v0.2.0
Rekor log index 2892721973
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:2f2c882bdebd84705032bb1bf3127cab7d539f40f0414687313898872e0f7db7

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 34 packages
Packages resolved 34
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~1,030 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
api_status ~21

Availability of the TERMDAT API. Never returns silently empty.

Input schema present but exposes no named parameters.

NameTypeReqDescription
classificationsinteger––
collectionsinteger––
messagestringyes–
provenancestringyes–
reachablebooleanyes–
retrieved_atstringyesISO-8601 UTC timestamp
sourcestring––

No examples provided.

check_terms ~96

Check a list of terms against validated TERMDAT designations. Intended for communication QA: verify that authority names, department titles and abbreviations in a draft match the officially validated form. Each term is reported as `validated`, `found_unvalidated` or `not_found`. Up to 25 terms per call; the lookups run concurrently.

NameTypeReqDescription
languagestring––
termsarrayyes–
NameTypeReqDescription
caveatstring––
checkedintegeryes–
languagestringyes–
not_foundintegeryes–
provenancestringyes–
resultsarrayyes–
retrieved_atstringyesISO-8601 UTC timestamp
sourcestring––
validatedintegeryes–

No examples provided.

get_entries ~86

Fetch known TERMDAT entries by their numeric IDs, with full language variants. Use this to re-retrieve an entry you already found via `search_terms` (its `entry_id`), e.g. to pull all four national-language designations at once.

NameTypeReqDescription
entry_idsarrayyes–
in_languagestring––
out_languagestring––
NameTypeReqDescription
entriesarrayyes–
hint––Set when the search returned nothing; suggests how to widen it
in_languagestringyes–
out_language–––
provenancestringyes–
retrieved_atstringyesISO-8601 UTC timestamp
returnedintegeryes–
search_termstringyes–
sourcestring––
truncatedbooleanyesTrue if the result hit max_results — narrow the query or raise the limit

No examples provided.

list_classifications ~36

List the 23 subject classifications (e.g. BILD = education), for `classification_ids`.

NameTypeReqDescription
languagestring––
NameTypeReqDescription
countintegeryes–
kindstringyes–
languagestringyes–
provenancestringyes–
retrieved_atstringyesISO-8601 UTC timestamp
sourcestring––
valuesarrayyes–

No examples provided.

list_collections ~34

List the ~140 TERMDAT collections, for use as `collection_ids` filters.

NameTypeReqDescription
languagestring––
NameTypeReqDescription
countintegeryes–
kindstringyes–
languagestringyes–
provenancestringyes–
retrieved_atstringyesISO-8601 UTC timestamp
sourcestring––
valuesarrayyes–

No examples provided.

search_terms ~623

Search TERMDAT for official designations of the Swiss Federal Administration. Use this to look up the officially validated German/French/Italian/English name of an authority, department or legal act — for example to check how a body is named in another national language before citing it. `search_term` is **Lucene query syntax**: `*` and `?` wildcards and the `~` fuzzy operator work. Matching is on whole words, so a compound is not found by its parts — «Quellensteuer» does not match «Quellensteuerverordnung», but «Quellensteuer*» does. Reach for a wildcard before concluding a term is absent. **Leave `detail` at True unless you want a bare hit list.** With `detail=False` the API omits `languageDetails`, and every entry comes back with an empty `variants` — id, url, status and classification, but not a single designation. That is a hit you cannot read a term from, from a tool whose purpose is terms. Use it to count or to filter by classification, never to answer «what is this called». `out_language` adds a target language to every entry's variants — it is purely additive and never filters the result set. `fields` is a comma-separated subset of: Terminus, Name, Abbreviation, Phraseology, Definition, Note, Context, Source, Metadata, Country, Comment; empty means Terminus, Name, Abbreviation, Phraseology, Definition, Note, Source. By default the search spans all 23 subject classifications; pass `classification_ids` or `collection_ids` to narrow it (see `list_classifications` / `list_collections`). Scope caveat: TERMDAT holds administrative nomenclature (authority names, titles of legal acts, abbreviations), not domain vocabulary — so a term may genuinely be absent. Establish that with a wildcard retry, not from a single empty result, and never fill the gap with a guessed designation. Coverage caveat: the public API serves a subset of what termdat.bk.admin.ch shows, and the Federal Chancellery confirmed on 2026-08-21 that this is deliberate — the selection follows t…

NameTypeReqDescription
classification_ids–––
collection_ids–––
detailboolean––
fieldsstring––
in_languagestring––
max_resultsinteger––
out_languagestring––
search_termstringyes–
NameTypeReqDescription
entriesarrayyes–
hint––Set when the search returned nothing; suggests how to widen it
in_languagestringyes–
out_language–––
provenancestringyes–
retrieved_atstringyesISO-8601 UTC timestamp
returnedintegeryes–
search_termstringyes–
sourcestring––
truncatedbooleanyesTrue if the result hit max_results — narrow the query or raise the limit

No examples provided.

translate_term ~134

Get the official equivalent of an administrative term in another national language. Returns the preferred designation (sequence 1) plus accepted variants, per matching entry. Use this for authority names, department titles and titles of legal acts. Matches only against designation fields, so a term merely *mentioned* in a definition is never reported as an equivalent. `term` accepts Lucene wildcards; on an empty result retry with `term*` before concluding there is no equivalent.

NameTypeReqDescription
from_languagestring––
max_resultsinteger––
termstringyes–
to_languagestring––
NameTypeReqDescription
from_languagestringyes–
hitsarrayyes–
provenancestringyes–
retrieved_atstringyesISO-8601 UTC timestamp
sourcestring––
termstringyes–
to_languagestringyes–
total_entriesintegeryes–

No examples provided.

Install

How do I install the io.github.malkreide/termdat-mcp server?

io.github.malkreide/termdat-mcp runs locally as a PyPI package, launched with uvx termdat-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · termdat-mcp

# add to Claude Code
claude mcp add malkreide-termdat-mcp -- uvx termdat-mcp
Common questions

What is the io.github.malkreide/termdat-mcp server?

io.github.malkreide/termdat-mcp is listed in the public MCP registry as io.github.malkreide/termdat-mcp. MCP server for TERMDAT, the terminology database of the Swiss Federal Administration. This page covers its PyPI package (termdat-mcp).

Is the io.github.malkreide/termdat-mcp server safe to use?

io.github.malkreide/termdat-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.malkreide/termdat-mcp server expose?

io.github.malkreide/termdat-mcp exposes 7 tools: search_terms, get_entries, translate_term, check_terms, list_collections, and 2 more. Their descriptions and schemas cost roughly 1,030 tokens of context every time the server is loaded.

Is the io.github.malkreide/termdat-mcp server still maintained?

io.github.malkreide/termdat-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.malkreide/termdat-mcp server under?

io.github.malkreide/termdat-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.