vsponeblock-mcp
Related Servers
Alternatives to vsponeblock-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables Claude and other MCP clients to discover and call Hitachi VSP 360 1.4 REST API operations, with search-based lookup, optional direct tools, automatic OAuth2 authentication, pagination, downloads, uploads, and read-only safety defaults.3890 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables Claude to query and manage NetApp ONTAP storage clusters directly, with read-only mode by default and optional provisioning/deletion tools when enabled.2-
- AlicenseAqualityDmaintenanceMCP server for the Wasabi WACM Connect API, enabling management of account hierarchy, storage, and billing data through Claude with 18 read-only and 12 opt-in write tools.181Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables testing and interacting with any REST API endpoints directly from MCP clients such as Claude and Cline, with support for multiple HTTP methods, authentication, custom headers, and response-size management.5 npmISC
- FlicenseAqualityDmaintenanceProvides tools for interacting with MinIO and S3-compatible object storage through MCP clients like Claude. It enables comprehensive bucket and object management, including listing, creating, uploading, and generating presigned URLs.132-
- AlicenseNot gradedqualityAmaintenanceEnables users to test and interact with any REST API endpoints directly from their development environment through MCP clients such as Claude and Cline. Supports GET, POST, PUT, DELETE, and PATCH requests with configurable authentication, custom headers, SSL verification, and response size limits.5 npmISC
TDQS
Scored across 3 tools
The three tools map to a clean discover → inspect → invoke pipeline (list, describe, call), each with an unambiguous role and no overlap. The descriptions even instruct the intended ordering, making misselection unlikely.
All tools share the vsponeblock_ prefix and a verb_noun pattern (describe_operation, list_operations, call_operation). The only nit is singular/plural inconsistency between 'operation' and 'operations', which is minor and readable.
This is a gateway/proxy pattern exposing an entire REST API, so three tools is exactly the right scope rather than a thin surface. Each tool earns its place and adding more would only fragment the discovery flow.
The set fully covers the read-only lifecycle: browse areas, list operations, inspect schemas, and invoke any operation, including async job and binary-response handling. Write operations are deliberately blocked, so the declarative surface can't create/update/delete, but this is a stated constraint rather than an oversight.