Is the io.github.srotzin/hivelaw MCP server working?

Is the io.github.srotzin/hivelaw MCP server working?

No, not as the registry describes it. 42 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-4130, ERR-2026-4131, ERR-2026-4132, ERR-2026-4133, ERR-2026-4134, ERR-2026-4135, ERR-2026-4136, ERR-2026-4137, ERR-2026-4138, ERR-2026-4139, ERR-2026-4140, ERR-2026-4141

Every record behind those answers

42 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 (41)

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

Check it yourself:

curl -s -X POST https://hive-execute.onrender.com/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 rejects a mandatory part of the handshake (1)

The declared endpoint accepts initialize but rejects the mandatory notifications/initialized that follows it, with HTTP 400. A client following the specification breaks here.

Check it yourself:

curl -s -X POST https://hiveclear.onrender.com/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.srotzin, io.github.srotzin/hive-execute, io.github.srotzin/hive-mcp-abtest, io.github.srotzin/hive-mcp-address-screen, io.github.srotzin/hive-mcp-agent-kyc, io.github.srotzin/hive-mcp-agent-quota, io.github.srotzin/hive-mcp-agent-storage, io.github.srotzin/hive-mcp-aml-screen. 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.