# io.github.SemanticDataCharter/sdc-mapper (pypi · sdc-mapper)

Map Governed Data Records to documented formats, reporting what happened to every value.

- Trust score: 85/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `sdc-mapper`: 85/100 (this document), [markdown](https://verifymcp.io/servers/semanticdatacharter-sdc-mapper/sdc-mapper.md), [page](https://verifymcp.io/servers/semanticdatacharter-sdc-mapper/sdc-mapper)

## Channel facts

- Registry: `pypi`
- Package: `sdc-mapper`
- Version: `4.3.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 1 of 17 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to SemanticDataCharter/sdc-mapper).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 8 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add semanticdatacharter-sdc-mapper -- uvx sdc-mapper
```

### Cursor

```json
{
  "mcpServers": {
    "semanticdatacharter-sdc-mapper": {
      "command": "uvx",
      "args": [
        "sdc-mapper"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "semanticdatacharter-sdc-mapper": {
      "command": "uvx",
      "args": [
        "sdc-mapper"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add semanticdatacharter-sdc-mapper -- uvx sdc-mapper
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "semanticdatacharter-sdc-mapper": {
      "type": "local",
      "command": [
        "uvx",
        "sdc-mapper"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add semanticdatacharter-sdc-mapper --command uvx --arg sdc-mapper
```

### Hermes

```yaml
mcp_servers:
  semanticdatacharter-sdc-mapper:
    command: "uvx"
    args: ["sdc-mapper"]
```

### Netclaw

```json
{
  "McpServers": {
    "semanticdatacharter-sdc-mapper": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "sdc-mapper"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add semanticdatacharter-sdc-mapper -t stdio -c uvx -a sdc-mapper
```

### Other

```json
{
  "mcpServers": {
    "semanticdatacharter-sdc-mapper": {
      "command": "uvx",
      "args": [
        "sdc-mapper"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 85, +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.

### 2026-11-03 (score 84, +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.

### 2026-11-01 (score 83, +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.

### 2026-10-30 (score 82, +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.

### 2026-10-29 (score 81, +1)

- [functional improvement] Security disclosure: fail → pass

### 2026-10-28 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-27 (score 65, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 4.3.1 → 4.3.2

### 2026-10-26 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

## MCP tools (6)

### `list_targets` (~44 tokens)

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).

### `map_record` (~277 tokens)

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.

Input parameters:

- `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, required): Path to the Governed Data Record's XML file on disk.
- `target` (string, required): A mapper name, as list_targets gives it.

### `check_mapping` (~144 tokens)

Validate a mapping file against the mapping schema, and, given a model, check it is bound to that model's current schema.

Input parameters:

- `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, required): Path to a mapping file (YAML) for this model and target, if the model alone does not settle the mapping.

### `fidelity` (~169 tokens)

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.

Input parameters:

- `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, required): Path to the Governed Data Record's XML file on disk.

### `log_summary` (~45 tokens)

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.

Input parameters:

- `days` (number)

### `verify_log` (~28 tokens)

Walk the log's hash chain from the first entry and report whether any entry was altered or removed.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/semanticdatacharter-sdc-mapper/sdc-mapper#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 81
- 2026-10-28: 80
- 2026-10-27: 65
- 2026-10-26: 79
- 2026-10-25: 64

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/sdc-mapper/
- Socket report: https://socket.dev/pypi/package/sdc-mapper
- Repository: https://github.com/SemanticDataCharter/sdc-mapper
- Changelog RSS feed: https://verifymcp.io/servers/semanticdatacharter-sdc-mapper/sdc-mapper.xml
- Changelog JSON feed: https://verifymcp.io/servers/semanticdatacharter-sdc-mapper/sdc-mapper.json
- HTML version of this page: https://verifymcp.io/servers/semanticdatacharter-sdc-mapper/sdc-mapper