CE-RISE Digital Passport Engineering Assistant
OCI · GHCR.IO/CE-RISE-SOFTWARE/DP-ENGINEERING-ASSISTANT-MCP:0.0.1 · SCANNED SEP 20
Helps plan and reuse CE-RISE Digital Passport components, models, and deployment assets.
Available components
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
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.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 135 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2592 tokens (~72/item across 36 items; 29 tools + 7 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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 29 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 31 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.
How do I install the CE-RISE Digital Passport Engineering Assistant MCP server?
CE-RISE Digital Passport Engineering Assistant runs locally as a container image, launched with docker run --rm -i ghcr.io/ce-rise-software/dp-engineering-assistant-mcp:0.0.1. 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/dp-engineering-assistant-mcp:0.0.1
claude mcp add ce-rise-software-dp-engineering-assistant -- docker run --rm -i ghcr.io/ce-rise-software/dp-engineering-assistant-mcp:0.0.1
{
"mcpServers": {
"ce-rise-software-dp-engineering-assistant": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/ce-rise-software/dp-engineering-assistant-mcp:0.0.1"
]
}
}
} {
"servers": {
"ce-rise-software-dp-engineering-assistant": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/ce-rise-software/dp-engineering-assistant-mcp:0.0.1"
]
}
}
} codex mcp add ce-rise-software-dp-engineering-assistant -- docker run --rm -i ghcr.io/ce-rise-software/dp-engineering-assistant-mcp:0.0.1
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ce-rise-software-dp-engineering-assistant": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/ce-rise-software/dp-engineering-assistant-mcp:0.0.1"
],
"enabled": true
}
}
} mcp_servers:
ce-rise-software-dp-engineering-assistant:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/ce-rise-software/dp-engineering-assistant-mcp:0.0.1"] {
"McpServers": {
"ce-rise-software-dp-engineering-assistant": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/ce-rise-software/dp-engineering-assistant-mcp:0.0.1"
]
}
}
} {
"mcpServers": {
"ce-rise-software-dp-engineering-assistant": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/ce-rise-software/dp-engineering-assistant-mcp:0.0.1"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 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.
- 10 Sept 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 20 Sept 2026 · Analysed oci/ghcr.io/ce-rise-software/dp-engineering-assistant-mcp:0.0.1
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_adoption_context Assess Adoption Context ~84
Assess a general Digital Passport adoption context across scope, drivers, value-chain role, shared information, data readiness, and value goals.
| Name | Type | Req | Description |
|---|---|---|---|
| adoption_context | object | yes | Declared adoption context. Useful keys include organization_role, passport_scope, compliance_drivers, value_chain_actors, shared_information, data_sources, existing_systems, value_goals, and implemen… |
No output schema declared.
No examples provided.
assess_deployment_artifact_readiness Assess Deployment Artifact Readiness ~69
Assess whether enough deployment context is declared before generated artifacts are treated as implementation-ready.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_context | object | yes | Declared deployment context. Useful keys include target_runtime, selected_services, io_adapter_strategy, model_registry_strategy, auth_strategy, environment_overlays, and operational_checks. |
No output schema declared.
No examples provided.
assess_implementation_readiness Assess Implementation Readiness ~62
Assess whether a Digital Passport implementation context has enough information to proceed.
| Name | Type | Req | Description |
|---|---|---|---|
| project_context | object | yes | Declared implementation context. Useful keys include passport_scope, user_goal, data_sources, selected_components, data_model_strategy, deployment_context, and validation_strategy. |
No output schema declared.
No examples provided.
build_connected_solution_snapshot Build Connected Solution Snapshot ~68
Build a grounded snapshot connecting catalog components to curated CE-RISE source repositories and documentation.
| Name | Type | Req | Description |
|---|---|---|---|
| include_headings | boolean | – | When true, include Markdown headings for each available key file. |
| source_ids | array | – | Optional list of source ids. Omit to include all connected sources. |
No output schema declared.
No examples provided.
build_live_service_readiness_snapshot Build Live Service Readiness Snapshot ~71
Build a read-only reachability/readiness snapshot over curated CE-RISE live service connections.
| Name | Type | Req | Description |
|---|---|---|---|
| service_ids | array | – | Optional service ids from list_live_service_connections. Omit to check all services. |
| timeout_seconds | number | – | Optional HTTP timeout between 0 and 30 seconds. |
No output schema declared.
No examples provided.
build_update_aware_solution_context Build Update-Aware Solution Context ~118
Combine stable catalog guidance with optional current release/tag/artifact metadata from configured CE-RISE update channels.
| Name | Type | Req | Description |
|---|---|---|---|
| check_remote | boolean | – | When true, fetch current metadata from configured update channels. |
| component_ids | array | – | Optional CE-RISE component ids. When omitted, relevant components are selected from user_goal or all components are included. |
| timeout_seconds | number | – | Optional HTTP timeout between 0 and 30 seconds. |
| user_goal | string | – | Optional user goal used to select relevant components from the stable catalog. |
No output schema declared.
No examples provided.
check_connected_sources Check Connected Sources ~64
Check local and optionally remote availability for connected CE-RISE sources.
| Name | Type | Req | Description |
|---|---|---|---|
| check_remote | boolean | – | When true, perform network HEAD checks for repository and documentation URLs. |
| source_ids | array | – | Optional list of source ids to check. Omit to check all sources. |
No output schema declared.
No examples provided.
check_update_channels Check Update Channels ~86
Fetch current metadata from configured read-only CE-RISE update channels.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_ids | array | – | Optional update channel ids to check. Omit to select by component_ids or check all channels. |
| component_ids | array | – | Optional CE-RISE component ids whose update channels should be checked. |
| timeout_seconds | number | – | Optional HTTP timeout between 0 and 30 seconds. |
No output schema declared.
No examples provided.
discover_model_repositories Discover Model Repositories ~78
Discover CE-RISE model repositories under the configured model namespace and propose update channels for newly available models.
| Name | Type | Req | Description |
|---|---|---|---|
| check_remote | boolean | – | When true, fetch the current CE-RISE-models repository list from the configured discovery channel. Defaults to true. |
| timeout_seconds | number | – | Optional HTTP timeout between 0 and 30 seconds. |
No output schema declared.
No examples provided.
generalize_reference_example Generalize Reference Example ~105
Generalize reusable workflow patterns from a CE-RISE reference example for a declared Digital Passport adoption context.
| Name | Type | Req | Description |
|---|---|---|---|
| adoption_context | object | – | Declared adoption context. Useful keys include organization_role, passport_scope, value_chain_actors, shared_information, and value_goals. |
| example_id | string | yes | Reference example id from list_reference_examples. |
| target_outcome | string | – | Optional target outcome, such as local learning workflow, deployment handover, or integration planning. |
No output schema declared.
No examples provided.
generate_deployment_artifact_plan Generate Deployment Artifact Plan ~174
Map deployment choices to Compose/Kubernetes starter artifact profiles derived from the CE-RISE GitOps template.
| Name | Type | Req | Description |
|---|---|---|---|
| adoption_context | object | – | Optional adoption or implementation context to carry through the plan. |
| check_remote_updates | boolean | – | When true, check configured update channels and include current metadata in the generated plan context. |
| include_internal_adapter | boolean | – | When true, include the optional internal adapter Compose profile. |
| include_re_indicators | boolean | – | When true, include RE Indicators Calculation Service profiles/extensions. |
| selected_components | array | – | Optional CE-RISE component ids already selected. |
| target | string | – | Optional deployment target: compose, kubernetes, or both. Defaults to both. |
| timeout_seconds | number | – | Optional HTTP timeout between 0 and 30 seconds for update checks. |
No output schema declared.
No examples provided.
generate_deployment_artifacts Generate Deployment Artifacts ~230
Return Docker Compose and/or Kubernetes starter file contents derived from the existing CE-RISE GitOps template.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_mode | string | – | Optional HEX Core authentication mode placeholder, such as jwt_jwks or none. |
| check_remote_updates | boolean | – | When true, check configured update channels and use current metadata where it maps safely to generated artifact fields. |
| environment | string | – | Optional environment label: local, dev, or prod. |
| external_io_adapter_url | string | – | Optional external HTTP IO adapter URL placeholder. |
| include_internal_adapter | boolean | – | When true, include the optional internal adapter Compose profile. |
| include_re_indicators | boolean | – | When true, include RE Indicators Calculation Service profiles/extensions. |
| project_name | string | – | Optional project name used for generated Kubernetes namespaces and artifact ids. |
| selected_components | array | – | Optional CE-RISE component ids already selected. |
| target | string | yes | Required deployment target: compose, kubernetes, or both. |
| timeout_seconds | number | – | Optional HTTP timeout between 0 and 30 seconds for update checks. |
No output schema declared.
No examples provided.
generate_implementation_plan Generate Implementation Plan ~68
Generate an ordered implementation plan that reuses existing CE-RISE assets.
| Name | Type | Req | Description |
|---|---|---|---|
| architecture_id | string | – | Optional architecture pattern id from recommend_passport_architecture. |
| goal | string | yes | Implementation goal. |
| known_components | array | – | Optional known CE-RISE component ids already selected. |
No output schema declared.
No examples provided.
generate_implementation_roadmap Generate Implementation Roadmap ~72
Generate a phased roadmap for Digital Passport adoption and implementation over existing CE-RISE assets.
| Name | Type | Req | Description |
|---|---|---|---|
| adoption_context | object | yes | Declared adoption context. |
| adoption_path_id | string | – | Optional adoption path id from recommend_adoption_path. |
| time_horizon | string | – | Optional planning horizon label. |
No output schema declared.
No examples provided.
identify_value_opportunities Identify Value Opportunities ~80
Identify practical value opportunities from shared Digital Passport information.
| Name | Type | Req | Description |
|---|---|---|---|
| adoption_context | object | – | Optional adoption context object. |
| selected_flow_ids | array | – | Optional flow ids from map_value_chain_flows. |
| shared_information | array | – | Optional declared shared information types or examples. |
| value_goals | array | – | Optional target value goals beyond compliance. |
No output schema declared.
No examples provided.
inspect_connected_source Inspect Connected Source ~61
Inspect curated key files from one connected CE-RISE source, including Markdown headings when available.
| Name | Type | Req | Description |
|---|---|---|---|
| include_headings | boolean | – | When true, include Markdown headings discovered in key files. |
| source_id | string | yes | Connected source id from list_connected_sources. |
No output schema declared.
No examples provided.
inspect_live_service_openapi Inspect Live Service OpenAPI ~77
Fetch and summarize the OpenAPI document from one live CE-RISE service connection.
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | – | Optional localhost-only base URL override for local testing. |
| service_id | string | yes | Service id from list_live_service_connections. |
| timeout_seconds | number | – | Optional HTTP timeout between 0 and 30 seconds. |
No output schema declared.
No examples provided.
list_connected_sources List Connected CE-RISE Sources ~59
List curated CE-RISE repositories, documentation sites, models, and service references connected to this assistant.
| Name | Type | Req | Description |
|---|---|---|---|
| include_status | boolean | – | When true, include local repository availability and key-file status. |
| kind | string | – | Optional source kind filter. |
No output schema declared.
No examples provided.
list_deployment_artifact_templates List Deployment Artifact Templates ~48
List CE-RISE GitOps-template-derived deployment artifact profiles for Compose and Kubernetes outputs.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | – | Optional target filter: compose, kubernetes, or both. |
No output schema declared.
No examples provided.
list_live_service_connections List Live Service Connections ~45
List curated read-only live service discovery connections for CE-RISE services.
| Name | Type | Req | Description |
|---|---|---|---|
| service_family | string | – | Optional service family filter, such as core, storage, or calculation. |
No output schema declared.
No examples provided.
list_reference_examples List Reference Examples ~56
List curated CE-RISE reference examples that can be generalized without copying their concrete demo data or local-only settings.
| Name | Type | Req | Description |
|---|---|---|---|
| source_component_id | string | – | Optional CE-RISE component id filter, such as dp_system_local_demonstrator. |
No output schema declared.
No examples provided.
list_solution_capabilities List CE-RISE Solution Capabilities ~51
List deterministic assistant-facing CE-RISE capability families from the local catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| family | string | – | Optional capability family filter, such as discovery, design, data-model, implementation, validation, or deployment. |
No output schema declared.
No examples provided.
list_solution_components List CE-RISE Solution Components ~50
List known existing CE-RISE components and their intended assistant reuse role.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | – | Optional capability id used to return related components. |
| kind | string | – | Optional component kind filter. |
No output schema declared.
No examples provided.
list_update_channels List Update Channels ~96
List configured read-only CE-RISE repository, release, tag, documentation, and artifact update channels.
| Name | Type | Req | Description |
|---|---|---|---|
| component_id | string | – | Optional CE-RISE component id filter. |
| source_id | string | – | Optional connected source id filter. |
| update_role | string | – | Optional update role filter, such as software_component_version, model_artifact_version, deployment_template_version, reference_example_version, tooling_version, or documentation_availability. |
No output schema declared.
No examples provided.
map_user_goal_to_ce_rise_capabilities Map User Goal To CE-RISE Capabilities ~60
Map a user goal to existing CE-RISE capabilities and suggested components using the deterministic local catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | – | Optional project constraints or keywords. |
| user_goal | string | yes | User's Digital Passport engineering goal. |
No output schema declared.
No examples provided.
map_value_chain_flows Map Value-Chain Flows ~109
Map requested, held, validated, enriched, or shared Digital Passport information across value-chain actors.
| Name | Type | Req | Description |
|---|---|---|---|
| adoption_context | object | – | Optional adoption context object. |
| information_needs | array | – | Optional list of information needs or shared information types. |
| organization_role | string | – | Optional organization role in the value chain. |
| product_scope | string | – | Optional product, material, asset, or process scope. |
| value_chain_actors | array | – | Optional list of value-chain actors. |
No output schema declared.
No examples provided.
probe_live_service Probe Live Service ~101
Probe curated read-only GET endpoints for one live CE-RISE service connection.
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | – | Optional localhost-only base URL override for local testing. |
| endpoint_ids | array | – | Optional list of safe endpoint ids to probe. Omit to probe all safe endpoints for the service. |
| service_id | string | yes | Service id from list_live_service_connections. |
| timeout_seconds | number | – | Optional HTTP timeout between 0 and 30 seconds. |
No output schema declared.
No examples provided.
recommend_adoption_path Recommend Adoption Path ~60
Recommend a CE-RISE reuse-oriented Digital Passport adoption path.
| Name | Type | Req | Description |
|---|---|---|---|
| adoption_context | object | yes | Declared adoption context. |
| priorities | array | – | Optional priorities such as compliance, local prototype, model alignment, value-chain exchange, or deployment preparation. |
No output schema declared.
No examples provided.
recommend_passport_architecture Recommend Passport Architecture ~60
Recommend a CE-RISE reuse-oriented Digital Passport architecture pattern.
| Name | Type | Req | Description |
|---|---|---|---|
| priorities | array | – | Optional priorities such as local validation, deployment, model alignment, or production preparation. |
| use_case | string | yes | Digital Passport use case or implementation scenario. |
No output schema declared.
No examples provided.
What is the CE-RISE Digital Passport Engineering Assistant MCP server?
CE-RISE Digital Passport Engineering Assistant is an MCP server listed in the public MCP registry as io.github.CE-RISE-software/dp-engineering-assistant. Helps plan and reuse CE-RISE Digital Passport components, models, and deployment assets. This page covers its container image (ghcr.io/ce-rise-software/dp-engineering-assistant-mcp:0.0.1).
Is the CE-RISE Digital Passport Engineering Assistant MCP server safe to use?
CE-RISE Digital Passport Engineering Assistant scores 53 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 CE-RISE Digital Passport Engineering Assistant MCP server expose?
CE-RISE Digital Passport Engineering Assistant exposes 29 tools: list_solution_capabilities, list_solution_components, map_user_goal_to_ce_rise_capabilities, recommend_passport_architecture, generate_implementation_plan, and 24 more. Their descriptions and schemas cost roughly 2,362 tokens of context every time the server is loaded.
Is the CE-RISE Digital Passport Engineering Assistant MCP server still maintained?
CE-RISE Digital Passport Engineering Assistant is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.