Repository navigation
chore: list the hosted HyperFrames MCP in the official MCP registry - #6408
Conversation
Adds server.json for registry.modelcontextprotocol.io under the io.github.heygen-com namespace, pointing at HeyGen's hosted server. Today the registry lists only a third-party paid clone.
jrusso1020
left a comment
jrusso1020
left a comment
There was a problem hiding this comment.
We validated server.json against the 2025-12-11 schema and checked the production route's Streamable HTTP setup plus public OAuth discovery. No JSON defect found. Please correct the publication instructions inline. Publishing needs James's explicit go, then an eligible heygen-com org Owner must run mcp-publisher. Authenticated tools and publication were not exercised.
| @@ -0,0 +1,18 @@ | |||
| { | |||
| "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json", | |||
| "name": "io.github.heygen-com/hyperframes", | |||
There was a problem hiding this comment.
The namespace is appropriate, but the PR body overstates who can publish and how. Current official registry authentication docs require a GitHub organization Owner, not ordinary membership. They also say plain interactive mcp-publisher login github currently cannot grant organization namespaces, even to Owners. Correct the manual plan to use an eligible Owner with appropriately scoped PAT authentication, or an authorized GitHub Actions OIDC path. After James's explicit go, a qualified org Owner should run the manual publisher from the repository root. Merging this file alone does not publish the entry.
There was a problem hiding this comment.
Right, thanks. Checked against the auth docs and #1468: the description now says merging doesn't publish, publishing waits for James's go, and a heygen-com org Owner runs mcp-publisher login github --token <PAT> (read:org, or fine-grained Members read-only) then mcp-publisher publish, or we add the OIDC workflow later. The ordinary-member claim is gone.
jrusso1020
left a comment
jrusso1020
left a comment
There was a problem hiding this comment.
We checked the updated description at the unchanged head. It now specifies James's go, the org-Owner PAT path and OIDC alternative, and the interactive-login limitation. Our earlier publication-instructions note is resolved. No authenticated MCP calls or publication were performed.
jrusso1020
left a comment
jrusso1020
left a comment
There was a problem hiding this comment.
We rechecked the unchanged head and corrected description. The earlier schema, hosted transport and public OAuth-discovery review still applies; the org-Owner publishing note is resolved. No blocker found. Authenticated tools and registry publication were not exercised.
Need: yes · Size: minimal · Reuse: official MCP listing schema · Simpler: already minimal · Structure: fine
Verdict: APPROVE.
Reasoning: The listing metadata is correct; publication remains a separate action.
…identity metadata that the merge brought in npm homepage, the MCP registry server.json and the context7 claim name the upstream project. DECISIONS (2026-10-26) already says never adopt: the fork does not publish and must not register or claim on upstream's behalf. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
What
Adds
server.jsonat the repo root, the listing file for the official MCP registry (registry.modelcontextprotocol.io). It describes HeyGen's hosted HyperFrames server athttps://mcp.heygen.com/mcp/hyperframes/under the nameio.github.heygen-com/hyperframes.Why
Coding agents and MCP clients look servers up in the official registry, and directories like PulseMCP copy from it. Today searching "hyperframes" there returns only a third-party paid clone (
com.clauxel.hyperframesrender), so agents that look us up find someone else's server.How we'll know:
registry.modelcontextprotocol.io/v0/servers?search=hyperframesreturnsio.github.heygen-com/hyperframes.Related work
Part of the off-site listing clean-up, alongside the npm homepage (#6407) and an awesome-mcp-servers entry. The server itself is unchanged.
How
2025-12-11/server.schema.json). The description fits the 100-character limit.io.github.heygen-com/namespace can only be published by a heygen-com GitHub organization Owner (registry auth docs), so no one else can claim it.mcp-publisher login github --token <PAT>(classic PAT withread:org, or fine-grained with Organization → Members → Read-only; no repo scopes) andmcp-publisher publish. The interactivemcp-publisher login githubcan't grant org namespaces today (registry#1468). The other route is the registry's GitHub Actions OIDC workflow, which a later PR can add if we want every version bump published.Test plan
server.jsonvalidates against the registry schema (jsonschema, 2025-12-11)bun run lintandoxfmt --checkpass