Multi-server MCP framework with PostgreSQL, SSH, Penpot, and pipeline tools. Includes shared error handling, circuit breakers, health checks, and proof-of-completion parameters.
14 tools with mixed quality. Most have basic descriptions (50-150 chars) and input schemas, but lack depth in parameter documentation and output schema specification. SSH tools dominate (9/14) with repetitive patterns. Critical gaps: no tool annotations (destructiveHint/readOnlyHint), minimal error recovery guidance, and vague parameter descriptions. Pipeline tool shows promise with structured proof parameters but lacks output schema docs. PostgreSQL tools are minimal. Average description length ~110 chars (below 194-char baseline); many parameters lack type constraints or format guidance.
Export query results to Excel format
Execute a SQL query against the PostgreSQL database
Inspect PostgreSQL database schema
Mark a pipeline stage as complete with proof of completion
Create or manage server aliases
Check connection status for all pooled SSH connections
Manage server groups for batch operations
Run health checks on a remote server (disk, memory, load, uptime)
No tool annotations (destructiveHint, readOnlyHint, idempotentHint) despite 9 WRITE and 1 IRREVERSIBLE tool. LLMs cannot distinguish safe from dangerous operations without explicit hints.
Output schemas not documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., what does ssh_list_servers return? server_id? hostname? connection_state?). Breaks tool chaining.
Parameter descriptions lack format/constraint guidance. 'server_id' appears in 6 tools but no description explains: is it a hostname, alias, or internal ID? 'query' in pg_query has no guidance on SQL dialect, injection risks, or result limits.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | <=2025-11-25 | v2 |
Manage SSH keys on a remote server (list, add authorized key)
List all configured SSH servers
List, find, or kill processes on a remote server
View or set server profile metadata (tags, notes, env)
Check the status of a systemd service on a remote server
Check health of all apex-data-mcp services
No error recovery guidance. Tools lack descriptions of failure modes, retryability, or next steps. E.g., ssh_health_check fails silently if server_id is invalid, no guidance to LLM on how to recover.
SSH tools accept opaque 'server_id' (alias) but no discovery tool to list valid aliases. Agents must guess or fail. Missing list_ssh_aliases or equivalent.