Summary
A full HTTP surface, including the part most clients quietly sanitise.
Ordinary tools re-encode what you send, which is fine until the payload is the test — a quote in a query string, a malformed header. The raw call keeps it intact, and the log directory means a session leaves an artifact you can go back over.
What it is
An HTTP client exposed as a server. Every method gets its own call with full control over headers, cookies, body and timeout, and a raw request call preserves the payload exactly as written. Every request and response is written to ~/mcp_requests_logs/.
What you get
- GET, POST, PUT, DELETE, PATCH, HEAD and OPTIONS, each with headers, cookies, body and timeout
- A raw request that keeps every character exactly as provided — the point when the payload is an injection string the client would otherwise normalise
- Automatic logging of all requests and responses to ~/mcp_requests_logs/
- Bilingual documentation: the README covers every tool in English and Chinese
Requirements
Pip install mcp-request, then run the mcp-request command over stdio. No account and no key. The requests go out from your machine with your network access, so only point it at hosts you are allowed to test.
Setup effort
One command — pip install mcp-request