[OCI] Submit OCI to all major MCP registries (Smithery, mcp.so, PulseMCP, Manufact, official)

[DevanshuNEU]

Why this exists

OCI is not present on any public MCP registry. Verified absent on Smithery (~2,000 servers), mcp.so (~19,000 servers), PulseMCP, Manufact (manufact.com/servers), and the Official MCP Registry at registry.modelcontextprotocol.io. The repo contains no `smithery.yaml`, no `server.json`, no `.well-known/` manifest.

Strategy v0.2.1 Move 1 ("canonical open-source code-intelligence MCP server", the shadcn-play) and locked belief #2 ("$0 install is the discovery vector") both depend on registry discoverability. With zero presence, organic install via `smithery mcp add codeintel` or registry browsing is structurally impossible.

Source: static audit + web search 2026-05-13. Logged as dogfood finding F-013 in DevVault.

What ships

• Add `smithery.yaml` to repo root (Smithery schema; declares stdio transport, entry point, env requirements)
• Add `server.json` to repo root (official MCP registry schema per registry.modelcontextprotocol.io)
• Submit OCI to Smithery via `smithery mcp publish` or registry web form
• Submit OCI to mcp.so via the community-driven submission form
• Submit OCI to PulseMCP
• Submit OCI to Manufact (manufact.com)
• Submit OCI to the Official MCP Registry (modelcontextprotocol/registry PR)
• Add a "Install from registry" section to README pointing to all 5 channels

Acceptance criteria

• `smithery.yaml` and `server.json` exist at repo root and pass schema validation
• OCI appears in search results on at least 3 of the 5 registries within 1 week of submission
• README has a "Install" section with `npx` / `smithery mcp add` / `pipx` invocation lines
• At least one cold install attempted from a registry (verified working end-to-end)

Wave

pre-thesis (Move 1 enabler; ships before 2026-06-22 validation gate)

Type

feat

Stack scope

• mcp-server
• cross-cutting (docs / registry artifacts / vault)

Priority

high

ADR required

yes - see `oci/decisions/2026-05-13-local-mode-v0.1.md` (LOCAL_MODE Option C produces the registry-installable artifact this issue depends on)

Dogfooding signal

yes - audit finding F-013 from 2026-05-13 dogfood audit session. Static-audit category (not tool-friction).

Related

• Wave: pre-thesis, Move 1 (positioning)
• Prior ADRs: `oci/decisions/2026-05-13-local-mode-v0.1.md` (LOCAL_MODE)
• Linked: #TBD (LOCAL_MODE issue, filed alongside)
• External: Smithery docs, Official MCP Registry, Manufact servers
• Blocked by: LOCAL_MODE (registries expect zero-config installs)

---

Filed from OCI audit 2026-05-13. Full context: `oci/dogfood-findings.md` F-013.