io.github.SemanticDataCharter/sdc-mapper
PYPI · SDC-MAPPER
Map Governed Data Records to documented formats, reporting what happened to every value.
Available components
Last scanned (4 hours ago)
Scores higher than 88% of PyPI servers
Category Documents and Files
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 17 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 SemanticDataCharter/sdc-mapper). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 802 tokens (~133/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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- Security disclosure: fail → pass ▲ functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 4.3.1 → 4.3.2 functional
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
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/sdc-mapper@4.3.2
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-mapper |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/SemanticDataCharter/sdc-mapper/.github/workflows/release.yml@refs/tags/v4.3.2 |
| Rekor log index | 3523396077 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:5e25f9767d8025049d7e5df3e23611fe9a8d5597e86fab25484febd7f9348bb4 |
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 17 packages
| Packages resolved | 17 |
|---|---|
| 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 →
check_mapping ~144
Validate a mapping file against the mapping schema, and, given a model, check it is bound to that model's current schema.
| 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. |
| mapping | string | yes | Path to a mapping file (YAML) for this model and target, if the model alone does not settle the mapping. |
No output schema declared.
No examples provided.
fidelity ~169
Run every installed mapper on one record and compare what each target did with each Exceptional Value: one row per Exceptional Value, one column per target. Shows which formats can say why a value is missing or unusable, and which can only leave it empty.
| 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. |
| mappings | object | – | Mapping file paths by mapper name. |
| record | string | yes | Path to the Governed Data Record's XML file on disk. |
No output schema declared.
No examples provided.
list_targets ~44
The target mappers installed: each target format and version, its package, and how it writes each ISO 21090 Exceptional Value (preserved, degraded, carried or lost).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
log_summary ~45
Read the log back over a window: calls, outcomes, value classes and Exceptional Value classes per target, and the models and mapping files in use.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | – |
No output schema declared.
No examples provided.
map_record ~277
Map one Governed Data Record to one target format. The record is validated first: valid, valid with Exceptional Values (one bad value is marked, not fatal), or refused with the reasons. Returns the output (inline, or written to output_dir), the coverage report (how every value reached the target, and what happened to every Exceptional Value), one sentence of what the target could not say, and the hash of the log entry. The model is the one the record names unless ct_id or directory is given.
| 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. |
| mapping | string | – | Path to a mapping file (YAML) for this model and target, if the model alone does not settle the mapping. |
| output_dir | string | – | Write the outputs and coverage.json here instead of returning them inline. |
| record | string | yes | Path to the Governed Data Record's XML file on disk. |
| target | string | yes | A mapper name, as list_targets gives it. |
No output schema declared.
No examples provided.
verify_log ~28
Walk the log's hash chain from the first entry and report whether any entry was altered or removed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.SemanticDataCharter/sdc-mapper MCP server?
io.github.SemanticDataCharter/sdc-mapper runs locally as a PyPI package, launched with uvx sdc-mapper. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · sdc-mapper
claude mcp add semanticdatacharter-sdc-mapper -- uvx sdc-mapper
What is the io.github.SemanticDataCharter/sdc-mapper MCP server?
io.github.SemanticDataCharter/sdc-mapper is an MCP server listed in the public MCP registry as io.github.SemanticDataCharter/sdc-mapper. Map Governed Data Records to documented formats, reporting what happened to every value. This page covers its PyPI package (sdc-mapper).
Is the io.github.SemanticDataCharter/sdc-mapper MCP server safe to use?
io.github.SemanticDataCharter/sdc-mapper scores 85 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/sdc-mapper MCP server expose?
io.github.SemanticDataCharter/sdc-mapper exposes 6 tools: list_targets, map_record, check_mapping, fidelity, log_summary, verify_log. Their descriptions and schemas cost roughly 707 tokens of context every time the server is loaded.
Is the io.github.SemanticDataCharter/sdc-mapper MCP server still maintained?
io.github.SemanticDataCharter/sdc-mapper 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/sdc-mapper MCP server under?
io.github.SemanticDataCharter/sdc-mapper 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.