This page explains Provenote’s current public distribution status without blurring package readiness, public discoverability, and official listing status.
In plain language: a public GitHub repo can already ship real starter bundles and real proof loops before every external listing goes live. Provenote now also has a live Official MCP Registry entry for provenote-mcp, while the rest of the host-specific marketplace lanes remain separate questions.
If you want the machine-readable packet inventory behind the host bundle story, start with ../examples/hosts/packet-index.json. That index points at the per-bundle manifest.yaml files while this page stays focused on claim levels and listing truth.
| Level | What it means | What it does not mean |
|---|---|---|
repo-owned prep exists |
the repo contains setup pages, starter files, sample config, or proof notes | public-ready package, public listing, or official marketplace status |
public-ready package available |
a public visitor can follow public docs, copy a public starter bundle, and run the documented verify loop | official marketplace listing, official directory inclusion, or platform endorsement |
publicly discoverable listing live |
the package or server is already visible in a public registry, directory, or marketplace surface | official partnership, endorsement, or automatic support guarantees |
official marketplace listing live |
the official platform listing is publicly visible and live | anything stronger than the platform actually says |
| Surface | Official public surface exists? | Public submission path verified? | Current repo-owned artifact | Current claim level | Official listing live? | Remaining blocker |
|---|---|---|---|---|---|---|
| Claude Code | yes, official Claude Code MCP docs exist and Anthropic documents a discovery surface plus official marketplace submission flows | yes, official marketplace/discovery docs and submission forms are documented | ../examples/hosts/claude-code/provenote-outcome-bundle/README.md, ../examples/hosts/claude-code/DIRECTORY_SUBMISSION.md, and integrations/claude-code.md | public-ready package available |
no | authenticated Anthropic marketplace submission plus directory review and any extra publisher-side materials Anthropic requires |
| OpenAI Codex | yes, official Codex MCP docs exist | no verified official listing flow was confirmed in this turn | ../examples/hosts/codex/provenote-outcome-bundle/README.md, ../examples/hosts/codex/PLUGIN_DIRECTORY_SUBMISSION.md, and integrations/codex.md | public-ready package available |
no | wait for OpenAI to expose or document an official listing path before claiming more |
| OpenClaw / ClawHub | yes | yes | ../examples/hosts/openclaw/README.md, ../examples/hosts/openclaw/CLAWHUB_SUBMISSION.md, ../examples/hosts/openclaw/clawhub/provenote-mcp-outcome-workflows/SKILL.md, and integrations/openclaw.md | public-ready package available |
no | authenticated ClawHub publish under a valid account and namespace |
| Official MCP Registry | yes | yes | ../examples/public-distribution/mcp-registry/README.md, ../examples/public-distribution/mcp-registry/PUBLISHABLE_ARTIFACT.md, ../examples/public-distribution/mcp-registry/server.json, mcp.md, and ../pyproject.toml | official marketplace listing live |
yes | package-backed install artifact upgrades remain optional follow-up work |
provenote-mcp.mcp.jsonprovenote-mcp.mcp.jsonThe official MCP Registry already exists and its docs include a publish quickstart plus a server.json reference that supports custom installation paths via websiteUrl.
The current repo now keeps the canonical submission metadata in ../examples/public-distribution/mcp-registry/server.json and mirrors the same registry-facing identity in server.json, both pointing at the first-party install docs in mcp.md.
Fresh registry read-back now returns:
io.github.xiaojiou176-open/provenote-mcpactive1.8.5That means the honest current level is now:
For that later packaging upgrade, the official registry requirements and the quickstart’s package-backed publish path still matter. They are no longer evidence that the current live entry is absent; they are evidence for what a future richer install surface would still need.
Said another way: registry-specific publication is still blocked by external publish/auth work when the goal changes from today’s live websiteUrl-backed entry to a richer package-backed install surface.
The repo now has a reusable promotion foundation, but not a complete promotion kit yet.
Current tracked assets include:
Those assets already support README framing, proof storytelling, and social-preview upload.
They still do not add up to a full promotion pack by themselves. A stronger promotion-ready state also needs:
Use promotion-kit.md for the tracked copy starters, asset inventory, and short demo storyboard.
This page does not claim:
