MCP server for HTTP API testing with Playwright. Supports full CRUD operations, path/query parameters, and comprehensive error handling for API automation workflows.
This server presents 4 HTTP operation tools with basic schemas and tool annotations, but suffers from severe description deficiencies, lack of parameter documentation, and missing error handling guidance. All tools are explicitly registered in src/server.ts with Zod schemas and toolAnnotations present, but descriptions are truncated (6-22 chars), and parameters lack descriptions entirely. The server implements basic CRUD operations but falls well short of production quality due to incomplete documentation and no guidance for LLM error recovery.
send the delete request
send the get request
send the post request
send the put request
All tool descriptions are under 20 characters ('send the post request', 'send the get request', etc.). Per HARD SCORING RULES, descriptions under 20 chars score 0-20 maximum. These provide zero context for LLM tool selection and violate pattern:tool-description baseline of 194 chars average for A+ tools.
NO parameter descriptions exist in any tool. All parameters (url, data, headers, timeout, pathParams, queryParams) lack descriptions. Per HARD SCORING RULES, parameters without descriptions violate pattern:tool-description baseline (100% of A+ tool params have descriptions). LLMs cannot determine parameter purpose or valid values.
No output schema documentation. While handlers return text content with status and response body, the structure is not formally documented. Pattern:tool and pattern:response-shaper require documented output schemas so LLMs know what fields to expect for chaining and extraction.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 41 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 32 | - | v1 |
Generic error messages ('Error occurred while sending POST request: ...') provide no recovery guidance. Per pattern:recovery-guide, errors must tell the LLM what to do next. A 404 or timeout should suggest next steps (retry, verify URL, check headers), not just echo the error.
No input validation or constraint descriptions. Parameters like 'timeout' are numeric but have no min/max documented. 'headers' and 'data' accept passthrough objects with no schema validation guidance. Per pattern:constrained-input, numeric params should declare bounds (e.g., 'timeout in milliseconds, 100-60000').
delete_request tool has destructiveHint: true but no confirmation step or dry-run. Per pattern:confirmation-request, irreversible operations should support confirmation or a preview step to prevent accidental data loss.
Parameter 'data' and 'headers' use z.object({}).passthrough().optional(), which accepts arbitrary objects with no schema validation. This invites hallucinated JSON structures and malformed payloads. Pattern:constrained-input recommends explicit schema or structured description of expected format.
No mention of HTTP authentication, bearer tokens, or API key injection in descriptions or parameters. Pattern:secret-injection forbids credentials in params, but the server should document how auth is handled (e.g., pass auth headers via 'headers' param) and whether token injection is supported.