io.github.SemanticDataCharter/sdcreader
PYPI · SDCREADER
Read published Semantic Data Charter models: catalog search, record structure, codes, pinned schema.
Available components
Last scanned (23 minutes ago)
Scores higher than 90% of PyPI servers
Category Code Search and Documentation
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
- 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to SemanticDataCharter/sdcreader). 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 Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 964 tokens (~160/item across 6 items; 6 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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 68% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 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 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.
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 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.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 25 Oct 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.30 → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 4.3.1 → 4.4.1 functional
- Package version: 4.3.1 → 4.4.0 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/sdcreader@4.4.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/sdcreader |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/SemanticDataCharter/sdcreader/.github/workflows/release.yml@refs/tags/v4.4.1 |
| Rekor log index | 3465761003 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:be1847323058b34bd3f25e09b8c5b8465d96f813f617fdf1384b9b315adecc7d |
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 6 packages
| Packages resolved | 6 |
|---|---|
| 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 →
check_package ~110
Run the reader's integrity check on a package directory: the JSON-LD names the directory's model, it has components, the schema is an XML Schema, and its bytes are the published current version when versions.json is present. Returns the SHA-256 and the pinned schema URL.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | yes | A package directory already on disk (dm-<ct>.jsonld and dm-<ct>.xsd, optionally catalog.json and versions.json). Give this or ct_id, not both. |
No output schema declared.
No examples provided.
describe_model ~152
Describe one published model: title, description, project, the root record, how many leaves and components it has and of which types, its Dublin Core as the modeler wrote it (defaults reported as null), its semantic links, and the schema URL pinned to the SHA-256 of the bytes every record is validated against.
| Name | Type | Req | Description |
|---|---|---|---|
| ct_id | string | – | The model's identifier (CUID2) in the public catalog; the package is fetched from the host this server was started with. |
| directory | string | – | A package directory already on disk (dm-<ct>.jsonld and dm-<ct>.xsd, optionally catalog.json and versions.json). Give this or ct_id, not both. |
No output schema declared.
No examples provided.
find_models ~96
Search SDCStudio's public catalog of published models by text, or list the models of one public project by name. Needs no account. Returns identifiers, titles and projects; pass an identifier to describe_model.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | – |
| page_size | integer | – | – |
| project | string | – | A public project's exact name, for example NIH_CDE. |
| search | string | – | Text matched against title and description. |
No output schema declared.
No examples provided.
list_codes ~138
The enumerated values of one component in a model: each value with the IRI, definition and code system the published schema annotates it with.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | The component's identifier (ct_id), as list_leaves reports it. |
| ct_id | string | – | The model's identifier (CUID2) in the public catalog; the package is fetched from the host this server was started with. |
| directory | string | – | A package directory already on disk (dm-<ct>.jsonld and dm-<ct>.xsd, optionally catalog.json and versions.json). Give this or ct_id, not both. |
No output schema declared.
No examples provided.
list_leaves ~151
The model's leaves in document order, each with its path of clusters, its SDC4 type, its constraints, how many enumerated values it has and its identity links. Paged: a model can have more than a thousand leaves.
| Name | Type | Req | Description |
|---|---|---|---|
| ct_id | string | – | The model's identifier (CUID2) in the public catalog; the package is fetched from the host this server was started with. |
| directory | string | – | A package directory already on disk (dm-<ct>.jsonld and dm-<ct>.xsd, optionally catalog.json and versions.json). Give this or ct_id, not both. |
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
read_record ~215
Read a Governed Data Record (an XML file on disk) against its model: the record's attributes and each value in document order with its component, path of clusters, elements, context and any Exceptional Value (ISO 21090 code, name, and whether it was written at the source or inserted by recovery beside a rejected value). The model is the one the record names, fetched by its identifier unless ct_id or directory is given. Paged. Does not validate the record.
| Name | Type | Req | Description |
|---|---|---|---|
| ct_id | string | – | The model's identifier (CUID2) in the public catalog; the package is fetched from the host this server was started with. |
| directory | string | – | A package directory already on disk (dm-<ct>.jsonld and dm-<ct>.xsd, optionally catalog.json and versions.json). Give this or ct_id, not both. |
| limit | integer | – | – |
| offset | integer | – | – |
| record | string | yes | Path to the record's XML file on disk. |
No output schema declared.
No examples provided.
How do I install the io.github.SemanticDataCharter/sdcreader MCP server?
io.github.SemanticDataCharter/sdcreader runs locally as a PyPI package, launched with uvx sdcreader. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · sdcreader
claude mcp add semanticdatacharter-sdcreader -- uvx sdcreader
What is the io.github.SemanticDataCharter/sdcreader MCP server?
io.github.SemanticDataCharter/sdcreader is an MCP server listed in the public MCP registry as io.github.SemanticDataCharter/sdcreader. Read published Semantic Data Charter models: catalog search, record structure, codes, pinned schema. This page covers its PyPI package (sdcreader).
Is the io.github.SemanticDataCharter/sdcreader MCP server safe to use?
io.github.SemanticDataCharter/sdcreader scores 88 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/sdcreader MCP server expose?
io.github.SemanticDataCharter/sdcreader exposes 6 tools: find_models, describe_model, list_leaves, list_codes, read_record, check_package. Their descriptions and schemas cost roughly 862 tokens of context every time the server is loaded.
Is the io.github.SemanticDataCharter/sdcreader MCP server still maintained?
io.github.SemanticDataCharter/sdcreader 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/sdcreader MCP server under?
io.github.SemanticDataCharter/sdcreader 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.