MCP server for simplified framework deployments on shared hosting environments
HostBridge MCP exhibits significant definition quality gaps. While all 5 tools have basic descriptions (10-50 chars), they lack depth and actionability. Input schemas are present but minimal, parameters have type and description, but lack enums, constraints, or validation guidance. Output schemas are entirely undocumented; tools return free-text JSON strings rather than structured objects. Error handling is generic ('Failed to X: {error}') with no recovery guidance. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels. Parameter descriptions are sparse (e.g., 'Provider-specific credentials' for a Dict with no structure hint). The deploy_framework tool is IRREVERSIBLE but has no confirmation pattern or dry-run option. Overall, definitions are minimal and would not pass production code review.
Analyze and return the requirements for deploying a framework on a provider.
Store authentication credentials for a hosting provider.
Check the status of the configured server.
Deploy a framework to the specified hosting provider.
Analyze deployment errors and suggest solutions.
No output schemas documented. All tools return free-text JSON strings (via json.dumps) rather than structured, typed responses. LLMs cannot plan downstream calls or extract specific fields reliably.
deploy_framework is IRREVERSIBLE but lacks confirmation or dry-run pattern. No guard against accidental destructive operations by agents.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Risk levels are declared in metadata but not exposed to the MCP protocol, limiting agent safety planning.
Error messages are generic and non-actionable. 'Failed to check status: {error}' gives no recovery guidance. No error classification (retryable vs user-fixable vs fatal).
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | <=2025-11-25 | v2 |
Parameter 'credentials' in authenticate_provider is a bare Dict with no structure hint. No guidance on required keys, format, or provider-specific variations.