Is the io.github.varvararatta/legal_mcp MCP server working?

Is the io.github.varvararatta/legal_mcp MCP server working?

No, not as the registry describes it. 8 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-4250, ERR-2026-4254, ERR-2026-4255, ERR-2026-4257, ERR-2026-4266, ERR-2026-4272, ERR-2026-4273, ERR-2026-4278

Why can't I reach the io.github.varvararatta/legal_mcp API?

Its declared address answered neither a request nor a TLS handshake on 2026-09-17, across 26 cases. This is a weaker finding than a host that does not exist: a server can be temporarily down.

ERR-2026-4251, ERR-2026-4252, ERR-2026-4253, ERR-2026-4256, ERR-2026-4258, ERR-2026-4259, ERR-2026-4260, ERR-2026-4261, ERR-2026-4262, ERR-2026-4263, ERR-2026-4264, ERR-2026-4265

Every record behind those answers

34 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.

server error (15)

The declared origin answered with a server error.

Check it yourself:

curl -s -X POST https://crypto-prices-mcp.mcpize.run/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"}}}'

the host cannot be reached (11)

The declared document or endpoint could not be reached.

Check it yourself:

curl -s -X POST https://country_data_mcp.mcpize.run/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"}}}'

the endpoint does not speak MCP correctly (8)

The declared endpoint answers, but rejects the MCP initialize handshake or replies outside the protocol.

Check it yourself:

curl -s -X POST https://air-quality-mcp.mcpize.run/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.varvararatta, io.github.varvararatta/air_quality_mcp, io.github.varvararatta/country_data_mcp, io.github.varvararatta/crypto_prices_mcp, io.github.varvararatta/currency_converter_mcp, io.github.varvararatta/dictionary_lexicon_mcp, io.github.varvararatta/ecommerce_mcp, io.github.varvararatta/education_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.