chore: MCP Registry manifest and bump version to 0.7.9#31
Conversation
Adds server.json (io.github.block/model-ledger, schema 2025-12-11) pointing MCP clients at 'uvx --from model-ledger[mcp,cli] model-ledger mcp', and the hidden mcp-name ownership marker the registry checks in the PyPI package description. The marker must ship in a PyPI release before the registry publish can validate ownership, hence the bump. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Vignesh Narayanaswamy <Vigneshn@squareup.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5dc720fc39
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json", | ||
| "name": "io.github.block/model-ledger", | ||
| "title": "Model Ledger", | ||
| "description": "Model inventory and governance: discover, query, and trace deployed models and their dependency graph as an append-only event log", |
There was a problem hiding this comment.
Shorten registry description to satisfy schema
The server.json manifest won't validate against the referenced 2025-12-11 MCP server schema because ServerDetail.description is capped at 100 characters, but this description is 129 characters. In the registry publishing path, that means the new 0.7.9 metadata is rejected before package ownership verification can succeed, so the release cannot be published to the official MCP Registry until this is shortened.
Useful? React with 👍 / 👎.
Adds
server.jsonfor the official MCP Registry (io.github.block/model-ledger) and the hiddenmcp-nameownership marker to the README — the registry validates PyPI package ownership by finding that marker in the package description, so it needs to ship in a release before publishing.Clients will launch the server as
uvx --from "model-ledger[mcp,cli]==0.7.9" model-ledger mcp(extras are required because the MCP and CLI dependencies are optional).🤖 Generated with Claude Code