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: 408 comments 19 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: NoMac ( All three are published to the official MCP Registry first, per the notes above, under the
Verification: Thanks! |
|
Onboarding request for github.com/mcp:
Disclosure: I work on HandlePilot. Thanks! |
Onboarding request: Customermates (
|
| Field | Value |
|---|---|
| Registry name | io.github.benjiwagner/customermates |
| Version | 0.1.0 (active, isLatest: true, published 2026-09-30) |
| Transport | Remote Streamable HTTP: https://customermates.com/api/v1/mcp |
| Auth | OAuth sign-in (the workspace is chosen on the consent screen); an API key in the x-api-key header also works |
| Repository | https://github.com/customermates/customermates |
| License | AGPL-3.0-only for first-party code outside ee/; commercial server components have separate terms |
| Docs | https://customermates.com/en/docs/mcp |
What it does. Open-source CRM. Customermates is the workspace where AI agents work with your customers, your knowledge and your rules, and people stay in control of what goes out. Through MCP an agent finds, creates, updates and links contacts, organizations, deals and tasks under the permissions of the user it connects as.
Verification (values read from the registry on the day of posting):
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=customermates"
curl "https://api.mcp.github.com/v0.1/servers?search=customermates" # no server returned yet
Onboarding request: BestSaaSWebDesigns (
|
| Field | Value |
|---|---|
| Registry name | com.bestsaaswebdesigns/catalog (domain-verified namespace, HTTP proof on bestsaaswebdesigns.com) |
| Version | 1.1.0, status active, isLatest: true (published 2026-10-26) |
| Transport | Remote, Streamable HTTP: https://mcp.bestsaaswebdesigns.com/mcp |
| Auth | None (free, public, read-only) |
| Repository | https://github.com/bestsaaswebdesigns/bestsaaswebdesigns-mcp (docs and registry metadata; the server is hosted) |
| License | MIT |
| Website / docs | https://bestsaaswebdesigns.com/mcp · https://bestsaaswebdesigns.com/mcp/docs |
What it does: Search 400+ real SaaS marketing websites by category, page section, visual style, tech stack, palette and font. 4 read-only tools (list_filters, search_sites, list_site_links, get_site) return live site links, colour palettes, fonts, stacks and links to screenshots, as design references for coding agents.
Verification (values read from the registry today):
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.bestsaaswebdesigns/catalog"
# → com.bestsaaswebdesigns/catalog 1.1.0, status active, isLatest true
curl "https://api.mcp.github.com/v0.1/servers?search=bestsaaswebdesigns"
# → count 0 (not listed yet)
Thanks!
|
Onboarding request: AI Visibility ( Published to the official MCP Registry first, per the process in the notes above.
Verification: Thanks! |
Onboarding request: Pachca (
|
| Field | Value |
|---|---|
| Registry name | com.pachca/mcp |
| Version | 1.5.0, status active, isLatest: true (published 2026-10-31) |
| Transport | Remote, Streamable HTTP: https://mcp.pachca.com/mcp |
| Auth | OAuth browser sign-in or a Pachca API token in the Authorization: Bearer header |
| Repository | https://github.com/pachca/openapi — plugin, skills, documentation and registry metadata; the MCP server is hosted |
| Repository license | MIT |
| Website | https://pachca.com |
| Documentation | https://dev.pachca.com/guides/mcp/overview |
| Server manifest | https://github.com/pachca/openapi/blob/main/server.json |
What it does: Pachca is a team chat app. Its official MCP server lets AI agents search and summarize discussions, send messages and thread replies, prepare drafts, set reminders, and manage chats and bots. Every call respects the connected account’s permissions, workspace role, chat access and plan.
Verification (checked on 2026-11-02):
curl -sS "https://registry.modelcontextprotocol.io/v0.1/servers?search=pachca"
# com.pachca/mcp — version 1.5.0, status active, isLatest: true
curl -sS "https://api.mcp.github.com/v0.1/servers?search=pachca"
# 0 results — not listed yetThank you for considering Pachca for the GitHub MCP Registry!
Onboarding request:
|
|
Onboarding request: com.biglysales/biglysales Hi! Requesting that BiglySales be added to github.com/mcp.
Verification: Thanks! |
|
Request: onboard com.acriumautomated/acrium to the GitHub MCP Registry |
Onboarding request: LurkAPI (
|
| Field | Value |
|---|---|
| Registry name | io.github.mesmerlord/lurkapi |
| Version | 1.0.0, active, isLatest: true (published 2026-11-01) |
| Remote endpoint | https://api.lurkapi.com/mcp (Streamable HTTP) |
| Auth | OAuth 2.1 with PKCE and dynamic client registration (browser sign-in), or an x-api-key header |
| Repository | https://github.com/mesmerlord/lurkapi-claude-plugin (the plugin and skills that register this server; the server itself is a hosted, closed-source service) |
| License | MIT (plugin repo); the hosted API has its own terms |
| What it does | Read-only access to public social media data: profiles, posts, comments, video transcripts and ad library results from 16 platforms (TikTok, Instagram, YouTube, Reddit, X, LinkedIn and more), one tool per endpoint. It's a paid API (most calls 1 credit) with 100 free credits at signup, no card. |
| Website | https://lurkapi.com |
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.mesmerlord/lurkapi"
curl "https://api.mcp.github.com/v0.1/servers?search=lurkapi" # not listed yet
Disclosure: I run LurkAPI. Thanks for considering it.
|
Onboarding request: Llama Logger ( Published to the official MCP Registry first, per the process in the notes above.
Verification: Disclosure: I work on Llama Logger (Llamachant Technology Ltd.). Thanks! |
Onboarding request: Maqui Analytics (
|
| Field | Value |
|---|---|
| Official registry name | io.github.luis-fuentes/maqui |
| Latest version | 1.0.0, status: active, isLatest: true (checked 2026-11-02) |
| Transport | Remote Streamable HTTP at https://app.somosmaqui.com/api/mcp; no local server package required |
| Authentication | OAuth with PKCE and explicit consent for approved client registrations, or a per-account Bearer API token |
| Repository | https://github.com/somosmaqui/maqui-mcp (documentation and registry metadata) |
| License | No open-source license is declared in the public listing repository; the MCP backend is a hosted service |
| Website / documentation | https://somosmaqui.com/asistentes-ia |
| Privacy policy | https://somosmaqui.com/privacidad |
What it does: Read-only marketing analytics for local businesses and agencies: Instagram, Google Ads, Meta Ads, GA4, Search Console, Microsoft Clarity, reviews, CRM leads and Fudo POS sales. Tools are scoped to the authorized Maqui account and its enabled modules.
Access: Real business data requires a provisioned Maqui account. OAuth accepts approved client registrations rather than unrestricted dynamic registration; additional client registrations and callbacks require approval by Maqui. Supported OAuth clients can select a synthetic demo on the consent screen without accessing real client data. This request does not claim that the VS Code / Copilot OAuth flow has already been validated.
Verification (checked 2026-11-02):
curl -sS "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.luis-fuentes%2Fmaqui/versions/latest"
# version 1.0.0, status active, isLatest true
curl -sS "https://api.mcp.github.com/v0.1/servers?search=maqui"
# servers: [], total: 0Please consider Maqui Analytics for initial onboarding so that subsequent versions can sync from the official registry. Thank you!
|
Note 🤖 Claude Opus 5.5 responding on behalf of Vishal Dubey Onboarding request: Vibecode (
|
| Field | Value |
|---|---|
| Registry name | com.vibecodeapp/vibecode (namespace verified by DNS on vibecodeapp.com) |
| Version | 1.0.0, active, isLatest: true |
| Transport / endpoint | Remote, Streamable HTTP, https://api.vibecodeapp.com/mcp |
| Auth | OAuth 2.1 with PKCE (S256), dynamic client registration and client ID metadata documents. Discovery: https://api.vibecodeapp.com/.well-known/oauth-protected-resource |
| Repository | https://github.com/vibecode/vibecode |
| License | MIT |
| What it does | Builds native iPhone apps and web apps from a chat. Vibecode's agent writes, builds (on cloud Macs for iPhone apps) and tests the app in the user's Vibecode account; the assistant follows the build, reads code and logs, and deploys the app. |
Verification:
curl -s "https://registry.modelcontextprotocol.io/v0.1/servers/com.vibecodeapp%2Fvibecode/versions/latest"|
Requesting a listing for Perly Pay's MCP server, |
Onboarding request: FlareWarden (
|
| Field | Value |
|---|---|
| Registry name | com.flarewarden/website-monitoring (namespace verified by DNS on flarewarden.com) |
| Version | 0.1.0, active, isLatest: true (published 2026-11-01) |
| Remote endpoint | https://mcp.flarewarden.com/mcp (Streamable HTTP) |
| Auth | OAuth 2.1 with PKCE (S256), dynamic client registration or a client ID metadata document. The public tools (is a service or website down) work without sign-in. |
| Repository | https://github.com/Flare-Warden/agent-plugins (plugin, skills and listing metadata; the server is a hosted service) |
| License | MIT (plugin repository) |
| Docs | https://flarewarden.com/docs/ai-agents |
What it does: checks whether a website or a service such as Stripe or AWS is down, from the vendor's own status page and FlareWarden's checks from several regions. With a FlareWarden account, it sets up and runs uptime monitoring for your sites, the services they depend on, cron jobs and status pages; every change is planned and confirmed before it is made.
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.flarewarden/website-monitoring"
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…