othervibes/Publish MCP Server

Publish an MCP server to the official MCP Registry using the MCP Publisher CLI.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
nameServer name in reverse-DNS format. Must contain exactly one forward slash separating namespace from server name.yes
descriptionClear human-readable explanation of server functionality. Should focus on capabilities, not implementation details.yes
versionVersion string for this server. SHOULD follow semantic versioning (e.g., "1.0.2", "2.1.0-alpha"). Non-semantic versions are allowed but may not sort predictably.yes
website_urlOptional URL to the server homepage, documentation, or project website. Provides a central link for users to learn more about the server.no
registry_typeRegistry type indicating how to download packages.yes
identifierPackage identifier - either a package name (for registries) or URL (for direct downloads).yes
package_versionPackage version. Must be a specific version. Version ranges are rejected. Defaults to top-level version when omitted.no
transport_typeTransport type for the package.yes
transport_urlTransport URL (required for streamable-http and sse transports).no
registry_base_urlBase URL of the package registry.no
file_sha256SHA-256 hash of the package file for integrity verification. Required for MCPB packages and optional for other package types.no
statusServer lifecycle status. 'deprecated' indicates the server is no longer recommended for new usage. 'deleted' indicates the server should never be installed and existing installations should be uninstalled.noactive
registry_urlRegistry base URL for publishing and verification.nohttps://registry.modelcontextprotocol.io
verifyWhen true, validates the published version is visible in the registry.notrue
namedescription
versionPublished version.
server_namePublished server identifier.
server_jsonFull server definition JSON used for publication.