Loading ToolBench

Reading the current corpus…

API-2-MCP MCP server · F · ToolBench

← Browse

API-2-MCP

github.com/1692775560/API-2-MCP

Generate production-ready MCP servers from OpenAPI specs.

2026-07-28+STDIO3 tools

26/100

Definition Quality24

Protocol Readiness28

Supportability29

Spec posture

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

Static source inference · medium confidence

Current-spec patterns detected

Summary

This is a code generator (CLI tool), not an MCP server. The three 'tools' listed (initialize, tools/list, tools/call) are not actual MCP tool definitions but rather references to a smoke test script. No real tool schemas, descriptions, or parameters are defined in the source. The server generates MCP servers from OpenAPI specs but does not itself expose tools with proper definitions. Tool definitions are inferred from test script references, not explicitly registered.

Tools (3)

initializeread onlysource verified32/100

Initialize the MCP server and negotiate protocol version and capabilities

tools/callwriteauthsource verified28/100

Call a specific tool with provided arguments

tools/listread onlysource verified13/100

List all available tools exposed by the MCP server

Issues (5)

CRITICALtool ↗

Tool definitions are inferred from test script references, not explicitly visible in source code. No actual MCP tool registration found.

initializetools/listtools/call

CRITICALconstrained-input ↗

No input schemas visible for tools/list (empty required array suggests no parameters, but schema completeness cannot be verified).

tools/list

HIGHtool-description ↗

Tool descriptions are generic and lack actionable context. 'List all available tools' does not explain when to call it or what structure it reveals.

tools/list

HIGHresponse-shaper ↗

No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields.

initializetools/listtools/call

HIGHrecovery-guide ↗

Recommendations

Locate and examine the actual MCP server implementation (likely in src/ or dist/). The smoke test script is not the server definition.
For each tool, add a description 50-200 characters explaining WHAT it does, WHEN to use it, and WHAT it returns.
Document output schemas for all tools. Specify field names, types, and whether results are paginated.
Add parameter descriptions for 'protocolVersion', 'capabilities', 'clientInfo' in initialize, and 'name', 'arguments' in tools/call.
Implement error handling that returns actionable messages: 'Tool not found: <name>. Available tools: [list]' instead of generic errors.

Score history

Overall score trend

First recorded score · v2 rubric

26/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	26	2026-07-28+	v2