MCP REST

Created By
ivanboringa year ago
Exposes a SSE MCP server as a rest endpoints for tools. Only for testing
Overview

what is MCP REST?

MCP REST is a REST API wrapper around the Model Context Protocol (MCP) client, designed for testing purposes. It allows users to interact with the MCP server without maintaining a constant connection.

how to use MCP REST?

To use MCP REST, install it globally using npm or run it with npx. You can connect to an SSE server by specifying the server URL and port as options.

key features of MCP REST?

  • Provides REST endpoints for interacting with the MCP server.
  • Supports connection to custom SSE servers.
  • Offers debugging options for troubleshooting.

use cases of MCP REST?

  1. Testing interactions with the MCP server without a persistent connection.
  2. Listing available tools and checking connection status via API endpoints.
  3. Calling specific tools with arguments through REST API requests.

FAQ from MCP REST?

  • Is MCP REST suitable for production use?

No, MCP REST is intended for testing purposes only and should not be used in a production environment.

  • How do I install MCP REST?

You can install it globally using npm install -g mcp-rest or use it with npx mcp-rest.

  • What are the available API endpoints?

The available endpoints include /status to check connection status and /tools to list all available tools.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ivanboring
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

35 minutes ago