Skip to content

Add official MCP Registry listing and OIDC publishing - #29

Open
vprudnikoff wants to merge 2 commits into
mainfrom
chore/mcp-registry-listings
Open

vprudnikoff wants to merge 2 commits into
mainfrom
chore/mcp-registry-listings

Conversation

@vprudnikoff

@vprudnikoff vprudnikoff commented Oct 29, 2026 •

Copy link
Copy Markdown
Member

The official MCP Registry has no Linked API entry. Add server.json for the npm stdio server and the hosted HTTP endpoint, with both token inputs marked as secrets. The npm metadata now declares the matching mcpName; version 2.3.21 contains no runtime source changes.

A tag-triggered GitHub Actions workflow publishes the package when needed, waits for public npm metadata and verifies its mcpName, then publishes the registry entry using GitHub OIDC. The publisher is pinned to v1.8.1 and its Sigstore bundle is verified before execution. Registry versions follow package.json. This workflow does not invoke the hosted-server deployment.

Validation: repository formatter, ESLint, typecheck and build passed; new metadata/workflow files pass Prettier; server.json passes the official JSON schema; local stdio and hosted HTTP initialize/tools-list checks both expose 68 tools; npm pack dry run includes server.json. Code style review passed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant