MCP server providing HTTP/curl-like interface for making HTTP requests with session management, cookie persistence, and flexible response handling.
curl_request has a comprehensive schema with 8 well-typed parameters and clear descriptions (avg 60 chars/param), meeting baseline expectations. However, mcp_version is trivial (empty input, no output schema documented). Tool descriptions are adequate but lack WHEN-to-use guidance and dependency hints. No error handling guidance visible (e.g., timeout behavior, invalid URL handling). Output schemas are not documented, LLMs cannot plan downstream calls. Parameter descriptions lack format constraints (e.g., timeout range 1-120 is stated but not in schema). No tool annotations (readOnlyHint, idempotentHint) despite both tools being read-only.
Perform an HTTP request via curl-like interface.
Return version information for the curl-mcp server.
mcp_version tool has no documented output schema. LLMs cannot infer what fields (version, build, timestamp, etc.) are returned, blocking downstream reasoning.
curl_request lacks error handling guidance. No description of what happens on timeout, invalid URL, SSL errors, or network failures. LLMs cannot plan recovery.
No tool annotations (readOnlyHint, idempotentHint) despite both tools being read-only and safe to retry. Agents cannot distinguish safe tools from destructive ones.
curl_request description lacks WHEN-to-use guidance. Does not explain when to use this vs other HTTP tools, or mention session persistence behavior.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | <=2025-11-25 | v2 |
Response structure for curl_request not documented. LLMs cannot know if response includes status_code, headers, body, timing, or error details.