Trust Directory / report
Qovery MCP Server UNKNOWN
No anonymous handshake observed — endpoints behind authentication are expected to show this result; it does not mean the server is broken.
Deploy apps and manage Kubernetes on AWS, GCP, Azure, and On-Premise with natural language.
| Registry name | com.qovery/mcp-server (v1.0.1) |
|---|---|
| Endpoint | https://mcp-api-ai.qovery.com/mcp?token={qovery_token} |
| Reported server | — |
| Protocol version | not negotiated |
| Tools exposed | unknown |
| Checked at | 2026-10-11T03:33:03.555Z |
Findings
- UNKNOWN
NO_RESPONSE— Endpoint did not complete MCP initialize + tools/list within timeout
Reproduce this report
npx @eidonze/mcpdoctor schema https://mcp-api-ai.qovery.com/mcp?token={qovery_token}
Embed status: <img src="https://xka0085-byte.github.io/mcp-doctor/trust/badge/com.qovery-mcp-server.svg"> · Machine-readable: /api/com.qovery-mcp-server.json
Generated by mcpdoctor — read-only MCP initialize + tools/list. No tools were called, no payments attempted. Static schema checks do not predict model tool selection or prove behavior across all clients. Scanned: 2026-10-11.