Is the io.github.fujimura-ui MCP server working?

Is the io.github.fujimura-ui MCP server working?

No, not as the registry describes it. 18 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-3500, ERR-2026-3501, ERR-2026-3502, ERR-2026-3503, ERR-2026-3504, ERR-2026-3505, ERR-2026-3506, ERR-2026-3507, ERR-2026-3508, ERR-2026-3509, ERR-2026-3510, ERR-2026-3511

Every record behind those answers

18 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 (18)

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

ERR-2026-3500https://jusho-mcp.plus-synergy.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3501https://jusho-mcp.plus-synergy.workers.dev/sseinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3502https://gbiz-leads-mcp.plus-synergy.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3503https://gbiz-leads-mcp.plus-synergy.workers.dev/sseinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3504https://edinet-mcp.plus-synergy.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3505https://edinet-mcp.plus-synergy.workers.dev/sseinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3506https://horei-mcp.plus-synergy.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3507https://horei-mcp.plus-synergy.workers.dev/sseinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3508https://estat-mcp.plus-synergy.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3509https://estat-mcp.plus-synergy.workers.dev/sseinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3510https://kokkai-mcp.plus-synergy.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3511https://kokkai-mcp.plus-synergy.workers.dev/sseinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3512https://fudousan-mcp.plus-synergy.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3513https://fudousan-mcp.plus-synergy.workers.dev/sseinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3514https://hojokin-mcp.plus-synergy.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3515https://hojokin-mcp.plus-synergy.workers.dev/sseinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3516https://tenki-mcp.plus-synergy.workers.dev/mcpinitialize returned HTTP 404checked 2026-09-17
ERR-2026-3517https://tenki-mcp.plus-synergy.workers.dev/sseinitialize returned HTTP 404checked 2026-09-17

Check it yourself:

curl -s -X POST https://jusho-mcp.plus-synergy.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.fujimura-ui/japan-address-geocoding-mcp, io.github.fujimura-ui/japan-company-leads-mcp, io.github.fujimura-ui/japan-corporate-filings-mcp, io.github.fujimura-ui/japan-law-search-mcp, io.github.fujimura-ui/japan-official-statistics-mcp, io.github.fujimura-ui/japan-parliament-search-mcp, io.github.fujimura-ui/japan-real-estate-mcp, io.github.fujimura-ui/japan-subsidy-search-mcp. 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.