Give the registry record a title, so directories stop calling us GetAnyAPI - #2
Merged
Conversation
…nyAPI Directory listings that ingest from the MCP Registry synthesize a display name from the reverse-DNS name when `title` is absent, which is why PulseMCP shows "GetAnyAPI" and LobeHub shows "Anyapi". One missing field, two wrong names. Adds "title": "AnyAPI" and bumps 0.1.3 -> 0.1.4 across server.json, its npm and OCI pins, package.json and the lockfile so the three stay consistent. Reaching the registry needs a v0.1.4 tag; publish.yml owns that path. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
kev1n
added a commit
that referenced
this pull request
Sep 6, 2026
) The registry is append-only and v0.1.4 was tagged and published before #2 merged, so the live latest record carries the keyless-tools wording but no title and directories still synthesize "GetAnyAPI" from the server name. Only a new version can carry the title, so bump every pin. 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.
Why
PulseMCP renders our listing GetAnyAPI and LobeHub renders it Anyapi. Neither is a data-entry mistake on their side: our registry record omits the optional
titlefield, so every directory that ingests from the MCP Registry synthesizes a display name out of the reverse-DNSname,io.github.getanyapi-com/anyapi. Both strings are that name run through a different formatter.The 2025-12-11 server schema defines
titleas "Optional human-readable title or display name for the MCP server. MCP subregistries or clients MAY choose to use this for display purposes."MAYis the honest word - this is the only lever at the source, not a guarantee any given directory re-reads it. It is still the fix to try before writing to anyone, because it corrects every registry-fed listing at once instead of one at a time.Checked first: neither PulseMCP nor mcpmarket.com has any owner edit, claim or report control, and PulseMCP froze all listing changes on 2026-09-03 ("we are not making changes to existing listings"), pointing submitters at the Official MCP Registry in the meantime. So there was no per-directory path even in principle.
What changed
server.jsongains"title": "AnyAPI", and the version goes 0.1.3 -> 0.1.4 acrossserver.json, its npm and OCI package pins,package.jsonand the lockfile, so the three stay consistent.Shipping
This needs a
v0.1.4tag to reach the registry -publish.ymlruns npm, then ghcr, thenmcp-publisherover OIDC, in that order, because the registry verifies the artifacts before it stores the metadata.Proof
npm run check-> 13 tests, 0 failures.server.jsonparses and matches the published 0.1.3 record apart from the title and the version bumps.🤖 Generated with Claude Code