Other · Remote MCP server
OpenClaw MCP Ecosystem
9 remote MCP servers on Cloudflare Workers for AI agents. Free tier + Pro API keys.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.yedanyagamiai-cmd/openclaw-mcp-servers- Version
- 1.0.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-03-03
- Updated
- 2026-03-03
- Publisher
- yedanyagamiai-cmd (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/yedanyagamiai-cmd) · how
- Listed under
- Cloudflare MCP servers
- Website
- product-store.yagami8095.workers.dev
- Repository
- github.com/yedanyagamiai-cmd/openclaw-mcp-servers
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://json-toolkit-mcp.yagami8095.workers.dev/mcp | None |
| Streamable HTTP | https://regex-engine-mcp.yagami8095.workers.dev/mcp | None |
| Streamable HTTP | https://color-palette-mcp.yagami8095.workers.dev/mcp | None |
| Streamable HTTP | https://timestamp-converter-mcp.yagami8095.workers.dev/mcp | None |
| Streamable HTTP | https://prompt-enhancer-mcp.yagami8095.workers.dev/mcp | None |
| Streamable HTTP | https://openclaw-intel-mcp.yagami8095.workers.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://json-toolkit-mcp.yagami8095.workers.dev/mcp(HTTP)- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
- Endpoint
https://regex-engine-mcp.yagami8095.workers.dev/mcp(HTTP)- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
- Endpoint
https://color-palette-mcp.yagami8095.workers.dev/mcp(HTTP)- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
- Endpoint
https://timestamp-converter-mcp.yagami8095.workers.dev/mcp(HTTP)- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
- Endpoint
https://prompt-enhancer-mcp.yagami8095.workers.dev/mcp(HTTP)- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
- Endpoint
https://openclaw-intel-mcp.yagami8095.workers.dev/mcp(HTTP)- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
How to connect OpenClaw MCP Ecosystem
OpenClaw MCP Ecosystem is a remote MCP server: there is nothing to install. Its endpoints are https://json-toolkit-mcp.yagami8095.workers.dev/mcp, https://regex-engine-mcp.yagami8095.workers.dev/mcp, https://color-palette-mcp.yagami8095.workers.dev/mcp, https://timestamp-converter-mcp.yagami8095.workers.dev/mcp, https://prompt-enhancer-mcp.yagami8095.workers.dev/mcp and https://openclaw-intel-mcp.yagami8095.workers.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| OpenbeautyfactsOpen Beauty Facts MCP - Open Beauty Facts API (free, no auth, keyless). | Remote · HTTPLive check: ✓ handshake |
| opencapital.shGive your AI deep fundamentals on US public companies - metrics, segments, peers. Free. | Remote · HTTPLive check: sign-in required |
| OpenClaw Agent by Nova (CIVAI)I execute requests through OpenClaw as a personal AI agent with persistent context, browser and she… | Remote · HTTPLive check: ✓ handshake |
| Openclaw Cost Tracker MCPAI agent token-cost telemetry + 429 prediction. Per-agent attribution, anomaly + routing + quota. | Local · stdio |
| OpenClaw MCP ServerMCP server bridging Claude.ai/Desktop with self-hosted OpenClaw via OAuth 2.1. | Local · stdio |
| Openclaw Output Vetter MCPVerify AI agent claims vs reality: inline grounding-check + swallowed-exception + transcript review. | Local · stdio |
| Openclaw Skill Vetter MCPVet third-party AI agent extensions + agent-config files (AGENTS.md,.cursor/rules, CLAUDE.md). | Local · stdio |
| Openclaw Upgrade Orchestrator MCPAI runtime upgrade safety + provider-side regression detection (snapshot diff + fingerprint). | Local · stdio |