Rhoai MCP Server

rhoai-mcp PyPI v0.1.1

Published by opendatahub-io — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Red Hat OpenShift AI

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

high Shell/command execution in server code (evals/reporting/recorder.py)MTC-SRC-002

In the server's implementation (`evals/reporting/recorder.py:38`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: commit = ( subprocess.check_output( ["git", "rev-parse", "--short", "HEAD"],

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server evals/reporting/recorder.py

high Shell/command execution in server code (src/rhoai_mcp/domains/model_registry/auth.py)MTC-SRC-002

In the server's implementation (`src/rhoai_mcp/domains/model_registry/auth.py:114`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: result = subprocess.run( [cli_path, "whoami", "-t"], capture_outp

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/rhoai_mcp/domains/model_registry/auth.py

Tools 90

Each tool and what it can reach — statically extracted from the published source.

  • get_registered_modelingests untrusted input
  • analyze_training_failureno sensitive capability
  • check_deployment_prerequisitesno sensitive capability
  • check_training_prerequisitesno sensitive capability
  • cluster_summaryno sensitive capability
  • create_data_science_projectno sensitive capability
  • create_pipeline_serverno sensitive capability
  • create_runtimeno sensitive capability
  • create_s3_data_connectionno sensitive capability
  • create_serving_runtimeno sensitive capability
Show 80 more tools ↓
  • create_storageno sensitive capability
  • create_workbenchno sensitive capability
  • delete_data_connectionno sensitive capability
  • delete_data_science_projectno sensitive capability
  • delete_inference_serviceno sensitive capability
  • delete_pipeline_serverno sensitive capability
  • delete_runtimeno sensitive capability
  • delete_storageno sensitive capability
  • delete_training_jobno sensitive capability
  • delete_workbenchno sensitive capability
  • deploy_modelno sensitive capability
  • diagnose_resourceno sensitive capability
  • estimate_resourcesno sensitive capability
  • estimate_serving_resourcesno sensitive capability
  • explore_clusterno sensitive capability
  • find_benchmarks_by_gpuno sensitive capability
  • fix_pvc_permissionsno sensitive capability
  • get_catalog_model_artifactsno sensitive capability
  • get_cluster_resourcesno sensitive capability
  • get_data_connectionno sensitive capability
  • get_deployment_configno sensitive capability
  • get_example_itemno sensitive capability
  • get_inference_serviceno sensitive capability
  • get_job_eventsno sensitive capability
  • get_job_specno sensitive capability
  • get_model_artifactsno sensitive capability
  • get_model_benchmarksno sensitive capability
  • get_model_endpointno sensitive capability
  • get_model_versionno sensitive capability
  • get_pipeline_serverno sensitive capability
  • get_project_detailsno sensitive capability
  • get_resourceno sensitive capability
  • get_runtime_detailsno sensitive capability
  • get_training_jobno sensitive capability
  • get_training_logsno sensitive capability
  • get_training_progressno sensitive capability
  • get_validation_metricsno sensitive capability
  • get_workbenchno sensitive capability
  • get_workbench_urlno sensitive capability
  • list_catalog_sourcesno sensitive capability
  • list_data_connectionsno sensitive capability
  • list_data_science_projectsno sensitive capability
  • list_example_itemsno sensitive capability
  • list_inference_servicesno sensitive capability
  • list_model_versionsno sensitive capability
  • list_notebook_imagesno sensitive capability
  • list_registered_modelsno sensitive capability
  • list_resource_namesno sensitive capability
  • list_resourcesno sensitive capability
  • list_serving_runtimesno sensitive capability
  • list_storageno sensitive capability
  • list_tool_categoriesno sensitive capability
  • list_training_jobsno sensitive capability
  • list_training_runtimesno sensitive capability
  • list_workbenchesno sensitive capability
  • manage_checkpointsno sensitive capability
  • manage_resourceno sensitive capability
  • multi_resource_statusno sensitive capability
  • prepare_model_deploymentno sensitive capability
  • prepare_trainingno sensitive capability
  • project_summaryno sensitive capability
  • recommend_modelno sensitive capability
  • recommend_serving_runtimeno sensitive capability
  • resource_statusno sensitive capability
  • resume_training_jobno sensitive capability
  • run_container_training_jobno sensitive capability
  • set_model_serving_modeno sensitive capability
  • setup_hf_credentialsno sensitive capability
  • setup_nfs_storageno sensitive capability
  • setup_training_runtimeno sensitive capability
  • setup_training_storageno sensitive capability
  • start_workbenchno sensitive capability
  • stop_workbenchno sensitive capability
  • suggest_toolsno sensitive capability
  • suspend_training_jobno sensitive capability
  • test_model_endpointno sensitive capability
  • trainno sensitive capability
  • trainingno sensitive capability
  • validate_training_configno sensitive capability
  • wait_for_job_completionno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.1 latest A 93/100 2 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/rhoai-mcp/badge.svg)](https://mcptrustchecker.com/registry/rhoai-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/rhoai-mcp"><img src="https://mcptrustchecker.com/registry/rhoai-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/rhoai-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan rhoai-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools