No, not as the registry describes it. 2 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-3659, ERR-2026-4238
4 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 package registry marks the exact version this entry declares as deprecated.
ERR-2026-4890 | https://registry.npmjs.org/@khalidsaidi/a2abench-mcp | npm marks @khalidsaidi/a2abench-mcp@1.0.1 deprecated: The ho | checked 2026-09-17 |
ERR-2026-4891 | https://registry.npmjs.org/@khalidsaidi/ragmap-mcp | npm marks @khalidsaidi/ragmap-mcp@1.0.1 deprecated: The host | checked 2026-09-17 |
Check it yourself:
curl -sS -o /dev/null -w '%{http_code}\n' https://registry.npmjs.org/@khalidsaidi/a2abench-mcp
The endpoint this registry entry declares returns 404 or 410 to the MCP initialize handshake.
ERR-2026-3659 | https://a2abench-mcp.web.app/mcp | initialize returned HTTP 404 | checked 2026-09-17 |
Check it yourself:
curl -s -X POST https://a2abench-mcp.web.app/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 declared endpoint answers, but rejects the MCP initialize handshake or replies outside the protocol.
ERR-2026-4238 | https://gmca-researchapp.web.app/mcp | response is not valid JSON: Expecting value: line 1 column 1 | checked 2026-09-17 |
Check it yourself:
curl -s -X POST https://gmca-researchapp.web.app/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.khalidsaidi, io.github.khalidsaidi/a2abench, io.github.tridevils, io.github.tridevils/gmca-certainty-matrix-validate. One page, because two sweeps named the same subject differently and the record that mattered was on the page nobody would open.
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.
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.
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.