OpenClaw MCP Ecosystem is listed as active in the registry but did not answer our last check. Last commit 27 Mar 2026.
9 remote MCP servers on Cloudflare Workers for AI agents. Free tier + Pro API keys.
We read the source, 7 h ago · rules 3dff92dd89df
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
check_command koyeb "curl -fsSL https://raw.githubusercontent.com/koyeb/koyeb-cli/master/install.sh | sh" || return 1
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
worker_path = os.path.join(base_dir, server_name, "worker.js")
const TELEGRAM_API = 'https://api.telegram.org/bot';
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
METRICS=$(curl -s -H "Authorization: Bearer ${{ secrets.FLEET_GATEWAY_TOKEN }}" \
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch OpenClaw MCP Ecosystem and you get told the day something new turns up.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.
claude mcp add openclaw-mcp-servers --transport http https://json-toolkit-mcp.yagami8095.workers.dev/mcp
{
"mcpServers": {
"openclaw-mcp-servers": {
"url": "https://json-toolkit-mcp.yagami8095.workers.dev/mcp"
}
}
}
[mcp_servers.openclaw-mcp-servers]
url = "https://json-toolkit-mcp.yagami8095.workers.dev/mcp"
{
"mcpServers": {
"openclaw-mcp-servers": {
"url": "https://json-toolkit-mcp.yagami8095.workers.dev/mcp"
}
}
}
{
"mcpServers": {
"openclaw-mcp-servers": {
"url": "https://json-toolkit-mcp.yagami8095.workers.dev/mcp"
}
}
}
This server publishes 8 more addresses. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://json-toolkit-mcp.yagami8095.workers.dev/mcp | streamable-http | answering | 50 ms | 11 min ago |
| https://regex-engine-mcp.yagami8095.workers.dev/mcp | streamable-http | answering | 61 ms | 11 min ago |
| https://color-palette-mcp.yagami8095.workers.dev/mcp | streamable-http | answering | 48 ms | 11 min ago |
| https://timestamp-converter-mcp.yagami8095.workers.dev/mcp | streamable-http | answering | 62 ms | 11 min ago |
| https://prompt-enhancer-mcp.yagami8095.workers.dev/mcp | streamable-http | answering | 55 ms | 11 min ago |
| https://openclaw-intel-mcp.yagami8095.workers.dev/mcp | streamable-http | answering | 50 ms | 11 min ago |
| https://openclaw-fortune-mcp.yagami8095.workers.dev/mcp | streamable-http | answering | 59 ms | 11 min ago |
| https://moltbook-publisher-mcp.yagami8095.workers.dev/mcp | streamable-http | answering | 60 ms | 11 min ago |
| https://agentforge-compare-mcp.yagami8095.workers.dev/mcp | streamable-http | answering | 71 ms | 11 min ago |
Hosted remote MCP server for YNAB on Cloudflare Workers with OAuth
smart-data-extractor MCP server on Cloudflare Workers · REST + MCP JSON-RPC · free tier
Cloudflare Workers MCP server: ai-prompt-optimizer
Cloudflare Workers MCP server: agent-memory
Cloudflare Workers MCP server: ai-agent-scratchpad
Cloudflare Workers MCP server: agent-trace-auditor
Cloudflare Workers MCP server: ai-eval
Cloudflare Workers MCP server: api-mock-server
Answers built from our own checks of this server.