feat: add publishing to the official MCP registry - #28
Merged
Conversation
Resolves the high-severity Dependabot alert (https://github.com/kujenga/zotero-mcp/security/dependabot/4) for a Bleichenbacher oracle in PKCS#7 EnvelopedData decryption, affecting cryptography >= 44.0.0, < 50.0.0: GHSA-g6cj-pr64-35w5 cryptography is a transitive dependency (mcp -> pyjwt[crypto] -> cryptography), so only uv.lock changes, upgraded with: uv lock --upgrade-package cryptography Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Patch release to get the MCP registry ownership marker into the README rendered on PyPI, which the registry validates against server.json. Also ships the cryptography upgrade for GHSA-g6cj-pr64-35w5 from the previous commit. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Registers this server as io.github.kujenga/zotero-mcp in the official registry (https://github.com/modelcontextprotocol/registry), the upstream source for aggregators like Glama and PulseMCP as well as MCP clients that browse it directly. Also disambiguates this project from io.github.54yyyu/zotero-mcp, an unrelated server with the same name that is already listed there. PyPI packages verify ownership differently from npm: instead of an mcpName field in package.json, the registry looks for an 'mcp-name: <server name>' marker in the README as rendered on PyPI, so publishing 0.3.1 to PyPI must precede the first registry publish. See https://modelcontextprotocol.io/registry/package-types for the marker format and boundary rules. The GHCR Docker image is deliberately not listed as a package yet: OCI validation requires an io.modelcontextprotocol.server.name LABEL baked into a version-pinned image, and the current workflow only tags branch-based images (:main). This can be added once versioned image tags are published. server.json validates against the 2025-12-11 schema via: uvx check-jsonschema --schemafile \ https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json \ server.json Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
kujenga
force-pushed
the
at/mcp-registry
branch
from
August 7, 2026 03:16
531a557 to
9f6b277
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The official MCP registry is the upstream metadata source for MCP server discovery — aggregators like Glama and PulseMCP pull from it, and MCP clients increasingly browse it directly. This project isn't listed there yet, while an unrelated server with the same name (
io.github.54yyyu/zotero-mcp, PyPI packagezotero-mcp-server) already is. Publishing asio.github.kujenga/zotero-mcpclaims our namespace, disambiguates the two projects, and gets discoverability everywhere downstream from a single publish.What changed
Everything needed to publish, minus the publish itself: the
server.jsonmetadata file, the PyPI ownership marker in the README, amake publish-mcptarget, release-steps docs, and a version bump to 0.3.1. The branch also leads with a security fix so it rides along in the 0.3.1 release: an upgrade of the transitivecryptographydependency to 50.0.0, resolving the high-severity Dependabot alert GHSA-g6cj-pr64-35w5 (Bleichenbacher oracle in PKCS#7 decryption; pulled in viamcp → pyjwt[crypto], so onlyuv.lockchanges). See commits for review.Two decisions worth flagging:
mcp-name:marker in the README as rendered on PyPI againstserver.json(package-types docs). That's why this includes a version bump — the marker only becomes visible to the registry once 0.3.1 is on PyPI.io.modelcontextprotocol.server.nameLABEL baked into a version-pinned image, and our workflow currently only pushes branch-tagged images (:main). Follow-up once versioned image tags exist.Validation
server.jsonvalidates against the official 2025-12-11 schema:uvx check-jsonschema --schemafile https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json server.jsonDeploy notes
After merging, going live is manual (also documented in the new README "Releasing" section):
make publish(PyPI first — the registry checks the marker on the 0.3.1 PyPI page)mcp-publisher login github(one-time;brew install mcp-publisher)make publish-mcpNote the registry is still in preview — breaking changes or data resets may occur before GA, in which case a re-publish may be needed.
🤖 Generated with Claude Code