mcp

{
  "id": "aix_74b9a23ced",
  "name": "mcp",
  "operator": "(unclaimed - source: registry-official · publisher: cloud.redu)",
  "description": "Agent-native cloud, EU-hosted. Provision VMs, networks & databases on redu.cloud via MCP.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-25",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "browser-automation",
    "cache-store",
    "code-execution",
    "container-ops",
    "data-enrichment",
    "github-ops",
    "observability",
    "order-tracking",
    "sql-database",
    "vector-search"
  ],
  "protocols": {
    "mcp": "https://mcp.redu.cloud/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 678,
    "uptime_30d": 0.9888268156424581,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 55,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-25T19:01:14.536Z"
  },
  "pricing_model": "unknown",
  "profile": {
    "mcp_server": "redu-cloud-mcp",
    "mcp_version": "2.0.0",
    "tool_count": 81,
    "tools": [
      {
        "name": "whoami",
        "description": "Verifies your redu.cloud credential with a REAL server round-trip and returns your identity + live quota. A green result means the key actually works — not merely that one is configured. Use this first if anything is 401ing."
      },
      {
        "name": "check_deploy_prerequisites",
        "description": "The deploy ENTRY GATE — run this first when a user wants to deploy. Verifies the account is ready and AUTO-SELECTS the network_id + keypair_name to pass to deploy_app (so you never hunt for them): (1) account reachable + quota, (2) a private network (picks your default — every account has one), (3) an SSH keypair (if you have none, returns ssh_key_recipe: the exact local ssh-keygen → import_keypair → write SSH_KEY_LOCATION-to-.env steps — run them, in yolo mode without asking). Returns { ready, network_id, keypair_name, missing, ssh_key_recipe }."
      },
      {
        "name": "deploy_overview",
        "description": "Orientation for deploying an app on redu.cloud: the end-to-end flow, the two source modes (git vs upload), how to handle a missing Dockerfile or a database, when (and when NOT) to split a deploy across multiple VMs, verifying a deploy functionally, and how to debug a failed build. Call this first when a user asks to deploy/ship/host an app and you're unsure where to start."
      },
      {
        "name": "create_api_key",
        "description": "Mints a NEW least-privilege redu API key for a deployed app or automation to use (e.g. to add a backup feature). GUARDRAIL: the first call does NOT create anything. It returns a confirmation the user must approve, because a key is a long-lived credential that acts on the account and ANY usage of it is BILLED to the account owner. Show the user the name, the exact scopes, and the billing notice, get their explicit approval, then call again with confirm:true. This is required even in yolo/auto mode. The secret is returned ONCE."
      },
      {
        "name": "integrate_overview",
        "description": "Orientation for wiring a redu.cloud capability (backups, DNS, extra storage, a managed DB, ...) INTO an app already deployed on redu, e.g. 'add a backup feature to the Supabase I deployed on redu'. Explains the pattern: mint a LEAST-PRIVILEGE scoped API key (with the user's approval via create_api_key), inject it into the app, and call the redu API from the app. Call this when a user asks to add/integrate a redu feature into a running deployment and you are unsure how."
      },
      {
        "name": "prepare_upload",
        "description": "Returns the LOCAL shell commands to package your working directory and upload it for an upload-mode deploy (no git, no PAT). Run them in the user's terminal, capture `source_token` from the upload's JSON response, then call deploy_app with that source_token (omit repo). The upload authenticates AUTOMATICALLY with a short-lived ticket minted from your MCP credential — NO API key needed in the command and nothing secret is printed (it falls back to needing $REDU_API_KEY only if minting is unavailable). Excludes node_modules/.git/.venv/build output and .env by default; honors .gitignore when is_g"
      },
      {
        "name": "scaffold_local",
        "description": "OPTIONAL preflight: returns a podman-compose.yml + .env so the user can run the app (and a throwaway local Postgres) on THEIR machine before deploying to redu — to see it run / sanity-check the container. Requires local podman/podman-compose. It's a suggestion, not a gate — skip it and go straight to deploy_app any time. Honest caveat: the local Postgres is NOT the managed Postgres, so a green local run does not prove the prod DB wiring."
      },
      {
        "name": "plan_instance",
        "description": "Aggregates images/flavors/keypairs/networks/security groups into human-friendly choices. Does not create anything. Happy path: import_keypair → plan_instance → create_instance → get_ssh_command. Call this second (after import_keypair, if you have no keypairs)."
      },
      {
        "name": "plan_managed_datastore",
        "description": "Plans a direct managed datastore create without provisioning anything. Use this before create_database, create_relational_database, create_redis, or create_clickhouse. For app deployments, prefer deploy_app database:'managed' so plan_deploy includes and wires the datastore automatically. Pass ha:true to plan a highly available datastore (postgres or clickhouse): three machines instead of one, surviving the loss of a machine without manual failover, at roughly 3x the hourly rate. The returned plan carries the machine count so you can show the user the cost before anything is created."
      },
      {
        "name": "select_surface",
        "description": "For a repo with SEVERAL runnable parts, call this BEFORE plan_deploy. You enumerate the candidate surfaces (find every Dockerfile/Containerfile, OPEN each, classify by its EXPOSE + CMD — never by directory name) and pass them in; redu RANKS them with fixed rules (a standalone browser desktop/noVNC > a self-contained web app > a keys-required playground > an API > a headless worker > docs/examples). GUIDED: returns the ranked list to present to the user, who picks. YOLO: auto-selects the TOP-ranked surface. Then run plan_deploy on the chosen surface's path + http_port. (A single-surface repo do"
      },
      {
        "name": "plan_deploy",
        "description": "Turns YOUR repo classification (you scan the repo and pass what you found) into a complete, approvable deploy plan WITHOUT creating anything. ⚡ REDU NEEDS THREE FILES IF THEY EXIST - redu.md, the compose file, the Dockerfile - and there are two ways to give them. ⭐ BEST, for an upload-mode deploy: run prepare_upload FIRST and pass its `source_token`; redu reads all three straight out of the upload you already made, the upload stays deployable, and you emit nothing. Pasting the same files costs you 20-29 KB of output for bytes the server already has. Otherwise (git mode) paste `redu_md` (cat re"
      },
      {
        "name": "list_instances",
        "description": "Lists your compute instances."
      },
      {
        "name": "list_flavors",
        "description": "Lists available instance sizes."
      },
      {
        "name": "list_images",
        "description": "Lists available OS images."
      },
      {
        "name": "list_keypairs",
        "description": "Lists your SSH keypairs. If empty, call import_keypair first before creating instances."
      },
      {
        "name": "list_security_groups",
        "description": "Lists your security groups."
      },
      {
        "name": "list_private_networks",
        "description": "Lists your private networks."
      },
      {
        "name": "list_volumes",
        "description": "Lists your block storage volumes."
      },
      {
        "name": "list_snapshots",
        "description": "Lists your instance snapshots."
      },
      {
        "name": "list_backups",
        "description": "Lists your volume backups."
      },
      {
        "name": "list_clusters",
        "description": "Lists your autoscaling clusters."
      },
      {
        "name": "list_dns_entries",
        "description": "Lists DNS proxy host entries."
      },
      {
        "name": "list_domains",
        "description": "Lists custom domains you have verified ownership of."
      },
      {
        "name": "list_regions",
        "description": "Lists available regions."
      },
      {
        "name": "list_databases",
        "description": "Lists your managed PostgreSQL databases. Once a row's status is 'ready', it carries the private-network connection details (private_ip, port 5432, db_name, db_user)."
      }
    ],
    "profiled_at": "2026-09-25T19:01:14.536Z"
  },
  "unreachable": false,
  "payment_method": "oauth"
}