jeonjw85/kenfold is a self-hosted memory server that lets Claude Code, Codex, OpenCode, and ChatGPT share memory over the MCP protocol. The merge commit 44d84be (PR #6) on 2026-10-21 prepares for submission to the official MCP Registry. It newly creates a root server.json, adds the ownership label io.modelcontextprotocol.server.name to the Dockerfile, and adds a 151-line docs/mcp-registry.md, with the English and Korean READMEs pointing to that document. 168 lines were added across 5 files, and no lines were deleted. The Go code, database schema, authentication policy, and network exposure scope were left unchanged.
The Registry is a catalog that holds only metadata about MCP servers. The current schema (2025-12-11) does not require packages or remotes, and the official validation tool likewise allows their absence. The prepared server.json passed at the official POST /v0.1/validate endpoint on 2026-10-20 with {"valid":true,"issues":[]}, and the version in the metadata uses the existing latest release 0.1.2 as-is rather than a newly created value. The document records, on that basis, that the server is tied to MCP Go SDK v1.8.0, offers streamable-http transport at the /mcp path, and uses per-agent Bearer keys and optional OAuth (PKCE S256). It also lays out, step by step, the procedure for attaching a packages entry so that the listing becomes an automatically installable one once a public OCI image is uploaded.
That said, passing validation is not publication. It is not confirmation of namespace ownership, not protocol authentication, and not a guarantee of catalog exposure. Because the v0.1.2 GitHub release has no attached assets and this repository points to neither a public image nor a hosted address that is in operation, packages and remotes were left empty. The release notes also state that actual connections to ChatGPT and claude.ai have not yet been verified. The benchmark status given in the README is likewise incomplete. The most recent scoring run left only partial results for 1,402/1,540 items of raw-LoCoMo and was then stopped because the API usage could not be checked, and extraction-LoCoMo and LongMemEval QA were not scored. Official registry listing is only a starting point and does not by itself prove ease of installation or performance. Until the OCI image is published, the packages entry is filled in, and client connection verification is added, it is better to treat this as one visible point of reference.