peer-mcp

Created By
aiworkspacea year ago
MCP Proxy to Expose Local MCP Server
Overview

what is peer-mcp?

peer-mcp is a proxy tool designed to expose a local MCP (Multi-Channel Protocol) server, allowing for easier access and interaction with local services.

how to use peer-mcp?

To use peer-mcp, set up your local MCP server and run the peer-mcp proxy to expose it. You can then access the server through the provided proxy URL.

key features of peer-mcp?

  • Exposes local MCP servers for external access
  • Simplifies the interaction with local services
  • Supports various configurations for flexibility

use cases of peer-mcp?

  1. Testing local applications that require external access.
  2. Developing and debugging services that need to communicate with a local MCP server.
  3. Facilitating collaboration by allowing team members to access local services remotely.

FAQ from peer-mcp?

  • What is an MCP server?

An MCP server is a server that uses the Multi-Channel Protocol to manage multiple communication channels.

  • Is peer-mcp free to use?

Yes! peer-mcp is open-source and free to use under the MIT license.

  • How do I configure peer-mcp?

Configuration details can be found in the documentation on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aiworkspace
Star
1
Language
-
License
MIT 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.

17 hours ago
Voyei

7 hours ago