mcpware

Created By
delexwa year ago
Gateway MCP Server - Routes tool calls to Docker-based MCP backends
Overview

what is mcpware?

mcpware is a Gateway MCP Server that intelligently routes tool calls to multiple Docker-based MCP backends, ensuring comprehensive security validation.

how to use mcpware?

To use mcpware, clone the repository, build the Docker image, configure your backend servers in a JSON file, and run it as a Docker container.

key features of mcpware?

  • Bypass Tool Limits: Exposes only 2 routing tools while providing access to unlimited backend tools.
  • Built-in Security: Prevents cross-backend data leakage and blocks SQL injection.
  • Single Entry Point: Acts as a gateway for multiple MCP servers with automatic process management.

use cases of mcpware?

  1. Routing requests from a client application to various backend services.
  2. Managing multiple backend servers through a single interface.
  3. Enhancing security for data transactions between different services.

FAQ from mcpware?

  • Can mcpware handle multiple backend servers?

Yes! mcpware is designed to route requests to multiple backend servers efficiently.

  • Is mcpware secure?

Yes! It includes built-in security features to prevent data leakage and unauthorized access.

  • What are the prerequisites for using mcpware?

You need Docker and the Claude Desktop app to run mcpware.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
delexw
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
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.

8 hours ago