# CE-RISE Digital Passport Engineering Assistant (oci · ghcr.io/ce-rise-software/dp-engineering-assistant-mcp:0.0.1)

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

- Trust score: 41/100 (low)
- Change this week: −2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- oci · `ghcr.io/ce-rise-software/dp-engineering-assistant-mcp:0.0.1`: 41/100 (this document), [markdown](https://verifymcp.io/servers/ce-rise-software-dp-engineering-assistant/ghcr-io-ce-rise-software-dp-engineering-assistant-mcp-0-0-1.md), [page](https://verifymcp.io/servers/ce-rise-software-dp-engineering-assistant/ghcr-io-ce-rise-software-dp-engineering-assistant-mcp-0-0-1)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/ce-rise-software/dp-engineering-assistant-mcp:0.0.1`
- 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-08-03.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - CVE data not yet available for this package.
  - Install-script risk not yet assessed.
  - Dependency-health data not yet available.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 87 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 2592 tokens (~72/item across 36 items; 29 tools + 7 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

## Install

### Claude

```bash
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
```

### Codex

```bash
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
```

### opencode

```json
{
  "$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
    }
  }
}
```

### Hermes

```yaml
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"]
```

### Other

```json
{
  "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"
      ]
    }
  }
}
```

## 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-08-02 (score 41, +3)

- [functional improvement] Stability: unverified → 0.20

### 2026-07-31 (score 38, −5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-27 (score 43, +35)

- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: good

### 2026-07-26 (score 8)

First indexed and scored.

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (29)

### `list_solution_capabilities` (~51 tokens)

List CE-RISE Solution Capabilities

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

Input parameters:

- `family` (string): Optional capability family filter, such as discovery, design, data-model, implementation, validation, or deployment.

### `list_solution_components` (~50 tokens)

List CE-RISE Solution Components

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

Input parameters:

- `capability_id` (string): Optional capability id used to return related components.
- `kind` (string): Optional component kind filter.

### `map_user_goal_to_ce_rise_capabilities` (~60 tokens)

Map User Goal To CE-RISE Capabilities

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

Input parameters:

- `constraints` (array): Optional project constraints or keywords.
- `user_goal` (string, required): User's Digital Passport engineering goal.

### `recommend_passport_architecture` (~60 tokens)

Recommend Passport Architecture

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

Input parameters:

- `priorities` (array): Optional priorities such as local validation, deployment, model alignment, or production preparation.
- `use_case` (string, required): Digital Passport use case or implementation scenario.

### `generate_implementation_plan` (~68 tokens)

Generate Implementation Plan

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

Input parameters:

- `architecture_id` (string): Optional architecture pattern id from recommend_passport_architecture.
- `goal` (string, required): Implementation goal.
- `known_components` (array): Optional known CE-RISE component ids already selected.

### `assess_implementation_readiness` (~62 tokens)

Assess Implementation Readiness

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

Input parameters:

- `project_context` (object, required): Declared implementation context. Useful keys include passport_scope, user_goal, data_sources, selected_components, data_model_strategy, deployment_context, and validation_strategy.

### `assess_adoption_context` (~84 tokens)

Assess Adoption Context

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

Input parameters:

- `adoption_context` (object, required): 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…

### `map_value_chain_flows` (~109 tokens)

Map Value-Chain Flows

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

Input parameters:

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

### `identify_value_opportunities` (~80 tokens)

Identify Value Opportunities

Identify practical value opportunities from shared Digital Passport information.

Input parameters:

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

### `recommend_adoption_path` (~60 tokens)

Recommend Adoption Path

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

Input parameters:

- `adoption_context` (object, required): Declared adoption context.
- `priorities` (array): Optional priorities such as compliance, local prototype, model alignment, value-chain exchange, or deployment preparation.

### `generate_implementation_roadmap` (~72 tokens)

Generate Implementation Roadmap

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

Input parameters:

- `adoption_context` (object, required): Declared adoption context.
- `adoption_path_id` (string): Optional adoption path id from recommend_adoption_path.
- `time_horizon` (string): Optional planning horizon label.

### `list_deployment_artifact_templates` (~48 tokens)

List Deployment Artifact Templates

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

Input parameters:

- `target` (string): Optional target filter: compose, kubernetes, or both.

### `generate_deployment_artifact_plan` (~174 tokens)

Generate Deployment Artifact Plan

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

Input parameters:

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

### `generate_deployment_artifacts` (~230 tokens)

Generate Deployment Artifacts

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

Input parameters:

- `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, required): Required deployment target: compose, kubernetes, or both.
- `timeout_seconds` (number): Optional HTTP timeout between 0 and 30 seconds for update checks.

### `assess_deployment_artifact_readiness` (~69 tokens)

Assess Deployment Artifact Readiness

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

Input parameters:

- `deployment_context` (object, required): Declared deployment context. Useful keys include target_runtime, selected_services, io_adapter_strategy, model_registry_strategy, auth_strategy, environment_overlays, and operational_checks.

### `list_reference_examples` (~56 tokens)

List Reference Examples

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

Input parameters:

- `source_component_id` (string): Optional CE-RISE component id filter, such as dp_system_local_demonstrator.

### `generalize_reference_example` (~105 tokens)

Generalize Reference Example

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

Input parameters:

- `adoption_context` (object): Declared adoption context. Useful keys include organization_role, passport_scope, value_chain_actors, shared_information, and value_goals.
- `example_id` (string, required): Reference example id from list_reference_examples.
- `target_outcome` (string): Optional target outcome, such as local learning workflow, deployment handover, or integration planning.

### `list_update_channels` (~96 tokens)

List Update Channels

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

Input parameters:

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

### `check_update_channels` (~86 tokens)

Check Update Channels

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

Input parameters:

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

### `build_update_aware_solution_context` (~118 tokens)

Build Update-Aware Solution Context

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

Input parameters:

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

### `discover_model_repositories` (~78 tokens)

Discover Model Repositories

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

Input parameters:

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

### `list_connected_sources` (~59 tokens)

List Connected CE-RISE Sources

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

Input parameters:

- `include_status` (boolean): When true, include local repository availability and key-file status.
- `kind` (string): Optional source kind filter.

### `check_connected_sources` (~64 tokens)

Check Connected Sources

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

Input parameters:

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

### `inspect_connected_source` (~61 tokens)

Inspect Connected Source

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

Input parameters:

- `include_headings` (boolean): When true, include Markdown headings discovered in key files.
- `source_id` (string, required): Connected source id from list_connected_sources.

### `build_connected_solution_snapshot` (~68 tokens)

Build Connected Solution Snapshot

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

Input parameters:

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

### `list_live_service_connections` (~45 tokens)

List Live Service Connections

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

Input parameters:

- `service_family` (string): Optional service family filter, such as core, storage, or calculation.

### `probe_live_service` (~101 tokens)

Probe Live Service

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

Input parameters:

- `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, required): Service id from list_live_service_connections.
- `timeout_seconds` (number): Optional HTTP timeout between 0 and 30 seconds.

### `inspect_live_service_openapi` (~77 tokens)

Inspect Live Service OpenAPI

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

Input parameters:

- `base_url` (string): Optional localhost-only base URL override for local testing.
- `service_id` (string, required): Service id from list_live_service_connections.
- `timeout_seconds` (number): Optional HTTP timeout between 0 and 30 seconds.

### `build_live_service_readiness_snapshot` (~71 tokens)

Build Live Service Readiness Snapshot

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

Input parameters:

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

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/ce-rise-software-dp-engineering-assistant/ghcr-io-ce-rise-software-dp-engineering-assistant-mcp-0-0-1#diagnostics

## Score history

- 2026-08-03: 41
- 2026-08-02: 41
- 2026-08-01: 38
- 2026-07-31: 38
- 2026-07-30: 43
- 2026-07-29: 43
- 2026-07-28: 43
- 2026-07-27: 43
- 2026-07-26: 8

## Links

- Repository: https://github.com/CE-RISE-software/dp-engineering-assistant
- Changelog RSS feed: https://verifymcp.io/servers/ce-rise-software-dp-engineering-assistant/ghcr-io-ce-rise-software-dp-engineering-assistant-mcp-0-0-1/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ce-rise-software-dp-engineering-assistant/ghcr-io-ce-rise-software-dp-engineering-assistant-mcp-0-0-1/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ce-rise-software-dp-engineering-assistant/ghcr-io-ce-rise-software-dp-engineering-assistant-mcp-0-0-1