📌 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: 107 comments 6 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. |
|
Hi @trent-j Could you please provide the exact steps or documentation required to list or publish my custom MCP server to the GitHub Registry https://github.com/mcp registry. I have security MCP server (Org level) which is used to provide security vulnerability remediation. I have already raise an support ticket for the process but didn't get any resolution for this. Ticket: 4444073 |
|
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. 🙏 |
|
We really appreciate your interest and the effort you put into getting your servers listed on the GitHub MCP Registry. We’re glad to share that they have now been onboarded. |
|
Wow! what amazing news, thank you for your patience and steer, much appreciated. |
|
Thanks again, trent-j 🙏 — two more of the FAF family are now published on the official MCP registry and ready whenever onboarding has room:
Both are live on registry.modelcontextprotocol.io under one.faf/*, following the OSS-registry-first process from this thread. No rush at all — 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:
|
| Field | Value |
|---|---|
| Registry entry | io.github.negm17111995/maqami-travel, version 1.0.6, active and latest |
| Endpoint | https://mcp.maqami.co/ (Streamable HTTP) |
| Auth | None. No account or API key |
| Package | npm maqami-travel 1.0.6, a stdio bridge to the remote endpoint (npx -y maqami-travel) |
| Repository | https://github.com/negm17111995/mcp-server (MIT) |
| server.json | https://github.com/negm17111995/mcp-server/blob/main/server.json |
What it does: MAQAMI is a hotel and flight booking platform with 3M+ hotels. The server searches hotels and flights, returns hotel details and reviews, looks up places and weather, and supports a prebook and book flow. Booking creates a real reservation and requires guest and payment details.
https://github.com/mcp/io.github.negm17111995/maqami-travel currently returns 404, and searching maqami on the GitHub MCP Registry API returns no results.
Happy to provide anything else needed. Thank you!
Onboarding request:
|
| Field | Value |
|---|---|
| Registry entry | io.github.Firefloco/chirpie |
| Version | 1.2.3, active, isLatest (published from CI via GitHub OIDC on each release) |
| Transports | Remote Streamable HTTP at https://chirpie.ai/mcp, and stdio via npx -y @chirpie/mcp |
| Auth | OAuth 2.1 with PKCE and dynamic client registration; API key bearer also accepted |
| Source | https://github.com/Firefloco/chirpie-mcp (MIT) |
| Docs | https://chirpie.ai/docs/mcp |
| Support | support@chirpie.ai |
Chirpie is the publishing connector for AI agents: post, thread and schedule to X, Bluesky, LinkedIn, Mastodon and Telegram, attach media, save drafts, read post analytics and answer comments. Every tool carries title, readOnlyHint, destructiveHint and openWorldHint annotations.
Thank you!
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | com.searchfragments/search-fragments (domain-verified namespace) |
| Version | 0.2.4, active, isLatest in the MCP Registry |
| Registry entry | https://registry.modelcontextprotocol.io/v0.1/servers/com.searchfragments%2Fsearch-fragments/versions/latest |
| Endpoint | https://searchfragments.com/api/mcp (Streamable HTTP), no authentication required |
| Tools | 3: resolve_fragment, verify_claim, submit_resolution_feedback, each with a title and explicit readOnly/destructive/idempotent/openWorld hints |
| Repository | https://github.com/Searchfragments/search-fragments-mcp (MIT) |
| Website / privacy / terms | https://searchfragments.com · https://searchfragments.com/privacy · https://searchfragments.com/terms |
| Support | hello@searchfragments.com |
Search Fragments resolves half-remembered books, films, songs and people (tip-of-the-tongue queries) into a cited answer, a shortlist, or an explicit "not resolvable". It is built to decline rather than guess. Free to use, no account or key needed. Already listed in Claude's connector directory and in Cursor.
Verify: curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.searchfragments"
|
Requesting initial GitHub MCP Registry onboarding for Silicon Valley Atlas, following the registry-first curation process here.
Current access limitation: Google sign-in remains in Testing, so only Atlas test users can connect until the owner publishes the consent configuration. Please consider this a pending-access onboarding request. We are not claiming gallery inclusion or unrestricted sign-in. |
|
Onboarding request: com.veriteknik/mcp Requesting initial GitHub MCP Registry onboarding, following the OSS-registry-first, manual-curation process described in this thread.
The server lets VeriTeknik customers manage their servers, DNS, backups and support tickets from their AI assistant. It is also submitted to the Claude Connectors Directory and ChatGPT Apps, and a Docker MCP Catalog PR is open (docker/mcp-registry#5392). Thanks! |
|
Requesting initial GitHub MCP Registry onboarding for pdfrender, following the OSS-registry-first, manual-curation process described in this thread. I build and run this server.
What it does. pdfrender turns HTML and CSS into PDF over a REST API and an MCP server. WeasyPrint 70 lays out the pages, with paper size, margins, headers, footers and page numbers set in CSS. It runs no JavaScript and fetches no URLs, so images and fonts go in as data: URIs. Limits are 2 MB of HTML and 50 pages per render. The servers are in Germany. The free plan has 100 credits a month and needs no card. Tools:
|
|
Requesting initial GitHub MCP Registry onboarding for AcqPath, following the OSS-registry-first, manual-curation process described in this thread. We build and operate this server.
AcqPath is an independent source-rights observation layer for AI data workflows. Given a public resource and intended use, it records supported machine-readable AI-use declarations and produces signed evidence for preflight, governance and audit decisions before RAG ingestion, indexing, training or search. Important scope boundary: AcqPath does not grant licences, establish ownership, provide legal clearance, prove actual downstream use, bypass access controls, or treat UNKNOWN as permission. Happy to provide any additional validation metadata the curation team needs. |
|
Following the notes above (dogfooding them myself 🙂), requesting onboarding for two more FAF servers. They join
What they do: persistent project context for xAI Grok and Google Gemini, from the IANA-registered Verification: Thanks! |
|
Please consider onboarding Toffu (ai.toffu/toffu) to the GitHub MCP Registry. Toffu is an AI marketing platform for marketing teams. Its hosted MCP server lets agents work with ad accounts, analytics, content, campaigns, and reports, including Google, Meta, and LinkedIn ad platforms.
Could you review Toffu for inclusion on github.com/mcp and let us know if any additional metadata or validation is needed? |
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | io.github.configure-dev/configure-memory |
| Version | 3.0.0, active and latest in the Official MCP Registry, verified October 5, 2026 UTC |
| Registry entry | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.configure-dev%2Fconfigure-memory/versions/3.0.0 |
| Transport | Remote Streamable HTTP at https://mcp.configure.dev/ |
| Authentication | OAuth authorization code with S256 PKCE and dynamic client registration; a Configure account is required for profile access |
| Public package and connection guide | https://github.com/configure-dev/configure-mcp-plugin |
| License | MIT for the public metadata and skill wrapper. The hosted service and backend are separate and subject to Configure's terms. |
| Website and documentation | https://configure.dev and https://docs.configure.dev |
| Privacy and terms | https://configure.dev/privacy.html and https://configure.dev/terms.html |
Public initialization and discovery expose nine general MCP tools. Profile reads and writes require the user's authorization. Optional linked apps require their own connections and permissions. The connector accesses the user's Configure profile; it does not provide automatic access to another assistant's private chat history.
The public repository contains metadata, connection instructions, and a focused context skill, not backend source. Native GitHub Copilot end-to-end OAuth testing is not yet complete, and no GitHub catalog approval is claimed. Please let us know what additional validation would help your review.
|
Onboarding request: Requesting initial GitHub MCP Registry onboarding for Dataddo Data to AI, following the OSS-registry-first, manual-curation process described in this thread. We (Dataddo) build and run this server.
What it does: Data to AI securely connects LLMs and agents to a company's business data from 400+ sources (CRMs, databases, ERPs, SaaS apps). Dataddo extracts and refreshes the data, stores it in SmartCache and serves it through a semantic layer: the model asks for business entities, fields and predefined metrics by name, never SQL, and answers carry their data freshness. The added semantics mean fewer confidently wrong answers. You control which data the agent sees, and sensitive fields can be hashed or excluded before they reach the model. You don't need to give every user access to every system. Verify: Thanks for considering it! |
|
Onboarding request: Please consider DropTheHassle for the GitHub MCP Registry. When someone tells their coding agent "put this online", the agent uploads the site it built and hands back a real HTTPS link, so nobody shares a localhost link again. It also checks with the domain registry whether a name is free and puts the site on its own domain with no DNS setup. The agent can never spend money.
Thanks! |
|
Onboarding request: Please consider Untap for the GitHub MCP Registry. Untap checks whether someone in the UK is owed money for a delayed or cancelled train (Delay Repay under each operator's scheme), a disrupted flight (UK261 and EU261) or a TfL journey charge, and returns the amount, the deadline and the operator's own claim link. People submit claims themselves; Untap never files on their behalf.
Verify: Thanks for considering it. |
|
Requesting onboarding of Fattly to github.com/mcp:
Thank you! |
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | io.github.outcomeci/mcp-server |
| Version | 1.0.0 |
| Official registry entry | Active/latest record |
| Repository and manifest | outcomeci/mcp-server · server.json |
| Transport | Remote Streamable HTTP |
| Endpoint | https://api.outcomeci.com/v1/mcp |
| Authentication | Browser-based OAuth; each user signs in to OutcomeCI and authorizes a workspace |
| Documentation | Connection instructions and tool catalog · Setup guides |
| License | MIT for the repository’s documentation, metadata, and configuration examples. The hosted backend is not distributed by this repository. |
| Website | https://outcomeci.com |
OutcomeCI connects AI assistants to workspace workflows: discover connector schemas, validate and save workflow definitions, configure triggers, and inspect run logs. Credentials are added through secure deposit links; the MCP tools expose Vault metadata rather than secret values. The server is hosted, with no local package installation required.
Verification:
curl 'https://registry.modelcontextprotocol.io/v0.1/servers/io.github.outcomeci%2Fmcp-server/versions/latest'Happy to provide any additional metadata or validation needed for onboarding. Thank you!
|
Onboarding request for github.com/mcp:
Verification: |
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…