MetaMesh UGA

What MetaMesh-UGA MCP server does

The MetaMesh-UGA MCP server acts as a control plane and gateway for MCP infrastructure. Its catalog synchronizes with the official MCP Registry every six hours and currently indexes more than 13,000 MCP servers, according to the project documentation. Clients can connect through https://api.metamesh-uga.dev/mcp using JSON-RPC over HTTP.

The gateway provides MCP discovery and native tools, while its REST API supports paginated tool listings, full-text search, and tool execution. A CLI is also provided for connecting to the gateway, invoking tools, listing tools by category, and viewing usage.

How it works

Requests pass through a routing layer that can consider latency, health, geography, cost, and weighted routing policies. The project describes a trust score based on uptime, latency, success rate, and security signals. Reliability features include retries, circuit breakers, bulkheads, hedging, and fallback behavior.

The platform also includes multiple cache levels, lifecycle states for catalog entries, dependency and CVE scanning, and an OPA/Rego policy engine. Health-based remediation and automatic deprecation are described as part of its self-healing and lifecycle behavior. Analytics cover usage, cost, and performance, with export support for OpenTelemetry and Prometheus.

The hosted gateway runs on Cloudflare Workers. Cloudflare D1 is used for the catalog database, KV for caching, and R2 for WebAssembly assets in the documented deployment setup. The project also describes a WebAssembly runtime for MCP tools compiled to WASM.

Setup and configuration

For self-hosting, the repository documents Node.js 18+, Go 1.21+, a Cloudflare account, and a Stripe account for payment features. The setup creates a D1 database, KV namespace, and R2 bucket, then applies the included SQL migration and deploys the Workers and dashboard packages.

Secrets documented for deployment include STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, JWT_SECRET, and ADMIN_KEY. Telegram credentials are optional. The CLI is built from the cli directory with Go and can then be installed on the local path.

Clients can use the hosted MCP URL directly. The README provides configurations for Claude Desktop, Cursor, and Windsurf using HTTP transport.

Tools and capabilities

Documented capabilities include:

• Registry synchronization, federation, mirroring, and snapshots
• Keyword, semantic, capability-graph, and intent-based discovery
• Health, reputation, security, and performance scoring
• Routing based on health, latency, geography, cost, or weights
• Caching with TTL and pattern invalidation
• Security scanning and OPA/Rego policy enforcement
• Usage, cost, and performance analytics
• REST, CLI, and MCP access to cataloged tools
• Stripe prepaid balances and per-call billing
• Optional x402 payments using USDC on Base

Limitations and notes

Stripe billing applies to the documented REST POST /v1/call flow when enforcement is enabled. The public MCP endpoint remains available for discovery and native metamesh.* tools without an account, according to the current production notes. x402 support is implemented but requires operator wallet configuration before activation.

The repository describes hosted service plans of Free, Pro at $19 per month, and Enterprise at $499 per month, but does not establish whether those plans apply to every deployment. Self-hosting requires Cloudflare resources and deployment configuration rather than a single standalone executable.