PowHTTP MCP

MCP server providing powerful HTTP client capabilities to AI agents — enabling agents to make arbitrary HTTP requests (GET, POST, PUT, DELETE, etc.), set custom headers, handle authentication, process responses, and interact with any REST API or web service via structured MCP tool calls.

Evaluated Mar 06, 2026 (0d ago) vcurrent

Homepage ↗ Repo ↗ Developer Tools http api-client web-requests mcp-server rest fetch

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

SSRF risk — can request any URL. Restrict accessible endpoints via network policies. Credentials in tool params are in agent context. Use with trusted agents only.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

An agent needs to call a web API that doesn't have a dedicated MCP server — PowHTTP provides a general-purpose HTTP bridge for any HTTP-accessible service.

Avoid When

A dedicated MCP server exists for your target service — purpose-built MCPs handle auth, pagination, and error handling more gracefully than raw HTTP calls.

Use Cases

• Making arbitrary HTTP requests to REST APIs from agent workflows
• Testing and debugging web API endpoints from development agents
• Fetching external data from web services when no dedicated MCP exists
• Automating API interactions that lack a dedicated MCP server

Not For

• Complex web scraping (use Crawlbase or Firecrawl for scraping with bot detection bypass)
• WebSocket or streaming connections (HTTP client is request/response only)
• Authenticated OAuth flows requiring browser redirect (manual OAuth steps)

Interface

REST API

GraphQL

gRPC

MCP Server

Yes ↗

SDK

Webhooks

Authentication

Methods: none

OAuth: No Scopes: No

No authentication for the MCP server itself. HTTP requests can include any custom headers (Bearer tokens, API keys) as parameters in tool calls.

Pricing

Model: free

Free tier: Yes

Requires CC: No

Free open source HTTP client MCP tool.

Agent Metadata

Pagination

none

Idempotent

Partial

Retry Guidance

Not documented

Known Gotchas

⚠ Agents can make requests to any URL — implement allowlisting if used in untrusted contexts
⚠ API keys passed in request headers are visible in tool call parameters — secure channel required
⚠ No built-in retry logic — agent must handle transient HTTP errors
⚠ Response parsing is raw — agents must handle JSON/HTML/binary responses themselves

Alternatives

fetch-mcp http-client-mcp requests-mcp

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for PowHTTP MCP.

$99

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-06.