No, not at the address its own documentation gives. The host declared as its server did not resolve in DNS on 2026-09-17, across 2 indexed operations. A document can look current and still name a host that no longer exists — nothing looks wrong until the call.
ERR-2026-4466, ERR-2026-4470
No, not as the registry describes it. 1 declared endpoint 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-4465
6 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 declared origin answered with a server error.
ERR-2026-4467 | https://legal.memoryapi.org/mcp | initialize returned HTTP 502 | checked 2026-09-17 |
ERR-2026-4468 | https://nasa.memoryapi.org/mcp | initialize returned HTTP 502 | checked 2026-09-17 |
ERR-2026-4469 | https://news.memoryapi.org/mcp | initialize returned HTTP 502 | checked 2026-09-17 |
Check it yourself:
curl -s -X POST https://legal.memoryapi.org/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 of the declared document or endpoint no longer resolves in DNS.
ERR-2026-4466 | https://contracts.memoryapi.org/mcp | DNS failure for contracts.memoryapi.org: [Errno -2] Name or | checked 2026-09-17 |
ERR-2026-4470 | https://rep.memoryapi.org/mcp | DNS failure for rep.memoryapi.org: [Errno -2] Name or servic | checked 2026-09-17 |
Check it yourself:
curl -s -X POST https://contracts.memoryapi.org/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 this registry entry declares returns 404 or 410 to the MCP initialize handshake.
ERR-2026-4465 | https://arb.memoryapi.org/mcp | initialize returned HTTP 404 | checked 2026-09-17 |
Check it yourself:
curl -s -X POST https://arb.memoryapi.org/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: org.memoryapi, org.memoryapi/contracts, org.memoryapi/legal, org.memoryapi/nasa, org.memoryapi/news, org.memoryapi/rep. 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.