Repository navigation
📌 Update, Oct 2026: how onboarding works (community notes)This thread became the place to request listing on github.com/mcp. These notes collect what's been said here. The process (based on the accepted answer, @trent-j, May 2026):
Include all of these in your request:
Check before you post (read the values from the registry, not from memory): Check whether you're already listed on GitHub's side: Community notes from this thread. Corrections welcome. Original question (Oct 2025): Hi community! Looking for clarification on how the GitHub MCP Registry works. Server: claude-faf-mcp Questions Is github.com/mcp a curated list (vs automatic sync)? Why We Ask Previously posted: modelcontextprotocol/registry #690 Thanks for any insights! 🙏 |
Replies: 316 comments 14 replies
|
39 days, no response. claude-faf-mcp is approved by Anthropic (PR #2759 MERGED), has 10,067+ npm downloads, but isn't visible on github.com/mcp despite being listed in modelcontextprotocol/servers. What are the curation criteria for github.com/mcp? Is there a separate approval process beyond the Anthropic PR? Links: |
|
🎉 Update: Additional Milestone Since Posting
This makes claude-faf-mcp:
Full details: https://www.faf.one/blog/iana-registration Still curious about the github.com/mcp curation process and happy to |
|
Hey @Wolfe-Jam, |
|
Hey HolgerMany thanks for your reply, we will take of it and let you know. thanks again,James (Wolfe) HarrisonFounderWolfe James LLCfaf.one - Project DNA for AI contextIANA Registered format .FAF for AI context application/vnd.faf+yaml"README evolution for AI era"Google Gemini CLI(9.5/10 Rating)
On Nov 10 2025, at 8:52 am, Holger Staudacher ***@***.***> wrote:
Hey @Wolfe-Jam,
right now the GitHub MCP registry is a curated list. This will change in a couple days when we enable sync with the open source registry. In order to get your server added, you have to publish it to the open source registry first. Here is a guide how to publish your server if you haven't done it already.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
|
Hey @hstaudacher - following up from November. Just published both FAF packages to the open source registry today:
Ready for sync whenever that goes live. If there's anything blocking the registry sync rollout, happy to help test, validate, or contribute. We've been through the mcp-publisher flow and can provide feedback if useful. |
|
Hey @hstaudacher — friendly follow-up from the November conversation about registry sync. Quick update on where things stand: we now have 6 FAF MCP servers published to the open source registry, all passing
All published via You mentioned back in November that github.com/mcp would start syncing from the open source registry. Is that sync live now? If so, is there something on our end we need to do to appear? If it's still in progress, totally understand — just want to make sure we're not missing a step. Happy to help test or validate anything on the sync pipeline. |
|
Status check, 2026-05-18: github.com/mcp still shows ~97 servers, so the open-source-registry sync doesn't look live yet. The FAF servers remain published & schema-clean on the OSS registry. If the list stays curated long-term: Is there an ETA for the sync, or is github.com/mcp staying curated? Either answer's fine — closing the loop on this thread. |
|
Hi @Wolfe-Jam, thanks for the thoughtful follow-up and for continuing to publish and validate your servers. A few clarifications from our side: the GitHub MCP Registry now has the ability to sync versions from the open source registry, but onboarding a new server is still a manual curation process today. Once a server has been onboarded, newly published versions from the OSS registry should sync from there. I’m closer to the technical side than the product/curation criteria, so I don’t want to overstate anything here. I’ll share your request with our product team and ask whether we’re able to move forward with onboarding them. Thanks again for your patience, and for offering to help validate the sync path. |
|
Hey @trent-j — thanks again for looking into this and for offering to take it to the product team, genuinely appreciate it. Quick update from our side: since May we've moved our two flagship servers to the FAF Foundation's DNS-verified No rush at all on the github.com/mcp side — mostly I'd love to understand the lay of the land so we can be ready: is onboarding/sync something that's moving, or staying curated for now? And if there's a process, criteria, or anything we should prep on our end to make it easy when the time comes, happy to do the legwork. Either way — thanks for keeping the channel open. 🙏 |
Onboarding request:
|
| Field | Value |
|---|---|
| Official registry name | io.github.edithatogo/fyi-mcp |
| Latest version | 0.1.2 (active / isLatest) |
| Repository | https://github.com/edithatogo/fyi-cli |
| server.json | https://github.com/edithatogo/fyi-cli/blob/master/server.json |
| Description | Local-first FOI/OIA request tracker MCP for Alaveteli platforms (FYI.org.nz and multi-jurisdiction catalog) |
OSS registry verification
curl -sS "https://registry.modelcontextprotocol.io/v0/servers?search=fyi-mcp"
returns io.github.edithatogo/fyi-mcp v0.1.2 active/latest.
github.com/mcp status (2026-07-09)
- Search
fyi-mcp/edithatogodoes not surface a curated card for this server https://github.com/mcp/io.github.edithatogo/fyi-mcp→ 404
Could the product/curation team please consider onboarding this server so OSS version sync can take effect? Happy to provide additional metadata or validation help.
Tracked in: edithatogo/fyi-cli#32
Onboarding request:
|
Onboarding request:
|
| Field | Value |
|---|---|
| Official Registry name | io.github.happy520ai/unified-ai-system |
| Latest version | 0.4.8 (active) |
| Package / transport | ghcr.io/happy520ai/unified-ai-system/mcp-server:0.4.8 / stdio |
| Repository | https://github.com/happy520ai/unified-ai-system |
| Manifest | https://github.com/happy520ai/unified-ai-system/blob/master/server.json |
| Documentation | https://happy520ai.github.io/unified-ai-system/codex-mcp-docker-quickstart.html |
Unified AI System is an Apache-2.0 self-hosted gateway that gives Codex, Cursor, Cline, and generic MCP clients nine bounded tools. Its differentiating first-run path turns rough natural-language requests into structured, reviewable prompts locally, with a deterministic fake provider and no account or API key required. Real provider calls remain explicit and disabled by default.
The repository publishes pinned OCI images and runs public CI, container, MCP discovery, security-scanner, clean-clone, and process-cleanup checks. The Official Registry currently contains versions 0.3.1 through 0.4.8; GitHub MCP search still returns no result.
Please consider onboarding this server so future Official Registry versions can sync. I am happy to provide any additional metadata or validation evidence the curation team needs.
|
Onboarding request: Following the OSS-registry-first process confirmed in this thread (publish to the open source registry, then request manual onboarding; versions sync after):
Derive gives agent output a permanent home. One call publishes a document, styled page, deck, or report to a versioned URL a teammate can open and comment on inline; the agent reads those comments back and revises. Every tool carries a title and honest Nothing to install and no key to paste — it is a remote server behind OAuth with dynamic client registration. Self-hosting is a single container, for teams that cannot send work to a hosted service. OSS registry verification: returns github.com/mcp status (2026-08-12): a search for Could the curation team consider onboarding this so future OSS registry versions sync automatically? Happy to provide any further metadata or validation. |
|
Onboarding request for a server already published to the OSS registry, following the format used earlier in this thread.
Happy to provide a populated test account for review. Thanks for considering. |
|
Requesting onboarding for a new server:
OSS registry verification: curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.rafaelgaspar/longhorn-mcp"returns the server with Publishing is automated via GitHub Actions OIDC on every tagged release ( |
|
Onboarding request: com.scandit/mcp Hi, I'm Akseli from Scandit! We'd like to request onboarding for the Scandit MCP server. It's already published and active in the Official MCP Registry. The server lets coding agents create a Scandit account, get trial license keys and set up the Scandit SDK in an app.
VerificationSecurity
To try it, connect the server and sign up for a free Scandit account during the OAuth flow. Repository
Happy to provide anything else you need. |
Onboarding request: Mail by Pony —
|
| Field | Value |
|---|---|
| Registry name | com.mailbypony/mail-by-pony (DNS-verified namespace) |
| Version / status | 0.3.0, active, isLatest: true (checked 26 October 2026) |
| Transport | Remote Streamable HTTP at https://www.mailbypony.com/mcp |
| Auth | OAuth 2.1 with protected-resource metadata (/.well-known/oauth-protected-resource) |
| Repository / license | Hosted service; source is not public. Terms |
| Docs | https://www.mailbypony.com/agents · Developer docs |
| Privacy / support | Privacy · Support |
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.mailbypony"
Thank you!
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | io.github.igrlk/uiverify (GitHub-verified namespace) |
| Version | 1.2.0, active, isLatest: true |
| Remote | Streamable HTTP at https://uiverify.ai/mcp, no package |
| Auth | OAuth 2.1 + PKCE (client ID metadata documents and dynamic client registration). No API key in the config; one sign-in reaches every project the user can access. |
| Tools | 15: 9 read-only (projects, builds, diffs, inline diff images, PR changesets, comments) and 6 that write (accept a diff or a build, post/update/resolve/delete a review comment) |
| Repository | https://github.com/uiverify/uiverify (CLI, capture SDKs, agent skills) |
| License | MIT |
| Docs | https://uiverify.ai/docs/triage-with-your-agent |
| Pricing | Free tier of 10,000 snapshots a month, 50,000 for open-source projects |
Tested in VS Code agent mode: install from the config below, sign in in the browser, then "list my UI Verify projects".
{ "servers": { "uiverify": { "type": "http", "url": "https://uiverify.ai/mcp" } } }Verify:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.igrlk/uiverify"
Thanks!
|
Requesting inclusion of StrataSpace in the GitHub MCP Registry.
|
Onboarding request:
|
| Field | Value |
|---|---|
| Official Registry name | com.gc-airporttransfers/booking (domain-verified namespace): https://registry.modelcontextprotocol.io/v0.1/servers?search=com.gc-airporttransfers |
| Version | 2.3.8, active, isLatest: true |
| Transport | Remote, Streamable HTTP |
| Endpoint | https://gc-airporttransfers.com/wp-json/atb-gateway/v1/mcp |
| Authentication | OAuth 2.1 with PKCE (S256). Client ID Metadata Documents, with dynamic client registration as a fallback. RFC 9728 protected-resource metadata; an unauthenticated request gets 401 with a resource_metadata pointer. No API key. |
| Protocol versions | 2026-07-28 (incl. server/discover), 2025-11-25, 2025-06-18 |
| Tools | get_service_info, get_quote, check_availability (read-only, readOnlyHint: true), request_booking (destructiveHint: false; creates a pending request only). Output schemas on the structured tools; MCP Apps quote card. |
| Repository | None: hosted commercial service, source not public |
| License | Proprietary (hosted service) |
| Website / docs | https://gc-airporttransfers.com.au/ai-agent-gateway/ |
| Support | admin@gc-airporttransfers.com.au |
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.gc-airporttransfers"
curl "https://api.mcp.github.com/v0.1/servers?search=gc-airporttransfers" # currently empty
Thank you for considering it.
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | com.llmtomd/llmtomd (HTTP-verified namespace for llmtomd.com) |
| Version | 1.0.3, active, isLatest |
| Remote | Streamable HTTP: https://mcp.llmtomd.com/mcp |
| Auth | OAuth 2.1 (PKCE + dynamic client registration) |
| Repository | https://github.com/codeshoel/llmtomd-mcp |
| License | MIT (documentation; hosted service) |
| What it does | Converts PDFs, Office docs, websites and audio into AI-ready Markdown, and lets agents search and ask questions across the user's converted documents. |
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=llmtomd"
Thanks!
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | com.gta6times/gta6times (HTTP-verified namespace for gta6times.com) |
| Version | 1.1.0, active, isLatest |
| Remote | Streamable HTTP at https://gta6times.com/mcp, no package |
| Auth | None: no sign-in and no key |
| Repository | https://github.com/vijaygopalbalasa/gta6times-mcp |
| License | MIT (the public repository holds the listing metadata and install docs; the server runs as a hosted service) |
| What it does | Read-only GTA 6 facts for assistants: launch countdown, unlock time and price by country, claim checks, trailers and source-labelled news. 11 tools, all readOnlyHint, each answer marked confirmed, reported or rumor. |
| Docs | https://gta6times.com/developers |
Verification: curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.gta6times" returns the entry above, and curl "https://api.mcp.github.com/v0.1/servers?search=gta6times" returns no servers yet.
GTA6 Times is an independent fan site and is not affiliated with Rockstar Games or Take-Two Interactive.
Registry onboarding request: LifeVerse Product Discovery
The server is active in the Official MCP Registry and the endpoint currently exposes four read-only tools. |
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | money.bankbridge/server (DNS-verified namespace for bankbridge.money) |
| Version | 1.0.3, active, isLatest: true |
| Remote | Streamable HTTP at https://bankbridge.money/api/mcp, no package |
| Auth | OAuth 2.1 with PKCE and dynamic client registration, or a Bearer bbk_... API key |
| Tools | 12, all readOnlyHint: true: accounts, transactions, search, spending summaries, recurring charges, monthly cashflow, merchant history, categories, holdings, investment transactions, plus connect_bank (returns a link to connect another bank). No write tools |
| Repository | https://github.com/bankbridge-money/bankbridge-plugin (client plugin, skills, docs and setup config; the server itself is a hosted service) |
| License | MIT (repository) |
| Docs | https://bankbridge.money/docs |
| Pricing | $5/mo or $50/yr per connected bank |
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=money.bankbridge"
curl "https://api.mcp.github.com/v0.1/servers?search=bankbridge" # currently empty
Testing without a bank account: the public demo key bbk_demo returns sample data as a bearer token, and the OAuth sign-in page has a "Try the demo" option.
Thanks!
|
Please consider onboarding PopNow to the GitHub MCP Registry. It is already published in the open-source MCP Registry; its current record was checked on 2026-10-27 and is
PopNow offers tools for generating/editing images, videos, music and speech, checking task status, and reading the connected account's creations. OAuth 2.1 supports PKCE S256, dynamic client registration and client metadata documents. API-key Bearer authentication is also available. Connecting is free; generation uses prepaid website credits through OAuth or a separate API USD balance through an API key. Larger OAuth jobs and all API-key generations require an approved budget. No credentials are included in the public repository. Please let us know if further information is needed for the manual curation step. Thank you. |
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | in.hookstep/hookpost (verified namespace for hookstep.in) |
| Version | 1.0.2, active (1.0.0 and 1.0.1 also active) |
| Remote | Streamable HTTP at https://hookpost.hookstep.in/api/mcp, no package |
| Auth | Workspace API key in Authorization: Bearer, declared in server.json as a secret header variable |
| Icon | 512×512 PNG in server.json |
| Repository | https://github.com/jatinder14/hookpost-mcp (MIT; listing metadata, install docs, CLI and n8n node) |
| Docs | https://hookpost.hookstep.in/mcp |
| Contact | support@hookstep.in |
The README already carries a one-click VS Code install link that prompts for the key as a password input. Thank you!
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | io.banksapi/docs (domain-verified namespace for banksapi.io) |
| Version | 0.1.0, active, isLatest: true |
| Remote | Streamable HTTP at https://banksapi.io/docs-mcp, no package |
| Auth | None. The server serves public documentation only and needs no account or API key |
| Tools | 4, all with readOnlyHint: true: search-banksapi-docs, get-banksapi-docs-page, get-banksapi-openapi-spec, get-banksapi-overview |
| Repository | The server is closed source and hosted by BANKSapi. Public install config and agent skills: https://github.com/BANKSapi/claude-plugin |
| License | Plugin repository: MIT |
| Docs | https://docs.banksapi.de/guide/docs-mcp.html |
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.banksapi/docs"
|
Onboarding request:
Would love to have it in the GitHub MCP Registry / VS Code gallery. Thanks! |
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | io.boim/vendors (DNS-verified namespace for boim.io) |
| Version | 2.0.2, active, isLatest: true |
| Transport | Remote, streamable HTTP: https://boim.io/api/mcp |
| Auth | None (no OAuth, no API key) |
| Repository | https://github.com/kikiyop1101/boim-mcp |
| License | MIT |
| What it does | Read-only lookup of Korean businesses (about 2.76M across all industries, SEMAS open data), about 76K vendors with public-procurement records (PPS open data) and about 9,100 open public tenders (KONEPS, Defense e-Procurement, LH, K-water, Nuri-jangteo). Six tools, all readOnlyHint: true; results are not ranked. |
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.boim"
curl "https://api.mcp.github.com/v0.1/servers?search=boim"
The second call returns no entry yet.
Submitted by PublicID Co., Ltd., the company that runs BOIM. This request was drafted with help from our AI assistant.
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | net.totallytarot/calculators (domain-verified namespace for totallytarot.net) |
| Version | 1.1.0, active, isLatest: true |
| Transport | Remote, streamable HTTP: https://totallytarot.net/mcp |
| Auth | None (no OAuth, no API key) |
| Repository | None public; this is a hosted remote server |
| License | Hosted service, free to call under the usage terms |
| Docs | https://totallytarot.net/library/developers/api-guide |
| What it does | Deterministic calculators, 18 read-only tools: Western natal charts and transits, planetary positions, moon phases, retrogrades, eclipses with local coverage, Vedic panchang and Vimshottari dasha, Chinese lunar calendar, solar terms and four pillars, I Ching hexagram text, Maya calendar conversion, and a tarot birth card. Every result is computed by the engine. |
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=net.totallytarot"
curl "https://api.mcp.github.com/v0.1/servers?search=totallytarot"
The second call returns no entry yet.
Submitted by Victoria Lee LLC, the publisher. Support: admin@totallytarot.net. Also listed in the Claude connectors directory.
Hi @Wolfe-Jam, thanks for the thoughtful follow-up and for continuing to publish and validate your servers.
A few clarifications from our side: the GitHub MCP Registry now has the ability to sync versions from the open source registry, but onboarding a new server is still a manual curation process today. Once a server has been onboarded, newly published versions from the OSS registry should sync from there.
I’m closer to the technical side than the product/curation criteria, so I don’t want to overstate anything here. I’ll share your request with our product team and ask whether we’re able to move forward with onboarding them.
Thanks again for your patience, and for offering to help valid…