Loading ToolBench

Reading the current corpus…

mcp-hub MCP server · D · ToolBench

mcp-hub

Streamable HTTP gateway with auto-discovery, per-tenant RBAC, OAuth PKCE, rate limits, circuit breakers, audit, and token-saving lean tool schemas. Forwards W3C traceparent across upstreams.

2026-07-28+STREAMABLE_HTTP5 tools

53/100

Definition Quality44

Protocol Readiness75

SupportabilityNot measured-

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · detected: Dynamic Client Registration

Deprecated protocol patterns detected

Summary

mcp-hub is a gateway/proxy server, not a traditional MCP tool provider. Its 5 tools are meta-operations (initialize, ping, tools/list, tools/describe, tools/call) that manage upstream MCP servers rather than domain-specific functionality. Tool descriptions are present but minimal (10-50 chars). Input schemas exist for tools/describe and tools/call but lack parameter descriptions. The tools/call schema includes 'requestState' (UUID for idempotency) which is good, but overall parameter documentation is sparse. No output schemas are documented. Error handling is not visible in the provided code. The server itself is well-engineered (stateless HTTP, health checks, audit, RBAC), but the tool definitions fall short of production-grade agent tool standards.

Tools (5)

initializeread onlyauth37/100

Initialize the MCP connection and retrieve protocol version and server capabilities

pingread onlyauthsource verified33/100

Ping the server to verify connectivity

tools/callwriteauthsource verified58/100

Execute a tool with the given arguments and return the result

tools/describeread onlyauth50/100

Get the full schema for a specific tool by name

tools/listread onlyauthsource verified33/100

List all available tools with lean schemas (skeleton view) and metadata about token savings

Issues (5)

CRITICALtool ↗

No input schemas visible for initialize, ping, tools/list.

initializepingtools/list

HIGHtool-description ↗

Parameter descriptions missing. tools/describe has 'name' param with description, but tools/call's 'arguments' and 'requestState' params lack descriptions explaining what values are valid or how they are used.

tools/call

HIGHtool ↗

No output schemas documented. LLMs cannot plan downstream calls or extract required fields without knowing what initialize, ping, tools/list, and tools/describe return.

initializepingtools/listtools/describe

HIGHtool-description ↗

Tool descriptions are too brief (10-50 chars). Rubric baseline is 194 chars average; descriptions under 20 chars score 0-20. initialize, ping, tools/list lack context for LLM selection.

initializeping

Recommendations

Add explicit input schemas to initialize, ping, and tools/list (even if empty objects). Document what each returns (e.g., initialize returns {protocolVersion, capabilities, serverInfo}).
Expand tool descriptions to 100-200 chars. Example: 'tools/describe: Retrieve the full JSON Schema for a specific tool by name. Use this after tools/list to get parameter details before calling tools/call.'
Add descriptions to all parameters. For tools/call: 'arguments: Tool-specific input object matching the schema returned by tools/describe. requestState: UUID for idempotency; same UUID retried returns cached result.'
Document output schemas inline or in a separate schema registry. tools/call should document: {success: bool, result?: object, error?: {code, message, retryable}}.
Add error recovery guidance to tools/call description: 'If tool not found, call tools/list to verify name. If upstream fails, check server status via /admin/servers.'

Spec posture evidence

Inferred effective spec: 2026-07-28+.

Relies on Dynamic Client Registration (deprecated) - use Client ID Metadata Documents (CIMD)

Score history

Overall score trend

First recorded score · v2 rubric

53/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	53	2026-07-28+	v2