mcp-registry/cloud.redu/mcp · v2.0.0
As of 2026-10-27 01:27 UTC, the Redu MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 19 outages in 90 days, with a median recovery of 4 minutes.
Agent-native cloud, EU-hosted. Provision VMs, networks & databases on redu.cloud via MCP.
Point your MCP client at this streamable-http endpoint: https://mcp.redu.cloud/mcp
5 tool definition(s) exceed ~1,200 tokens each (largest: deploy_app, ~3,754).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~11,157 tokens every session. How to fix →
91 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
87 parameter(s) across 24 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
5 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Loading this server's tool list costs an agent ~35,063 tokens before any work — more than 99% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
In the last 30 days: 6 tool(s) removed and 34 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Runs commands or code supplied by the model. Legitimate for dev tools; clients should require confirmation. Example (exec_private_vps, name): "exec_private_vps(script, request_key, operation_id, timeout_seconds)"
Declare destructiveHint/readOnlyHint on these tools and say plainly in the description what runs, where, and with what limits. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 24 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcloud.redu%2Fmcp/fixes
{
"name": "postgres_data_change",
"description": "Changes the data INSIDE a managed Postgres database, as the console does: rows, tables and columns, a SQL write, a CSV import, saved queries, the editing lock. Each write is sent once. Deleting, dropping, renaming, a SQL write and unlocking need confirm: true, set only after the user said yes. Call postgres_data_read action help first for the arguments.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"action"
],
"properties": {
"id": {
"type": "integer"
},
"to": {
"type": "string"
},
"csv": {
"type": "string"
},
"key": {
"type": "string"
},
"sql": {
"type": "string"
},
"keys": {
"type": "array",
"items": {
"type": "array",
"items": {
"type": "string"
}
}
},
"name": {
"type": "string"
},
"rows": {
"type": "array",
"items": {
"type": "array"
}
},
"table": {
"type": "string"
},
"action": {
"enum": [
"help",
"insert",
"update",
"delete",
"sql",
"create_table",
"rename_table",
"add_column",
"rename_column",
"drop_column",
"drop_table",
"restore_table",
"import",
"saved_save",
"saved_update",
"saved_delete",
"lock",
"unlock"
],
"type": "string"
},
"column": {
"type": "string"
},
"create": {
"type": "string"
},
"changes": {
"type": "array",
"items": {
"type": "object",
"required": [
"column",
"old",
"new"
],
"properties": {
"new": {
"type": [
"string",
"null"
]
},
"old": {
"type": [
"string",
"null"
]
},
"column": {
"type": "string"
}
},
"additionalProperties": false
}
},
"columns": {
"type": "array"
},
"confirm": {
"type": "boolean",
"description": "Only after the user said yes."
},
"delimiter": {
"enum": [
"comma",
"semicolon",
"tab",
"pipe"
],
"type": "string"
},
"write_ref": {
"type": "string",
"format": "uuid"
},
"trash_name": {
"type": "string"
},
"column_spec": {
"type": "string"
},
"database_id": {
"type": "integer",
"exclusiveMinimum": 0
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": true
},
"title": "Change Postgres data"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/cloud.redu/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/cloud.redu/mcp"}) over MCP.
deploy_app ~3,754 tokensdeploy_compose ~3,392 tokensplan_deploy ~3,226 tokensupgrade_to_cluster ~2,489 tokenscreate_clickhouse ~1,296 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcloud.redu%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcloud.redu%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcloud.redu%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcloud.redu%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fcloud.redu%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a7ec760564f2c644…, first seen 2026-10-26, included at leaf 74055 of 76,589. Version history · verify what your client received.
Compare: most reliable cloud servers · most reliable devops servers · most reliable security servers · most reliable database servers · most reliable files servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 01:27 UTC, the Redu MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 19 outages in 90 days, with a median recovery of 4 minutes.
Redu MCP server advertises 91 tools, including architecture_diagram, attach_volume, check_deploy_prerequisites, create_api_key, create_backup.
Point your MCP client at this streamable-http endpoint: https://mcp.redu.cloud/mcp
Glimind scanned all 91 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.