Say the four catalog tools are keyless, and release it - #1
Merged
Conversation
The hosted server now answers a credential-free tools/call for list_apis, search_apis, get_api and quote_api (getanyapi-com/anyapi#1041). This repo published the opposite this morning in 0.1.3, in the README and in all three ANYAPI_API_KEY descriptions inside server.json, and the MCP Registry republishes that file to every aggregator that reads it - so the correction only reaches those aggregators through a release. run_api and the account tools are unchanged and still 401 without a key. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.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
1 participant
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.
What changed
The hosted server now answers a credential-free
tools/callforlist_apis,search_apis,get_apiandquote_api(getanyapi-com/anyapi#1041). This repo published the opposite this morning in 0.1.3 - in the README and in all threeANYAPI_API_KEYdescriptions insideserver.json.server.jsonis the file the MCP Registry republishes to every aggregator that reads it, so the correction only reaches them through a release. Hence the 0.1.4 bump rather than a docs-only edit.What is unchanged
run_apiand the account tools still return 401 without a key. The proxy declares no tool of its own and forwards everything, so nothing about its behaviour changes here - only what it says about the server it forwards to.Proof
npm run checkpasses, 13/13, including the two assertions that would catch a half-done version bump: "server.json names the version this package actually publishes" and "the reported version is the published one, not a second copy".package.json,package-lock.jsonand all threeserver.jsonversion fields (plus the GHCR image tag) are at 0.1.4.Merge and tag
v0.1.4only after anyapi#1041 is live, so the sentence is true when the registry republishes it.🤖 Generated with Claude Code