A unified MCP gateway server that aggregates multiple MCP upstream servers (SSE, Stdio, HTTP) with admin dashboard for server management, API key control, and tool discovery.
Scoring was not performed
Missing input schemas for 4 of 6 tools (initialize, logging/setLevel, completion/complete, ping). Tools must declare input schema with parameter types and constraints.
tools/call accepts 'arguments' as bare object type with no schema, validation rules, or routing guidance. LLMs cannot infer valid argument structure without downstream schema visibility.
No output schemas documented for any tool. Agents cannot plan downstream calls or extract chaining IDs (e.g., what does tools/list return per item? field names?). This violates pattern:response-shaper.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 20 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 33 | 2024-11-05+ | v1 |
logging/setLevel description states 'Currently accepts request but does not modify logging behavior', this is non-functional stub masquerading as a tool. Removes false surface and either implement fully or remove.
completion/complete description states 'Returns empty completions to avoid client errors. Full implementation is a TODO.', non-functional stub. Either implement completion semantics or remove tool.
tools/list and tools/call descriptions lack error recovery guidance. No explanation of what errors can occur (permission denied, upstream server unreachable) or what agent should do next (e.g., 'If server not found, call tools/list to see available servers').
tools/call 'name' parameter description lacks format specification. Should state: 'Tool name in format serverName__toolName (double-underscore separator). Use tools/list to discover available tools.'
tools/list 'cursor' parameter has no guidance on format, expected next steps, or pagination exhaustion behavior. Should explain: 'Opaque string from previous call. Omit to start from beginning. Omit cursor when no more results.'
tools/call has no input validation rules for 'arguments' object. Should specify: expected size limits, max nesting depth, forbidden keys, and what happens if arguments violate downstream schema.
initialize tool should not be exposed as a callable tool. It is a protocol-level capability negotiation, not a user-callable action. Remove from tool list or mark with toolAnnotations.isMetadata=true.