MCP HTTP Request Proxy

MCPOpen Source12.0

by chendatony31 • APIs & Integration

A lightweight MCP server that exposes and reuses arbitrary HTTP APIs through the Model Context Protocol, letting agents make and manage HTTP requests centrally.

Example Use Cases

1
Call arbitrary HTTP APIs (REST or RPC) through MCP without adding a separate MCP server per API.
2
Register and reuse API definitions (endpoints, methods, headers, and parameter schemas) so requests can be made consistently and programmatically.
3
Manage and inspect available APIs, perform pre-request processing, and centrally route requests (for things like querying blockchain RPCs or third-party services).

Description

mcp-request is a Model Context Protocol (MCP) server that lets you register, manage, and invoke HTTP APIs from a single MCP endpoint. It simplifies exposing existing HTTP services to agents without creating dedicated MCP servers per API, supports registering API definitions (including headers, params, and schemas), and offers utilities for listing and pre-processing requests. Typical uses include wrapping RPC endpoints (e.g., Sui RPC), adding ad-hoc API endpoints like weather queries, and centralizing request configuration.

Capabilities(4 total)

Tools (4)

registerApi

Register a new custom API. Complete API configuration information is required, including id, name, description, params, and api configuration.

config:string*

deleteApi

Delete a registered API.

id:string*

beforeRequest

Before querying any data, this tool first retrieves a list of available APIs that can be directly invoked. It returns a list of interface definitions. Based on the user's request match the appropriate API, prompts the user to complete the required input parameters, and then uses the request tool to make the call. The first argument to request tool is the id field of the selected API from the list, and complete other parameters that defined in the params field of the API using a JSON string type as the second argument.

request

This is a general tool for sending requests. It takes 2 parameters: the first is the id of the API to call, and the second is the parameters required for the API request

id:string*args:string*

Quick Actions

View on GitHub

Security

Scanned 2 month(s) ago

Risk Level

MINIMAL

Read-only data retrieval, no side effects

Trust Score

C57/100

9/17 checks passed

Scores are informational only and provided “as is” without warranty. AgentHotspot assumes no liability for actions taken based on these ratings.

Quick Stats

Service TypeMCP

Pricing ModelUnknown

Capabilities4 Tools / 0 Prompts / 0 Resources

Ownerchendatony31

CategoryAPIs & Integration

DependenciesStandalone

Set Your Username