Is the io.github.yedanyagamiai-cmd MCP server working?

Is the io.github.yedanyagamiai-cmd MCP server working?

No, not as the registry describes it. 9 declared endpoints failed the MCP initialize handshake on 2026-09-17 — the protocol's own way of asking a server to identify itself. No tool was ever called.

ERR-2026-4317, ERR-2026-4318, ERR-2026-4319, ERR-2026-4320, ERR-2026-4321, ERR-2026-4322, ERR-2026-4323, ERR-2026-4324, ERR-2026-4325

Every record behind those answers

9 open records, observed 2026-09-10. Every claim below carries the command that disproves it. If one is wrong, it should be withdrawn — 111 have been across the whole registry.

the endpoint is gone (9)

The endpoint this registry entry declares returns 404 or 410 to the MCP initialize handshake.

ERR-2026-4317https://json-toolkit-mcp.yagami8095.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-4318https://regex-engine-mcp.yagami8095.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-4319https://color-palette-mcp.yagami8095.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-4320https://timestamp-converter-mcp.yagami8095.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-4321https://prompt-enhancer-mcp.yagami8095.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-4322https://openclaw-intel-mcp.yagami8095.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-4323https://openclaw-fortune-mcp.yagami8095.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-4324https://moltbook-publisher-mcp.yagami8095.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-4325https://agentforge-compare-mcp.yagami8095.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17

Check it yourself:

curl -s -X POST https://json-toolkit-mcp.yagami8095.workers.dev/mcp -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"check","version":"1"}}}'

Also filed as: io.github.yedanyagamiai-cmd/openclaw-mcp-servers. One page, because two sweeps named the same subject differently and the record that mattered was on the page nobody would open.

If a record here is wrong

Run its check. If the answer differs from what is written, say so here and it will be withdrawn — 111 already have been. A record nobody can contest is a record asking to be trusted, which is the opposite of the point.

What this page does not tell you

This is not a clean bill of health for anything not listed. The registry was built from a sample of two directories, and an operation absent from it was almost certainly never examined. Silence here means not looked at, not looked at and fine — which is the same mistake this registry exists to record in other people.

What this is

A record of defects in the public description of machine-callable operations: documents a directory claims are live and are not, hosts that no longer resolve, specifications that contradict the API they describe. It is not a ranking, not a review, and not a judgement about the service. No credential is ever sent to anything listed here.

The whole registry, machine-readable: errata.json. Index of subjects: index.html.

Built from registry errata-2026-09-10@21826040e38a. If manifest.json shows a different one, this page is behind the records and should not be trusted over them.