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/i14y-mcp

PYPI · I14Y-MCP

MCP server for I14Y — Switzerland's national open-data metadata catalogue (DCAT-AP-CH)

Available components

+15 this week 93 Trust /100

Last scanned (1 day ago)

Scores higher than 96% of PyPI servers

Category Search and Retrieval

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 Security100
  • No malware found by supply-chain analysis.Pass
  • 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 32 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/i14y-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 45 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1805 tokens (~138/item across 13 items; 13 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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.

  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 2 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 1 Nov 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 31 Oct 26 +14
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: pass → unverified ▼ functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
  • 25 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 17 Oct 26 +2
    • Stability: 0.90 → pass security
  • 16 Oct 26 −2
    • Stability: pass → 0.90 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 4 Nov 2026 · Analysed pypi/i14y-mcp@0.4.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/i14y-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/malkreide/i14y-mcp/.github/workflows/publish.yml@refs/tags/v0.4.0
Rekor log index 2893015293
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:8f2aaa248c8a7658a849aedb07bdfd2512325e134ad4506444461b341da300c4

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 32 packages
Packages resolved 32
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~1,593 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 ~52

Check whether the I14Y API is reachable and which endpoints respond. Always returns an evaluable status rather than an empty result, so an agent can distinguish «no data matched» from «the source is down».

Input schema present but exposes no named parameters.

NameTypeReqDescription
base_urlstringyes–
checked_endpointsobjectyes–
last_successful_call–––
notestringyes–
provenancestring–Where this payload came from.
reachablebooleanyes–
retrieved_atstringyesUTC timestamp of retrieval.
sourcestring–Attribution string.

No examples provided.

get_concept ~58

Retrieve one concept definition, including its value type and version. Args: concept_id: UUID from `list_concepts`. language: Language for titles and descriptions.

NameTypeReqDescription
concept_idstringyes–
languagestring––
NameTypeReqDescription
concept–yes–
provenancestring–Where this payload came from.
retrieved_atstringyesUTC timestamp of retrieval.
sourcestring–Attribution string.

No examples provided.

get_data_service ~60

Retrieve the full record for one registered API, including endpoints. Args: data_service_id: UUID from `list_data_services`. language: Language for titles and descriptions.

NameTypeReqDescription
data_service_idstringyes–
languagestring––
NameTypeReqDescription
data_service–yes–
provenancestring–Where this payload came from.
retrieved_atstringyesUTC timestamp of retrieval.
sourcestring–Attribution string.

No examples provided.

get_dataset ~130

Retrieve the full, aggregated metadata record for one dataset. This is the aggregated detail tool: a single call returns the contact point, temporal and spatial coverage, documentation links *and* every distribution with its licence — so `search_catalog` → `get_dataset` answers «who publishes it, through which interface, under which licence» in two calls, without a separate distributions or contact lookup. Args: dataset_id: UUID from `search_catalog` or `list_datasets`. language: Language for titles and descriptions.

NameTypeReqDescription
dataset_idstringyes–
languagestring––
NameTypeReqDescription
dataset–yes–
provenancestring–Where this payload came from.
retrieved_atstringyesUTC timestamp of retrieval.
sourcestring–Attribution string.

No examples provided.

get_dataset_distributions ~135

Get the downloadable files and access URLs for a dataset. This is the «where do I actually get the data» tool. Each distribution carries its own format, licence and download URL — licences differ between distributions of the same dataset, so always read the `licence` field before reusing the data. (`get_dataset` returns these same distributions alongside the rest of the record.) Args: dataset_id: UUID from `search_catalog` or `list_datasets`. language: Language for titles and descriptions.

NameTypeReqDescription
dataset_idstringyes–
languagestring––
NameTypeReqDescription
dataset_idstringyes–
dataset_title–––
distributionsarrayyes–
provenancestring–Where this payload came from.
retrieved_atstringyesUTC timestamp of retrieval.
returnedintegeryes–
sourcestring–Attribution string.

No examples provided.

list_catalogs ~82

List the catalogues that feed into I14Y. Each catalogue represents one contributing organisation's data collection. Args: language: Language for titles. page: 1-based page number. page_size: Records per page (1-100).

NameTypeReqDescription
languagestring––
pageinteger––
page_sizeinteger––
NameTypeReqDescription
catalogsarrayyes–
pageintegeryes–
page_sizeintegeryes–
provenancestring–Where this payload came from.
retrieved_atstringyesUTC timestamp of retrieval.
returnedintegeryes–
sourcestring–Attribution string.

No examples provided.

list_concepts ~127

List harmonised concepts and code lists of the Swiss administration. Concepts are the semantic backbone of interoperability: shared definitions and code lists that different bodies agree to use. Note that these are not reachable through `search_catalog`. Args: publisher_identifier: Publisher identifier from `list_publishers`. language: Language for titles and descriptions. page: 1-based page number. page_size: Records per page (1-100).

NameTypeReqDescription
languagestring––
pageinteger––
page_sizeinteger––
publisher_identifier–––
NameTypeReqDescription
conceptsarrayyes–
pageintegeryes–
page_sizeintegeryes–
provenancestring–Where this payload came from.
retrieved_atstringyesUTC timestamp of retrieval.
returnedintegeryes–
sourcestring–Attribution string.

No examples provided.

list_data_services ~140

List machine interfaces (APIs) registered by Swiss public bodies. The strategic payload of this server: the national register of official APIs, with endpoint URLs and OpenAPI specification links where the publisher supplied them. Use this to discover whether an interface already exists before building a scraper. Args: publisher_identifier: Publisher identifier from `list_publishers`. language: Language for titles and descriptions. page: 1-based page number. page_size: Records per page (1-100).

NameTypeReqDescription
languagestring––
pageinteger––
page_sizeinteger––
publisher_identifier–––
NameTypeReqDescription
data_servicesarrayyes–
pageintegeryes–
page_sizeintegeryes–
provenancestring–Where this payload came from.
retrieved_atstringyesUTC timestamp of retrieval.
returnedintegeryes–
sourcestring–Attribution string.

No examples provided.

list_datasets ~156

List registered datasets, optionally filtered by publisher. Unlike `search_catalog`, this endpoint paginates correctly and covers the complete register (roughly 2000 datasets as of July 2026), including records the search index misses. Args: publisher_identifier: Publisher identifier from `list_publishers`. access_rights: e.g. "PUBLIC", "NON_PUBLIC", "RESTRICTED". language: Language for titles and descriptions. page: 1-based page number. page_size: Records per page (1-100).

NameTypeReqDescription
access_rights–––
languagestring––
pageinteger––
page_sizeinteger––
publisher_identifier–––
NameTypeReqDescription
datasetsarrayyes–
pageintegeryes–
page_sizeintegeryes–
provenancestring–Where this payload came from.
retrieved_atstringyesUTC timestamp of retrieval.
returnedintegeryes–
sourcestring–Attribution string.

No examples provided.

list_public_services ~92

List registered public services (administrative offerings for citizens). Args: publisher_identifier: Publisher identifier from `list_publishers`. language: Language for titles and descriptions. page: 1-based page number. page_size: Records per page (1-100).

NameTypeReqDescription
languagestring––
pageinteger––
page_sizeinteger––
publisher_identifier–––
NameTypeReqDescription
pageintegeryes–
page_sizeintegeryes–
provenancestring–Where this payload came from.
public_servicesarrayyes–
retrieved_atstringyesUTC timestamp of retrieval.
returnedintegeryes–
sourcestring–Attribution string.

No examples provided.

list_publishers ~145

List the public bodies that publish into I14Y. Returns publisher identifiers needed by the other tools, plus the Swiss UID where available — the UID is the join key to `register-mcp` (Zefix). Args: identifier: Filter by exact publisher identifier. uid: Filter by Swiss UID, e.g. "CHE-123.456.789". language: Language for names. page: 1-based page number. page_size: Records per page (1-100).

NameTypeReqDescription
identifier–––
languagestring––
pageinteger––
page_sizeinteger––
uid–––
NameTypeReqDescription
pageintegeryes–
page_sizeintegeryes–
provenancestring–Where this payload came from.
publishersarrayyes–
retrieved_atstringyesUTC timestamp of retrieval.
returnedintegeryes–
sourcestring–Attribution string.

No examples provided.

search_catalog ~274

Search Switzerland's national metadata catalogue for data resources. The primary entry point: use this to find out *who* publishes data on a topic before looking for a specific dataset. Returns titles, publishers, themes and portal permalinks. Known limitation (verified live 2026-07-21): the upstream search index covers Datasets only. Filtering by `types=["Concept"]` or `types=["DataService"]` returns zero results even though those entities exist — use `list_concepts` and `list_data_services` for those. Args: query: Free-text search term, e.g. "Sonderpaedagogik" or "Bildung". An empty string returns the full index (over 1000 records) and is not recommended. language: Language for titles and descriptions. types: Restrict to resource types. Effectively only "Dataset" works. themes: Filter by theme identifiers. publishers: Filter by publisher identifiers. limit: Maximum records to return (1-200). Upstream ignores paging, so capping happens in this server.

NameTypeReqDescription
languagestring––
limitinteger––
publishers–––
querystringyes–
themes–––
types–––
NameTypeReqDescription
hint––Actionable next step when match_type is 'none' (e.g. which tool to try).
hitsarrayyes–
languagestringyes–
match_typestring–'none' when nothing matched, so the agent never sees a bare empty result.
provenancestring–Where this payload came from.
query–––
retrieved_atstringyesUTC timestamp of retrieval.
returnedintegeryesRecords in this payload after capping.
sourcestring–Attribution string.
total_matchedintegeryesMatches reported by the upstream index.
truncatedbooleanyesTrue when the upstream result set exceeded the cap.

No examples provided.

search_codelist_entries ~142

List the individual codes of a code-list concept. Use this to resolve official code values — for example the canonical list of a classification used across several federal datasets. Only concepts with `concept_type == "CodeList"` return entries. Args: concept_id: UUID of a code-list concept from `list_concepts`. language: Language for entry names. Required by the upstream API. page: 1-based page number. page_size: Records per page (1-200).

NameTypeReqDescription
concept_idstringyes–
languagestring––
pageinteger––
page_sizeinteger––
NameTypeReqDescription
concept_idstringyes–
entriesarrayyes–
languagestringyes–
pageintegeryes–
page_sizeintegeryes–
provenancestring–Where this payload came from.
retrieved_atstringyesUTC timestamp of retrieval.
returnedintegeryes–
sourcestring–Attribution string.

No examples provided.

Install

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

io.github.malkreide/i14y-mcp runs locally as a PyPI package, launched with uvx i14y-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 · i14y-mcp

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

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

io.github.malkreide/i14y-mcp is listed in the public MCP registry as io.github.malkreide/i14y-mcp. MCP server for I14Y, Switzerland's national open-data metadata catalogue (DCAT-AP-CH). This page covers its PyPI package (i14y-mcp).

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

io.github.malkreide/i14y-mcp scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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/i14y-mcp server expose?

io.github.malkreide/i14y-mcp exposes 13 tools: search_catalog, list_datasets, get_dataset, get_dataset_distributions, list_data_services, and 8 more. Their descriptions and schemas cost roughly 1,593 tokens of context every time the server is loaded.

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

io.github.malkreide/i14y-mcp is still listed as active in the MCP registry. We last reached this channel on 4 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/i14y-mcp server under?

io.github.malkreide/i14y-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.