Digital Passport Assessment Workbench
OCI · GHCR.IO/CE-RISE-SOFTWARE/DPAWB-MCP:0.1.2
Deterministic SHACL-based assessment and comparison for digital passport data models.
Available components
Last scanned (4 hours ago)
Scores higher than 77% of OCI servers
Category Developer Tools
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
- 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: no license is declared. See how to fix → Fail
- Actively maintained (last published 191 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 460 tokens (~46/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 16 Oct 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.
- 15 Oct 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 5 Nov 2026 · Analysed oci/ghcr.io/ce-rise-software/dpawb-mcp:0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
assess Assess Profile ~33
Assess one composition profile and return one assessment_result document.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | yes | Local path to one composition profile YAML file. |
No output schema declared.
No examples provided.
capabilities Get Capabilities ~16
Return the deterministic command and artifact capability catalog.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
compare Compare Assessments ~74
Compare exactly two assessment_result documents and optionally apply an analyst-authored alignment file.
| Name | Type | Req | Description |
|---|---|---|---|
| alignment | string | – | Optional local path to one alignment YAML file. |
| left_assessment | string | yes | Local path to the left assessment_result JSON document. |
| right_assessment | string | yes | Local path to the right assessment_result JSON document. |
No output schema declared.
No examples provided.
coverage Assess Use-Case Coverage ~53
Assess one use case against one composition profile and return one coverage_result document.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | string | yes | Local path to one composition profile YAML file. |
| use_case | string | yes | Local path to one use-case YAML file. |
No output schema declared.
No examples provided.
prioritize Prioritize Improvement Targets ~68
Rank improvement targets from one assessment_result document plus optional downstream result documents.
| Name | Type | Req | Description |
|---|---|---|---|
| assessment | string | yes | Local path to one assessment_result JSON document. |
| comparison | string | – | Optional local path to one comparison_result JSON document. |
| coverage | array | – | Optional list of local coverage_result JSON document paths. |
No output schema declared.
No examples provided.
recommend_composition Recommend Composition ~87
Recommend a deterministic combined composition from two assessment results.
| Name | Type | Req | Description |
|---|---|---|---|
| comparison | string | – | Optional local path to one comparison_result JSON document. |
| coverage | array | – | Optional list of local coverage_result JSON document paths. |
| left_assessment | string | yes | Local path to the left assessment_result JSON document. |
| right_assessment | string | yes | Local path to the right assessment_result JSON document. |
No output schema declared.
No examples provided.
schema Get Schema ~20
Return one bundled JSON Schema.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
summarize Summarize Results ~38
Create one deterministic summary_result document from one or more existing result JSON documents.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | One or more local paths to result JSON documents. |
No output schema declared.
No examples provided.
template Get Template ~21
Return one bundled YAML template document.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
vocabulary Get Vocabulary ~21
Return one bundled controlled vocabulary document.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Digital Passport Assessment Workbench MCP server?
Digital Passport Assessment Workbench runs locally as a container image, launched with docker run --rm -i ghcr.io/ce-rise-software/dpawb-mcp:0.1.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/ce-rise-software/dpawb-mcp:0.1.2
claude mcp add ce-rise-software-dpawb -- docker run --rm -i ghcr.io/ce-rise-software/dpawb-mcp:0.1.2
What is the Digital Passport Assessment Workbench MCP server?
Digital Passport Assessment Workbench is an MCP server listed in the public MCP registry as io.github.CE-RISE-software/dpawb. Deterministic SHACL-based assessment and comparison for digital passport data models. This page covers its container image (ghcr.io/ce-rise-software/dpawb-mcp:0.1.2).
Is the Digital Passport Assessment Workbench MCP server safe to use?
Digital Passport Assessment Workbench scores 50 out of 100 on VerifyMCP. 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 Digital Passport Assessment Workbench MCP server expose?
Digital Passport Assessment Workbench exposes 10 tools: assess, coverage, compare, prioritize, recommend_composition, and 5 more. Their descriptions and schemas cost roughly 431 tokens of context every time the server is loaded.
Is the Digital Passport Assessment Workbench MCP server still maintained?
Digital Passport Assessment Workbench 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.