io.github.SemanticDataCharter/sdchealthdcatap
PYPI · SDCHEALTHDCATAP
HealthDCAT-AP catalogs of published Semantic Data Charter models; Turtle or JSON-LD; no account.
Available components
Last scanned (5 hours ago)
Scores higher than 92% of PyPI servers
Category Health and Science
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 setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 11 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to SemanticDataCharter/sdc_healthdcat_ap). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 322 tokens (~322/item across 1 items; 1 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 Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 +16
- Malware scan: unverified → pass ▲ security
- Package version: 4.1.0 → 4.1.1 functional
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 4.1.0 → 4.1.1 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 5 Nov 2026 · Analysed pypi/sdchealthdcatap@4.1.1
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 | SemanticDataCharter/sdc_healthdcat_ap |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/SemanticDataCharter/sdc_healthdcat_ap/.github/workflows/release.yml@refs/tags/v4.1.1 |
| Rekor log index | 3466020234 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:8ce59e2b3ba8877c442a25c581293f12f0ccad0f1b4d98216964b7ef08a16c59 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 11 packages
| Packages resolved | 11 |
|---|---|
| Stale | 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 →
write_catalog ~237
Write a HealthDCAT-AP (release 8) catalog describing one or more published Semantic Data Charter models as health datasets at the declared access level, as Turtle or JSON-LD, each with the model's schema cited by URL and SHA-256. The health layer (applicable legislation, health category, the HDAB, the distribution) comes from the package's declared input. Validated in this package's CI with the HealthData@EU validator's own shape set from a pinned snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_email | string | – | The publisher's contact e-mail; the package's declared default applies when omitted. |
| contact_name | string | – | The publisher's contact point name; the package's declared default applies when omitted. |
| ct_ids | array | – | Model identifiers (CUID2) in the public catalog, fetched from the host this server was started with. |
| date | string | – | The catalog date, YYYY-MM-DD; today when omitted. |
| directories | array | – | Package directories on disk. Give ct_ids or directories or both; at least one model. |
| format | string | – | Serialization of the catalog. |
No output schema declared.
No examples provided.
How do I install the io.github.SemanticDataCharter/sdchealthdcatap MCP server?
io.github.SemanticDataCharter/sdchealthdcatap runs locally as a PyPI package, launched with uvx sdchealthdcatap. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · sdchealthdcatap
claude mcp add semanticdatacharter-sdchealthdcatap -- uvx sdchealthdcatap
What is the io.github.SemanticDataCharter/sdchealthdcatap MCP server?
io.github.SemanticDataCharter/sdchealthdcatap is an MCP server listed in the public MCP registry as io.github.SemanticDataCharter/sdchealthdcatap. HealthDCAT-AP catalogs of published Semantic Data Charter models; Turtle or JSON-LD; no account. This page covers its PyPI package (sdchealthdcatap).
Is the io.github.SemanticDataCharter/sdchealthdcatap MCP server safe to use?
io.github.SemanticDataCharter/sdchealthdcatap scores 89 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.SemanticDataCharter/sdchealthdcatap MCP server expose?
io.github.SemanticDataCharter/sdchealthdcatap exposes 1 tool: write_catalog. Their descriptions and schemas cost roughly 237 tokens of context every time the server is loaded.
Is the io.github.SemanticDataCharter/sdchealthdcatap MCP server still maintained?
io.github.SemanticDataCharter/sdchealthdcatap 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.SemanticDataCharter/sdchealthdcatap MCP server under?
io.github.SemanticDataCharter/sdchealthdcatap declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.