Update upstream MCP registry schema to v1.3.3 (2025-10-17) #2278
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.
Summary
Updates
pkg/registry/upstream.goandpkg/registry/upstream_conversion.goto match the latest MCP community registry schema format (v1.3.3, 2025-10-17 schema version).Major Schema Changes
Structure Changes
Serverobject; fields likeName,Description,Versionare now directly onUpstreamServerDetailx-publisher.x-dev.toolhiveto_metawith reverse DNS namespacingNew Fields
Schema($schema) for JSON Schema URITitlefor human-readable display nameWebsiteURLfor documentation linksIconsarray for UI displaySubfolderin repository for monorepo supportRegistryBaseURLandIdentifierin packagesFileSha256for MCPB package integrity verificationPackage Type Support
@scope/name@version)[email protected])dnx://protocolBug Fixes
npx://[email protected])Operator Integration
Updated the Kubernetes operator integration:
cmd/thv-operator/pkg/sources/types.go- Uses new flattened structurecmd/thv-operator/pkg/sources/testutils.go- Updated test buildersTesting
pkg/registry/...andcmd/thv-operator/pkg/sources/...)References
🤖 Generated with Claude Code