Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CE-RISE Digital Passport Engineering Assistant

OCI · GHCR.IO/CE-RISE-SOFTWARE/DP-ENGINEERING-ASSISTANT-MCP

Helps plan and reuse CE-RISE Digital Passport components, models, and deployment assets.

40 Trust /100

Last scanned (4 hours ago)

Scores higher than 42% of OCI servers

Category Developer Tools

Trust breakdown (7 categories)

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 0 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability86
  • 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 3023 tokens (~81/item across 37 items; 30 tools + 7 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 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
  • 99% 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 30 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 32 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.

Changelog

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 0
    • Security disclosure: fail → unverified ▼ functional
  • 4 Nov 26 40

    First indexed and scored.

Diagnostics

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/dp-engineering-assistant-mcp@0.0.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 →

MCP tools · 30 exposed · ~2,739 tokens

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 →

Tool Tokens
assess_adoption_context ~84

Assess a general Digital Passport adoption context across scope, drivers, value-chain role, shared information, data readiness, and value goals.

NameTypeReqDescription
adoption_contextobjectyesDeclared 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 ~69

Assess whether enough deployment context is declared before generated artifacts are treated as implementation-ready.

NameTypeReqDescription
deployment_contextobjectyesDeclared 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 ~62

Assess whether a Digital Passport implementation context has enough information to proceed.

NameTypeReqDescription
project_contextobjectyesDeclared 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 ~68

Build a grounded snapshot connecting catalog components to curated CE-RISE source repositories and documentation.

NameTypeReqDescription
include_headingsboolean–When true, include Markdown headings for each available key file.
source_idsarray–Optional list of source ids. Omit to include all connected sources.

No output schema declared.

No examples provided.

build_live_service_readiness_snapshot ~71

Build a read-only reachability/readiness snapshot over curated CE-RISE live service connections.

NameTypeReqDescription
service_idsarray–Optional service ids from list_live_service_connections. Omit to check all services.
timeout_secondsnumber–Optional HTTP timeout between 0 and 30 seconds.

No output schema declared.

No examples provided.

build_update_aware_solution_context ~118

Combine stable catalog guidance with optional current release/tag/artifact metadata from configured CE-RISE update channels.

NameTypeReqDescription
check_remoteboolean–When true, fetch current metadata from configured update channels.
component_idsarray–Optional CE-RISE component ids. When omitted, relevant components are selected from user_goal or all components are included.
timeout_secondsnumber–Optional HTTP timeout between 0 and 30 seconds.
user_goalstring–Optional user goal used to select relevant components from the stable catalog.

No output schema declared.

No examples provided.

check_connected_sources ~64

Check local and optionally remote availability for connected CE-RISE sources.

NameTypeReqDescription
check_remoteboolean–When true, perform network HEAD checks for repository and documentation URLs.
source_idsarray–Optional list of source ids to check. Omit to check all sources.

No output schema declared.

No examples provided.

check_update_channels ~86

Fetch current metadata from configured read-only CE-RISE update channels.

NameTypeReqDescription
channel_idsarray–Optional update channel ids to check. Omit to select by component_ids or check all channels.
component_idsarray–Optional CE-RISE component ids whose update channels should be checked.
timeout_secondsnumber–Optional HTTP timeout between 0 and 30 seconds.

No output schema declared.

No examples provided.

discover_model_repositories ~78

Discover CE-RISE model repositories under the configured model namespace and propose update channels for newly available models.

NameTypeReqDescription
check_remoteboolean–When true, fetch the current CE-RISE-models repository list from the configured discovery channel. Defaults to true.
timeout_secondsnumber–Optional HTTP timeout between 0 and 30 seconds.

No output schema declared.

No examples provided.

generalize_reference_example ~105

Generalize reusable workflow patterns from a CE-RISE reference example for a declared Digital Passport adoption context.

NameTypeReqDescription
adoption_contextobject–Declared adoption context. Useful keys include organization_role, passport_scope, value_chain_actors, shared_information, and value_goals.
example_idstringyesReference example id from list_reference_examples.
target_outcomestring–Optional target outcome, such as local learning workflow, deployment handover, or integration planning.

No output schema declared.

No examples provided.

generate_deployment_artifact_plan ~266

Map deployment choices to Compose/Kubernetes starter artifact profiles derived from the CE-RISE GitOps template.

NameTypeReqDescription
adoption_contextobject–Optional adoption or implementation context to carry through the plan.
check_remote_updatesboolean–When true, check configured update channels and include current metadata in the generated plan context.
hex_core_base_urlstring–Validation endpoint used by selected CE-RISE calculation services. May be an external compatible implementation; its compatibility is not assessed here.
include_internal_adapterboolean–When true, include the optional internal adapter Compose profile.
include_re_indicatorsboolean–When true, include RE Indicators Calculation Service profiles/extensions.
include_see_impactsboolean–Include SEE Impacts profiles/extensions independently of RE Indicators. Defaults to whether see_impacts_calculation_service is in selected_components.
selected_componentsarray–Optional selected CE-RISE ids and external component labels. Only selected CE-RISE parts are generated; omitting this argument requests the optional HEX Core reference baseline.
targetstring–Optional deployment target: compose, kubernetes, or both. Defaults to both.
timeout_secondsnumber–Optional HTTP timeout between 0 and 30 seconds for update checks.

No output schema declared.

No examples provided.

generate_deployment_artifacts ~322

Return Docker Compose and/or Kubernetes starter file contents derived from the existing CE-RISE GitOps template.

NameTypeReqDescription
auth_modestring–Optional HEX Core authentication mode placeholder, such as jwt_jwks or none.
check_remote_updatesboolean–When true, check configured update channels and use current metadata where it maps safely to generated artifact fields.
environmentstring–Optional environment label: local, dev, or prod.
external_io_adapter_urlstring–Optional external HTTP IO adapter URL placeholder.
hex_core_base_urlstring–Validation endpoint used by selected CE-RISE calculation services. May be an external compatible implementation; its compatibility is not assessed here.
include_internal_adapterboolean–When true, include the optional internal adapter Compose profile.
include_re_indicatorsboolean–When true, include RE Indicators Calculation Service profiles/extensions.
include_see_impactsboolean–Include SEE Impacts profiles/extensions independently of RE Indicators. Defaults to whether see_impacts_calculation_service is in selected_components.
project_namestring–Optional project name used for generated Kubernetes namespaces and artifact ids.
selected_componentsarray–Optional selected CE-RISE ids and external component labels. Only selected CE-RISE parts are generated; omitting this argument requests the optional HEX Core reference baseline.
targetstringyesRequired deployment target: compose, kubernetes, or both.
timeout_secondsnumber–Optional HTTP timeout between 0 and 30 seconds for update checks.

No output schema declared.

No examples provided.

generate_implementation_plan ~82

Generate an ordered implementation plan that reuses existing CE-RISE assets.

NameTypeReqDescription
architecture_idstring–Optional architecture pattern id from recommend_passport_architecture.
goalstringyesImplementation goal.
known_componentsarray–Optional selected CE-RISE ids and external component labels. User selections are preserved; reference patterns do not add mandatory components.

No output schema declared.

No examples provided.

generate_implementation_roadmap ~72

Generate a phased roadmap for Digital Passport adoption and implementation over existing CE-RISE assets.

NameTypeReqDescription
adoption_contextobjectyesDeclared adoption context.
adoption_path_idstring–Optional adoption path id from recommend_adoption_path.
time_horizonstring–Optional planning horizon label.

No output schema declared.

No examples provided.

identify_value_opportunities ~80

Identify practical value opportunities from shared Digital Passport information.

NameTypeReqDescription
adoption_contextobject–Optional adoption context object.
selected_flow_idsarray–Optional flow ids from map_value_chain_flows.
shared_informationarray–Optional declared shared information types or examples.
value_goalsarray–Optional target value goals beyond compliance.

No output schema declared.

No examples provided.

inspect_connected_source ~61

Inspect curated key files from one connected CE-RISE source, including Markdown headings when available.

NameTypeReqDescription
include_headingsboolean–When true, include Markdown headings discovered in key files.
source_idstringyesConnected source id from list_connected_sources.

No output schema declared.

No examples provided.

inspect_live_service_openapi ~77

Fetch and summarize the OpenAPI document from one live CE-RISE service connection.

NameTypeReqDescription
base_urlstring–Optional localhost-only base URL override for local testing.
service_idstringyesService id from list_live_service_connections.
timeout_secondsnumber–Optional HTTP timeout between 0 and 30 seconds.

No output schema declared.

No examples provided.

list_connected_sources ~59

List curated CE-RISE repositories, documentation sites, models, and service references connected to this assistant.

NameTypeReqDescription
include_statusboolean–When true, include local repository availability and key-file status.
kindstring–Optional source kind filter.

No output schema declared.

No examples provided.

list_deployment_artifact_templates ~48

List CE-RISE GitOps-template-derived deployment artifact profiles for Compose and Kubernetes outputs.

NameTypeReqDescription
targetstring–Optional target filter: compose, kubernetes, or both.

No output schema declared.

No examples provided.

list_live_service_connections ~45

List curated read-only live service discovery connections for CE-RISE services.

NameTypeReqDescription
service_familystring–Optional service family filter, such as core, storage, or calculation.

No output schema declared.

No examples provided.

list_reference_examples ~56

List curated CE-RISE reference examples that can be generalized without copying their concrete demo data or local-only settings.

NameTypeReqDescription
source_component_idstring–Optional CE-RISE component id filter, such as dp_system_local_demonstrator.

No output schema declared.

No examples provided.

list_solution_capabilities ~51

List deterministic assistant-facing CE-RISE capability families from the local catalog.

NameTypeReqDescription
familystring–Optional capability family filter, such as discovery, design, data-model, implementation, validation, or deployment.

No output schema declared.

No examples provided.

list_solution_components ~50

List known existing CE-RISE components and their intended assistant reuse role.

NameTypeReqDescription
capability_idstring–Optional capability id used to return related components.
kindstring–Optional component kind filter.

No output schema declared.

No examples provided.

list_update_channels ~96

List configured read-only CE-RISE repository, release, tag, documentation, and artifact update channels.

NameTypeReqDescription
component_idstring–Optional CE-RISE component id filter.
source_idstring–Optional connected source id filter.
update_rolestring–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 ~60

Map a user goal to existing CE-RISE capabilities and suggested components using the deterministic local catalog.

NameTypeReqDescription
constraintsarray–Optional project constraints or keywords.
user_goalstringyesUser's Digital Passport engineering goal.

No output schema declared.

No examples provided.

map_value_chain_flows ~109

Map requested, held, validated, enriched, or shared Digital Passport information across value-chain actors.

NameTypeReqDescription
adoption_contextobject–Optional adoption context object.
information_needsarray–Optional list of information needs or shared information types.
organization_rolestring–Optional organization role in the value chain.
product_scopestring–Optional product, material, asset, or process scope.
value_chain_actorsarray–Optional list of value-chain actors.

No output schema declared.

No examples provided.

probe_live_service ~101

Probe curated read-only GET endpoints for one live CE-RISE service connection.

NameTypeReqDescription
base_urlstring–Optional localhost-only base URL override for local testing.
endpoint_idsarray–Optional list of safe endpoint ids to probe. Omit to probe all safe endpoints for the service.
service_idstringyesService id from list_live_service_connections.
timeout_secondsnumber–Optional HTTP timeout between 0 and 30 seconds.

No output schema declared.

No examples provided.

recommend_adoption_path ~60

Recommend a CE-RISE reuse-oriented Digital Passport adoption path.

NameTypeReqDescription
adoption_contextobjectyesDeclared adoption context.
prioritiesarray–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 ~95

Recommend a CE-RISE reuse-oriented Digital Passport architecture pattern.

NameTypeReqDescription
prioritiesarray–Optional priorities such as local validation, deployment, model alignment, or production preparation.
selected_componentsarray–Optional user-selected CE-RISE ids and external component labels. When provided, this selection is preserved without adding a required CE-RISE stack.
use_casestringyesDigital Passport use case or implementation scenario.

No output schema declared.

No examples provided.

review_configuration_consistency ~144

Review supplied resolved Compose or rendered Kubernetes configuration for CE-RISE service, port, URL, model catalog, and authentication inconsistencies. Does not open supplied paths, contact services, or execute commands.

NameTypeReqDescription
environmentstring–Defaults to local; prod also checks for disabled authentication.
filesarrayyesFile path labels and JSON/YAML contents. Supply resolved Compose configuration or rendered Kubernetes manifests, not unevaluated Kustomize overlays. Redact credential values while retaining their key…
model_catalogobject|array–Optional catalog contents when a referenced catalog file is not supplied. Inline or mounted catalog contents take precedence.
targetstringyes–

No output schema declared.

No examples provided.

Install

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.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/dp-engineering-assistant-mcp

# add to Claude Code
claude mcp add ce-rise-software-dp-engineering-assistant -- docker run --rm -i ghcr.io/ce-rise-software/dp-engineering-assistant-mcp:0.0.2
Common questions

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

Is the CE-RISE Digital Passport Engineering Assistant MCP server safe to use?

CE-RISE Digital Passport Engineering Assistant scores 40 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 30 tools: list_solution_capabilities, list_solution_components, map_user_goal_to_ce_rise_capabilities, recommend_passport_architecture, generate_implementation_plan, and 25 more. Their descriptions and schemas cost roughly 2,739 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.