MCP server for testing REST APIs by fetching OpenAPI specs, listing endpoints, resolving schemas, analyzing requirements, and making API calls
Four tools with basic descriptions and partial schemas. Tool names follow verb_noun convention (list_, get_, resolve_, analyze_) which is good. However, parameter descriptions are sparse or missing entirely. Output schemas are not documented, tools return JSON strings without specifying field structure. Error handling is minimal (mostly 'not found' messages). No input validation, no enum constraints, no pagination support. The resolve_schema and analyze_endpoint_requirements tools have longer descriptions (200+ chars) but lack parameter-level detail. Overall, definitions are functional but fall short of production quality.
Analyzes an endpoint and returns detailed information about what it requires: - Where parameters should be placed (query, body, form-data) - Required vs optional fields - Data types and validation rules - Authentication requirements - Content-Type expectations
Returns all details for a given endpoint path from the cached OpenAPI JSON, including all methods.
Fetches an OpenAPI JSON from the given URL and returns all endpoints with their descriptions. Also stores the OpenAPI JSON in a global cache for later use. Optionally filters endpoints by a search term (path, method, or description).
Resolves a schema reference (e.g., #/components/schemas/FranchiseAdminCreationRequest) from the cached OpenAPI spec and returns the complete schema definition with all fields, types, validation rules, and descriptions.
Output schemas not documented. All tools return JSON strings without specifying field structure, types, or required fields. LLMs cannot plan downstream calls or extract data reliably.
Parameter descriptions incomplete or missing. 'search' param in list_openapi_endpoints has a description, but get_endpoint_details 'path' param lacks detail on format/examples. analyze_endpoint_requirements 'method' param description is minimal.
No input validation or enum constraints. 'method' parameter accepts any string; should be constrained to GET, POST, PUT, DELETE, PATCH, etc. Free-form strings invite hallucinated values.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | 2026-07-28+ | v2 |
Error messages lack recovery guidance. 'No OpenAPI spec loaded' tells the LLM to call list_openapi_endpoints, but other errors (endpoint not found, schema not found) do not suggest next steps or alternatives.
Global state (openapi_cache, session_cache) creates stateful behavior. MCP protocol expects stateless request handling. Cache should be per-request or session-scoped, not global.