Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/ferprieto/mcp-http-client/mcp-http-client-servergit clone --depth 1 https://github.com/ferPrieto/MCP-Http-ClientWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/ferprieto/mcp-http-client/mcp-http-client-server)<a href="https://agentmods.dev/mcp/ferprieto/mcp-http-client/mcp-http-client-server"><img src="https://agentmods.dev/badge/mcp/ferprieto/mcp-http-client/mcp-http-client-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-http-client-server scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "mcp-http-client-server": { "command": "npx", "args": [ "-y", "mcp-http-client-server" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 9 lines scan A 089695a4c780
mcp-http-client-server is an MCP server published in the GitHub repository ferPrieto/MCP-Http-Client (7 stars, last pushed 8mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
cloudwatch
MCP server "cloudwatch" as configured in awslabs/mcp. Runs locally from the awslabs.cloudwatch-mcp-server@latest Python package. Needs 1 environment variable to run.
cloudwatch-appsignals
MCP server "cloudwatch-appsignals" as configured in awslabs/mcp. Runs locally from the awslabs.cloudwatch-applicationsignals-mcp-server@latest Python package. Needs 1 environment variable to run.
awesome-copilot
MCP server "awesome-copilot" as configured in microsoft/mcp-dotnet-samples. Runs in Docker (ghcr.io/microsoft/mcp-dotnet-samples/awesome-copilot:1.0.2026082702).
strata
MCP server for progressive tool usage at any scale (see https://klavis.ai). Remote server at strata.klavis.ai.
mcp-server-zotero-dev
MCP server enabling AI assistants to build, test, and debug Zotero plugins. Runs locally from the @introfini/mcp-server-zotero-dev npm package. Needs 2 environment variables to run.
solana-mcp-vybe
MCP server "solana-mcp-vybe", hosted remotely at mcp.vybenetwork.xyz, as configured in vybenetwork/solana-mcp-vybe.