HTTP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 19 Aug 2026.
MCP server for HTTP requests (curl) with structured, token-efficient output
What the code does
We read the source, 2 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const output = execFileSync(resolver, [cmd], {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to HTTP
same job, measured the same wayMCP server for code search (ripgrep + fd) with structured, token-efficient output
MCP server for Make/Just task runners with structured, token-efficient output
MCP server for GitHub operations (PRs, issues, actions) with structured, token-efficient output
A lightweight, structured, token-efficient local-first MCP memory server
MCP server for API testing: HTTP requests, cURL generation, health checks.
Token-efficient MCP server for MySQL, PostgreSQL, and SQLite
Token-efficient MCP server for MySQL, PostgreSQL, and SQLite
Hash-verified file editing MCP server with token efficiency hook for AI coding agents.
HTTP — questions
Answers built from our own checks of this server.