io.github.malkreide/i14y-mcp
PYPI · I14Y-MCP · SCANNED SEP 20
MCP server for I14Y — Switzerland's national open-data metadata catalogue (DCAT-AP-CH)
Available components
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 native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 33 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 0 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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add malkreide-i14y-mcp -- uvx i14y-mcp
{
"mcpServers": {
"malkreide-i14y-mcp": {
"command": "uvx",
"args": [
"i14y-mcp"
]
}
}
} {
"servers": {
"malkreide-i14y-mcp": {
"command": "uvx",
"args": [
"i14y-mcp"
]
}
}
} codex mcp add malkreide-i14y-mcp -- uvx i14y-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"malkreide-i14y-mcp": {
"type": "local",
"command": [
"uvx",
"i14y-mcp"
],
"enabled": true
}
}
} openclaw mcp add malkreide-i14y-mcp --command uvx --arg i14y-mcp
mcp_servers:
malkreide-i14y-mcp:
command: "uvx"
args: ["i14y-mcp"] {
"McpServers": {
"malkreide-i14y-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"i14y-mcp"
]
}
}
} assistant mcp add malkreide-i14y-mcp -t stdio -c uvx -a i14y-mcp
{
"mcpServers": {
"malkreide-i14y-mcp": {
"command": "uvx",
"args": [
"i14y-mcp"
]
}
}
} 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.
- 20 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 19 Sept 26 +15
- Stability: 0.80 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Schema quality: 122 → 138 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.3.2 → 0.4.0 functional
- 18 Sept 26 −18
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed pypi/i14y-mcp@0.4.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
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 33 packages
| Packages resolved | 33 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
api_status Check the I14Y 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.
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | yes | – |
| checked_endpoints | object | yes | – |
| last_successful_call | – | – | – |
| note | string | yes | – |
| provenance | string | – | Where this payload came from. |
| reachable | boolean | yes | – |
| retrieved_at | string | yes | UTC timestamp of retrieval. |
| source | string | – | Attribution string. |
No examples provided.
get_concept Get one 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.
| Name | Type | Req | Description |
|---|---|---|---|
| concept_id | string | yes | – |
| language | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| concept | – | yes | – |
| provenance | string | – | Where this payload came from. |
| retrieved_at | string | yes | UTC timestamp of retrieval. |
| source | string | – | Attribution string. |
No examples provided.
get_data_service Get one 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.
| Name | Type | Req | Description |
|---|---|---|---|
| data_service_id | string | yes | – |
| language | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data_service | – | yes | – |
| provenance | string | – | Where this payload came from. |
| retrieved_at | string | yes | UTC timestamp of retrieval. |
| source | string | – | Attribution string. |
No examples provided.
get_dataset Get one 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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | – |
| language | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | – | yes | – |
| provenance | string | – | Where this payload came from. |
| retrieved_at | string | yes | UTC timestamp of retrieval. |
| source | string | – | Attribution string. |
No examples provided.
get_dataset_distributions Get a dataset's 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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | – |
| language | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | – |
| dataset_title | – | – | – |
| distributions | array | yes | – |
| provenance | string | – | Where this payload came from. |
| retrieved_at | string | yes | UTC timestamp of retrieval. |
| returned | integer | yes | – |
| source | string | – | Attribution string. |
No examples provided.
list_catalogs List catalogues ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| page | integer | – | – |
| page_size | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| catalogs | array | yes | – |
| page | integer | yes | – |
| page_size | integer | yes | – |
| provenance | string | – | Where this payload came from. |
| retrieved_at | string | yes | UTC timestamp of retrieval. |
| returned | integer | yes | – |
| source | string | – | Attribution string. |
No examples provided.
list_concepts List harmonised 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).
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| page | integer | – | – |
| page_size | integer | – | – |
| publisher_identifier | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| concepts | array | yes | – |
| page | integer | yes | – |
| page_size | integer | yes | – |
| provenance | string | – | Where this payload came from. |
| retrieved_at | string | yes | UTC timestamp of retrieval. |
| returned | integer | yes | – |
| source | string | – | Attribution string. |
No examples provided.
list_data_services List data services (APIs) ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| page | integer | – | – |
| page_size | integer | – | – |
| publisher_identifier | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data_services | array | yes | – |
| page | integer | yes | – |
| page_size | integer | yes | – |
| provenance | string | – | Where this payload came from. |
| retrieved_at | string | yes | UTC timestamp of retrieval. |
| returned | integer | yes | – |
| source | string | – | Attribution string. |
No examples provided.
list_datasets 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).
| Name | Type | Req | Description |
|---|---|---|---|
| access_rights | – | – | – |
| language | string | – | – |
| page | integer | – | – |
| page_size | integer | – | – |
| publisher_identifier | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| datasets | array | yes | – |
| page | integer | yes | – |
| page_size | integer | yes | – |
| provenance | string | – | Where this payload came from. |
| retrieved_at | string | yes | UTC timestamp of retrieval. |
| returned | integer | yes | – |
| source | string | – | Attribution string. |
No examples provided.
list_public_services 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).
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| page | integer | – | – |
| page_size | integer | – | – |
| publisher_identifier | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | yes | – |
| page_size | integer | yes | – |
| provenance | string | – | Where this payload came from. |
| public_services | array | yes | – |
| retrieved_at | string | yes | UTC timestamp of retrieval. |
| returned | integer | yes | – |
| source | string | – | Attribution string. |
No examples provided.
list_publishers 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).
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | – | – | – |
| language | string | – | – |
| page | integer | – | – |
| page_size | integer | – | – |
| uid | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | yes | – |
| page_size | integer | yes | – |
| provenance | string | – | Where this payload came from. |
| publishers | array | yes | – |
| retrieved_at | string | yes | UTC timestamp of retrieval. |
| returned | integer | yes | – |
| source | string | – | Attribution string. |
No examples provided.
search_catalog Search the I14Y catalogue ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| limit | integer | – | – |
| publishers | – | – | – |
| query | string | yes | – |
| themes | – | – | – |
| types | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| hint | – | – | Actionable next step when match_type is 'none' (e.g. which tool to try). |
| hits | array | yes | – |
| language | string | yes | – |
| match_type | string | – | 'none' when nothing matched, so the agent never sees a bare empty result. |
| provenance | string | – | Where this payload came from. |
| query | – | – | – |
| retrieved_at | string | yes | UTC timestamp of retrieval. |
| returned | integer | yes | Records in this payload after capping. |
| source | string | – | Attribution string. |
| total_matched | integer | yes | Matches reported by the upstream index. |
| truncated | boolean | yes | True when the upstream result set exceeded the cap. |
No examples provided.
search_codelist_entries Search a concept's code list ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| concept_id | string | yes | – |
| language | string | – | – |
| page | integer | – | – |
| page_size | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| concept_id | string | yes | – |
| entries | array | yes | – |
| language | string | yes | – |
| page | integer | yes | – |
| page_size | integer | yes | – |
| provenance | string | – | Where this payload came from. |
| retrieved_at | string | yes | UTC timestamp of retrieval. |
| returned | integer | yes | – |
| source | string | – | Attribution string. |
No examples provided.
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 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.