"Unofficial Minecraft Proxy (MCP) Server" matching MCP servers:

A single-tool MCP proxy that exposes Dokploy's full tRPC API (473 endpoints) with multi-instance support and on-demand skill loading, saving 77-92% tokens compared to the official MCP.

Enables managing a Vercel account through MCP tools such as listing projects, viewing deployments and logs, and redeploying. Includes an OAuth layer so Gemini Spark can connect securely.

Enables AI agents and external systems to programmatically trigger and monitor Jenkins jobs, retrieve build status and logs via MCP standards.

Supply-chain gate for AI agent skills and MCP servers: poison-scan tool definitions, hash-pin the vetted set into a lock file and verify drift in CI. truecopy-mcp is a drop-in stdio proxy that filters a live server's tools/list down to its pinned, unmodified, unpoisoned tools.

Budget & cost control for AI agents: hard per-agent spend caps, rate limits, idempotency, and human-in-the-loop approval — enforced before each LLM call, not after the invoice. One hosted MCP endpoint (no proxy or self-hosting), settled via x402 (USDC on Base).

Connects MCP-compatible coding agents to a hosted Test Maze instance for verifying test scenarios via a stdio-to-HTTP proxy.

Enables AI coding agents to fetch the real latest versions of packages from npm, PyPI, crates.io and the Go module proxy, then check manifests or whole projects for outdated dependencies and rewrite them in place. It also reports the current releases and underlying dependency stacks of AI coding tools like Claude Code, Codex and Gemini CLI.

Unofficial MCP server for Railway that enables managing Railway infrastructure through natural language, including projects, services, deployments, environments, variables, templates, domains, volumes, observability, integrations, networking, and workflows.

Enables AI assistants to manage hosted sites through a local stdio proxy to the backend MCP endpoint, covering site configuration, deployments, assets, CMS schemas and entries, webhooks, contact submissions, and API credentials.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{