Mcp MCP Server

https://mcp.redu.cloud/mcp Remote v2.0.0

Published by mcp.redu.cloud — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Agent-native cloud, EU-hosted. Provision VMs, networks & databases on redu.cloud via MCP.

Trust grade
B
82/100
Last scanned get badge →
Trust
B · 82/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
Live
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
B Why this grade threat 88 − adoption risk = 82/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 − 11.5 = 88. What the published surface and source actually contain:

PointsWhat was foundCategory
−9.5 Annotation contradicts behavior on "upgrade_to_cluster" ×2 MTC-CAP-003 permissions
−2.1 Reference to a credential-exfiltration path in metadata ×3 MTC-INJ-TARGET-1 injection

2. Client adoption risk — 88 − 6 = 82. 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

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 9

high Tool "upgrade_to_cluster" exposes command/code executionMTC-CAP-001

Tool "upgrade_to_cluster" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool upgrade_to_cluster

high Tool "deploy_compose" exposes command/code executionMTC-CAP-001

Tool "deploy_compose" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool deploy_compose

medium Unconstrained URL/host parameter "controller_url" on "trigger_agent_batch"MTC-CAP-007

Tool "trigger_agent_batch" takes a URL/host parameter "controller_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool trigger_agent_batch · inputSchema.properties.controller_url

medium Annotation contradicts behavior on "upgrade_to_cluster"MTC-CAP-003

Tool "upgrade_to_cluster" advertises destructiveHint=false but its derived capabilities include state-modifying actions (code-exec). Tool annotations are attacker-controllable and must never be trusted; a mismatch like this is exactly how a hostile server hides a destructive tool.

Fix: Ignore server-provided annotations for security decisions; gate destructive tools on explicit user consent.

Location: tool upgrade_to_cluster

medium Annotation contradicts behavior on "deploy_compose"MTC-CAP-003

Tool "deploy_compose" advertises destructiveHint=false but its derived capabilities include state-modifying actions (code-exec). Tool annotations are attacker-controllable and must never be trusted; a mismatch like this is exactly how a hostile server hides a destructive tool.

Fix: Ignore server-provided annotations for security decisions; gate destructive tools on explicit user consent.

Location: tool deploy_compose

medium Unconstrained command parameter "migrate_command" on "deploy_compose"MTC-CAP-006

Tool "deploy_compose" takes a command-shaped parameter "migrate_command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool deploy_compose · inputSchema.properties.migrate_command

low Reference to a credential-exfiltration path in metadataMTC-INJ-TARGET-1

Reference to a credential-exfiltration path in metadata detected in the inputSchema.properties.public_key.description of tool "import_keypair". Instruction-like content in tool metadata is executed by the model, not the human, and is the primary tool-poisoning vector.

Evidence: id_rsa

Fix: Tool descriptions should describe behavior, not instruct the assistant. Treat imperative / secrecy / sequencing language in metadata as hostile.

Location: tool import_keypair · inputSchema.properties.public_key.description

low Reference to a credential-exfiltration path in metadataMTC-INJ-TARGET-1

Reference to a credential-exfiltration path in metadata detected in the description of tool "get_ssh_command". Instruction-like content in tool metadata is executed by the model, not the human, and is the primary tool-poisoning vector.

Evidence: ~/.ssh

Fix: Tool descriptions should describe behavior, not instruct the assistant. Treat imperative / secrecy / sequencing language in metadata as hostile.

Location: tool get_ssh_command · description

low Reference to a credential-exfiltration path in metadataMTC-INJ-TARGET-1

Reference to a credential-exfiltration path in metadata detected in the inputSchema.properties.keypair_name.description of tool "get_ssh_command". Instruction-like content in tool metadata is executed by the model, not the human, and is the primary tool-poisoning vector.

Evidence: ~/.ssh

Fix: Tool descriptions should describe behavior, not instruct the assistant. Treat imperative / secrecy / sequencing language in metadata as hostile.

Location: tool get_ssh_command · inputSchema.properties.keypair_name.description

Tools 70

Each tool and what it can reach — enumerated from the running server.

  • deploy_composeruns code / shell
  • trigger_agent_batchnetwork egress
  • upgrade_to_clusterruns code / shell
  • architecture_diagramno sensitive capability
  • check_agent_prerequisitesno sensitive capability
  • check_deploy_prerequisitesno sensitive capability
  • create_api_keyno sensitive capability
  • create_backupno sensitive capability
  • create_clickhouseno sensitive capability
  • create_controllerno sensitive capability
Show 60 more tools ↓
  • create_databaseno sensitive capability
  • create_instanceno sensitive capability
  • create_media_spaceno sensitive capability
  • create_redisno sensitive capability
  • create_relational_databaseno sensitive capability
  • create_snapshotno sensitive capability
  • create_volumeno sensitive capability
  • delete_backupno sensitive capability
  • delete_clickhouseno sensitive capability
  • delete_clusterno sensitive capability
  • delete_databaseno sensitive capability
  • delete_deploymentno sensitive capability
  • delete_instanceno sensitive capability
  • delete_keypairno sensitive capability
  • delete_redisno sensitive capability
  • delete_relational_databaseno sensitive capability
  • delete_snapshotno sensitive capability
  • deploy_appno sensitive capability
  • deploy_overviewno sensitive capability
  • deploy_vpnno sensitive capability
  • get_agent_statusno sensitive capability
  • get_deploymentno sensitive capability
  • get_domain_verificationno sensitive capability
  • get_instance_logsno sensitive capability
  • get_ssh_commandno sensitive capability
  • import_keypairno sensitive capability
  • instance_actionno sensitive capability
  • integrate_overviewno sensitive capability
  • list_backupsno sensitive capability
  • list_clickhouse_databasesno sensitive capability
  • list_clustersno sensitive capability
  • list_databasesno sensitive capability
  • list_deploymentsno sensitive capability
  • list_dns_entriesno sensitive capability
  • list_domainsno sensitive capability
  • list_flavorsno sensitive capability
  • list_imagesno sensitive capability
  • list_instancesno sensitive capability
  • list_keypairsno sensitive capability
  • list_media_spacesno sensitive capability
  • list_private_networksno sensitive capability
  • list_redisno sensitive capability
  • list_regionsno sensitive capability
  • list_relational_databasesno sensitive capability
  • list_security_groupsno sensitive capability
  • list_snapshotsno sensitive capability
  • list_volumesno sensitive capability
  • plan_deployno sensitive capability
  • plan_instanceno sensitive capability
  • plan_managed_datastoreno sensitive capability
  • prepare_uploadno sensitive capability
  • restore_backupno sensitive capability
  • scaffold_localno sensitive capability
  • select_surfaceno sensitive capability
  • set_managed_backupsno sensitive capability
  • setup_agent_fleetno sensitive capability
  • setup_agent_sessionno sensitive capability
  • update_clusterno sensitive capability
  • verify_domainno sensitive capability
  • whoamino sensitive capability

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
v2.0.0 latest B 82/100 9 1.10.0 2026-07-24

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: B · 82/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-redu-cloud/badge.svg)](https://mcptrustchecker.com/registry/mcp-redu-cloud)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-redu-cloud"><img src="https://mcptrustchecker.com/registry/mcp-redu-cloud/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-redu-cloud/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 https://mcp.redu.cloud/mcp --online

Use the free API → How scoring works

More in AI & Agents