mcptoon: replace the unpublished @modelcontextprotocol/server-fetch example - #127
Open
activeing123 wants to merge 1 commit into
Open
activeing123 wants to merge 1 commit into
activeing123 wants to merge 1 commit into
Conversation
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
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.
The
mcptoonpage's first example installs a package that no longer exists on npm:Checked against the registry today:
registry.npmjs.org/@modelcontextprotocol%2Fserver-fetch→ 404 (unpublished)registry.npmjs.org/@modelcontextprotocol%2Fserver-everything→ 200 (published)So anyone copying that line gets an
npm error 404before they ever reach the tool. This patch points both examples at the package that actually exists, keeping the file's existing bracket-placeholder style:Full disclosure: I maintain
mcptoon, so I have an interest in the page being accurate — but the two commands above are simply the ones documented in the project README, which is what the page should mirror. The<!-- verified: -->stamp and everything else in the file are untouched.