Repository navigation
fix(registry): describe all three product lines and x402 in server.json - #7
Merged
Merged
Conversation
The MCP Registry entry io.github.virtualsms-io/sms is metadata-correct (version 1.3.1, correct npm + HTTP transport) but its description only named SMS verification and rentals - it omitted proxies and x402 entirely. This description propagates verbatim to every directory that syndicates from the registry (mcpindex.ai, mcp-marketplace.io), so it is the cheapest available fix for those two. Also updated package.json's description, which is the same stale text and drives the npmjs.com listing page directly. Commit-Author: sub-agent Task-Source: /tmp/brief-stale-18.md (dispatched) Reason: registry/npm description undersells two of three product lines and the x402 payment path; propagates to every directory that mirrors registry metadata verbatim.
virtualsms-io
added a commit
that referenced
this pull request
Sep 7, 2026
Bumps server.json's root version to 1.3.2 to release the already-merged registry description fix (#7) to the MCP Registry listing. packages[0].version stays at 1.3.1 deliberately: the registry does not require server.json's root version to equal packages[].version, this is an officially documented pattern ("Use Prerelease Versions for Registry-only Updates"), and no npm publish is needed since the published 1.3.1 package is unchanged. Commit-Author: sub-agent Task-Source: user-prompt Reason: Ship the registry listing description fix as a registry-only version bump without republishing the npm package, per the registry's documented registry-only-update pattern.
virtualsms-io
added a commit
that referenced
this pull request
Sep 7, 2026
* chore(release): registry-only bump to 1.3.2 Bumps server.json's root version to 1.3.2 to release the already-merged registry description fix (#7) to the MCP Registry listing. packages[0].version stays at 1.3.1 deliberately: the registry does not require server.json's root version to equal packages[].version, this is an officially documented pattern ("Use Prerelease Versions for Registry-only Updates"), and no npm publish is needed since the published 1.3.1 package is unchanged. Commit-Author: sub-agent Task-Source: user-prompt Reason: Ship the registry listing description fix as a registry-only version bump without republishing the npm package, per the registry's documented registry-only-update pattern. * chore(registry): describe Cloud Browser sessions in the server description Commit-Author: claude-main Task-Source: user-prompt Reason: operator-approved final description text must cover all four product lines (SMS, rentals, proxy, Cloud Browser) plus x402 before the 1.3.2 registry publish. --------- Co-authored-by: VirtualSMS <265610251+virtualsms-io@users.noreply.github.com>
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
2 participants
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
server.json's description (the MCP Registry entryio.github.virtualsms-io/sms) only named SMS verification and rentals — it omitted proxies and x402 entirely, even though the registry metadata is otherwise correct (version 1.3.1, correct npm + HTTP transport).package.json'sdescriptionfield carried the identical stale text and drives the npmjs.com listing page directly — updated for consistency.NOT done — needs an operator-approved release action
This PR only changes the file. Getting the new description live requires a publish action, which I have not taken:
.github/workflows/publish-mcp-registry.ymlfires on a GitHubrelease: publishedevent or a manualworkflow_dispatch. Sinceserver.json'sversionis already1.3.1(matching what's already published), aworkflow_dispatchrun againstmainafter this merges should be enough to re-publish metadata — but I have not verified whether the MCP Registry's publisher allows republishing the same version's metadata versus requiring a version bump. Someone needs to either confirm that or bump to 1.3.2 before triggering it.package.json's description only reaches npmjs.com on a freshnpm publish, i.e. a version bump (1.3.1→1.3.2) and a real release. Not something to do without explicit approval.Report back to the operator: this PR is safe to merge on its own (it only edits two description strings, guard-clean), but publishing it live needs one of the two actions above, explicitly chosen.
Verify
bash scripts/check-positioning.sh→OK - no banned copy in tracked files(38 rules, mixed-content profile).noticket/ — Linear is at its free-plan issue cap, no ticket could be created (expected per brief).