mcp-ovh-api
Related Servers
Alternatives to mcp-ovh-api
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceRead-only MCP server for browsing and reading S3 objects, with tools for listing buckets/objects, reading text and binary files, and extracting text from PDFs.-
- AlicenseAqualityDmaintenanceMCP server for AWS S3 — list buckets, browse objects, upload/download files, and generate presigned URLs.7128 npm4MIT
- AlicenseAqualityDmaintenanceMCP server for uploading, listing, and retrieving files on S3-compatible storage (AWS S3, DigitalOcean Spaces) with public/private access and temporary URLs.40MIT
- AlicenseAqualityAmaintenanceEnables management of Scaleway IAM (applications, API keys, policies, permission sets) and Object Storage bucket policies through an MCP server.11711 npmMIT
- AlicenseAqualityBmaintenanceEnables managing and interacting with any S3-compatible storage endpoint through MCP tools for listing, reading, writing, copying, and deleting buckets and objects.11MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to manage Backblaze B2 Cloud Storage through native B2 and S3-compatible tools, including bucket operations, file upload/download, key management, and presigned URLs.1-
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another. Its purpose is clearly stated as an authentication/configuration diagnostic.
The single tool name `ovh_auth_status` follows a clear snake_case domain-action pattern. With only one tool, there is no inconsistency to assess.
The server claims to be an OVHcloud API server but exposes only a single diagnostic tool. This is an extreme mismatch between the broad implied domain and the one available operation.
The surface contains only an auth-status check and no OVHcloud resource operations such as listing projects, managing instances, or any CRUD lifecycle. It is effectively a diagnostic stub rather than a usable API toolset.