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: 229 comments 12 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: sh.dflow/mcp
Published to the official registry on 2026-10-12. Please onboard it to github.com/mcp so it can show up in the VS Code MCP gallery. Verification: curl "https://registry.modelcontextprotocol.io/v0.1/servers/sh.dflow%2Fmcp/versions/1.0.0" |
Onboarding request: de.viafrei/mcpPlease consider ViaFrei for onboarding into the GitHub MCP Registry.
A stdio bridge to the same endpoint is on npm as Verification: Disclosure: I build ViaFrei; this is my own server. Sergii Mavrov |
Onboarding request: four Antevo servers (
|
| Field | The 07:00 Brief | Antevo Executive Brief | Antevo Trademark | Antevo Wealth |
|---|---|---|---|---|
| Registry name | ch.antevo/0700-brief |
ch.antevo/executive |
ch.antevo/trademark |
ch.antevo/wealth |
| Version | 1.0.0 | 1.0.1 | 1.0.1 | 1.0.1 |
| Remote (streamable HTTP) | https://api.antevo.ch/mcp/0700/mcp |
https://api.antevo.ch/mcp/executive/mcp |
https://trademark.antevo.ch/mcp |
https://api.antevo.ch/mcp/wealth/mcp |
| Auth | none | none | none for screening; OAuth 2.1 (PKCE, DCR) for the signed-in tools, asked for on first use | OAuth 2.1 with PKCE and dynamic client registration |
Shared by all four
- Repository: https://github.com/ANTEVO-CH/antevo-mcp, with connection metadata, install links, and the Cursor, Gemini CLI and Kiro manifests.
- License: the repository is MIT. The hosted services are proprietary, run by Antevo (VestAI LTD).
- Documentation: https://antevo.ch/mcp/
What they do
- The 07:00 Brief: a daily editorial morning read on markets and the world: what moved, what to watch, the Risk Radar and sector notes. No account.
- Antevo Executive Brief: markets, macro history and world events, with the dated edition behind every answer. No account.
- Antevo Trademark: screens a brand name across 50+ national and regional trademark registers, with each office's opposition window. Signed in: your watchlist, conflicts, deadlines and holder investigations.
- Antevo Wealth: a household's own balance sheet (net worth, holdings, exposure, risk, real assets). It records holdings only after the user approves each change, and it never trades.
Verification
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=ch.antevo"
curl "https://api.mcp.github.com/v0.1/servers?search=ch.antevo" # 0 todayThank you. Contact: contact@antevo.ch
|
Onboarding request: Status Is Down (
|
Onboarding request:
|
| Field | Value |
|---|---|
| Official registry name | br.com.9bot/mcp |
| Version | 1.0.0 (active, isLatest) |
| Remote | Streamable HTTP at https://mcp.9bot.com.br/mcp |
| Auth | OAuth 2.1 with PKCE (S256) and dynamic client registration; scopes 9bot.read_only and 9bot.full_access. Metadata at https://mcp.9bot.com.br/.well-known/oauth-authorization-server |
| Repository | https://github.com/9-bot/mcp |
| License | MIT (public metadata and docs; the hosted service is operated by 9bot) |
| Website / docs | https://9bot.com.br/en/ · https://9bot.com.br/en/9bot-docs/ |
| Privacy / Terms | https://9bot.com.br/en/privacy-policy/ · https://9bot.com.br/en/terms-of-use/ |
| Support | contato@9bot.com.br |
What it does: lets AI assistants manage, automate and analyze WhatsApp groups, communities and channels through a 9bot account. Requires a 9bot subscription (7-day trial available).
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=br.com.9bot"
curl "https://api.mcp.github.com/v0.1/servers?search=9bot" # currently 0 results
Happy to adjust and re-publish anything if needed. Thanks!
Onboarding request: com.xposedornot/xposedornot (XposedOrNot)Please consider XposedOrNot for github.com/mcp and the VS Code MCP gallery. We run the hosted server and the breach index behind it. Values read from the official registry on 2026-10-19.
What it does: XposedOrNot data breach lookups for agents. Check whether an email appears in known breaches, read its breach history, list breaches by company domain or breach ID, and get breach exposure counts for a domain, plus index metrics and recent breaches. Six read-only tools, each with a title and readOnlyHint annotation. Never returns passwords. Verification: Disclosure: I run XposedOrNot. Thanks for curating the list. |
|
Onboarding request: io.github.andreibesleaga/agentic-system-core |
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | ai.mailbeast/mailbeast |
| Version | 1.0.2 (active, isLatest: true) |
| Transport | remote, Streamable HTTP at https://mcp.mailbeast.ai/mcp |
| Auth | OAuth 2.1 (Client ID Metadata Document and dynamic client registration, PKCE S256); the user picks read-only or read + write on the consent screen |
| Website | https://mailbeast.ai |
| Docs | https://developer.mailbeast.ai/mcp-server |
| Repository | none: hosted service by Mark-Digital, LLC, source is not public |
| License | Proprietary |
| Description | Cold email outreach in MailBeast.ai: campaigns with A/B sequences, leads, sending mailboxes and warmup, reply inbox and campaign analytics. |
Check (unauthenticated request returns 401 with OAuth discovery):
curl -si -X POST https://mcp.mailbeast.ai/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | com.mybestsim/esim-comparator |
| Version | 1.1.0 (latest) |
| Transport | Remote, Streamable HTTP: https://mcp.mybestsim.com/mcp |
| Auth | None (read-only, rate limited) |
| Repository | https://github.com/MyBestSim/mybestsim-mcp |
| License | MIT |
| Docs | https://mybestsim.com/en/mybestsim-in-chatgpt-and-claude/ |
Compares prepaid travel eSIM plans from 30+ providers by destination, data and trip length, and plans multi-country trips (4 read-only tools: search_esim_plans, get_destination_overview, get_esim_plan, plan_trip_esim). We run the hosted server and the comparator behind it.
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | io.github.bersimao/b1-mcp-server (GitHub-verified namespace) |
| Version | 1.5.1, active, isLatest: true |
| Transport | local stdio, npm package b1-mcp-server (npx b1-mcp-server) |
| Repository | https://github.com/bersimao/b1-mcp-server (I maintain it) |
| License | MIT |
It gives AI clients guarded access to SAP Business One: SQL on SAP HANA / Microsoft SQL Server, and the Service Layer OData API. SQL is read-only (only SELECT passes the server-side guardrail). Service Layer is GET-only by default; writes are opt-in per connection profile and require user approval (MCP elicitation, or the client's permission prompt) unless the profile explicitly disables it, which is intended for development companies. Credentials stay in a local file, and no tool is designed to return them.
Onboarding request: io.sociality/sociality-mcp (Sociality.io MCP)Please consider Sociality.io MCP for github.com/mcp. We operate the hosted server. I verified the registry values below on 2026-10-19; the GitHub registry currently returns 0 results for Sociality.
Sociality.io MCP gives AI agents access to social account analytics, post insights, and public competitor benchmarking across Facebook, Instagram, X, LinkedIn, YouTube, and TikTok. It exposes 7 tools: 6 read-only tools and 1 tool for explicitly adding a tracked competitor. Access follows the authorized user's workspace permissions; analytics and post queries use MCP credits. Verification: curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.sociality%2Fsociality-mcp"
curl "https://api.mcp.github.com/v0.1/servers?search=sociality"Happy to provide any additional information needed for onboarding. Thank you! |
onboarding request:
|
| field | value |
|---|---|
| registry entry | com.omnara/omnara (DNS-verified namespace on omnara.com), 0.1.0, active, isLatest: true |
| endpoint | https://app.omnara.com/mcp, streamable HTTP |
| auth | OAuth 2.1 + PKCE (S256) with Client ID Metadata Documents, so clients sign in with just the URL. unauthenticated requests get 401 with a resource_metadata pointer. personal access tokens also work |
| tools | 75, each with a title and readOnlyHint / destructiveHint / idempotentHint / openWorldHint |
| repo | https://github.com/omnara-ai/omnara (Apache-2.0, 2.9k stars) |
| docs | https://docs.omnara.com/api/authentication#connecting-mcp-clients |
| website / privacy / terms | https://www.omnara.com · https://www.omnara.com/privacy · https://www.omnara.com/terms |
| also listed in | Claude's connectors directory, Glama (connector rated A), the official MCP registry |
what it does: Omnara is an open-source managed agent platform. from Copilot you can launch AI agents on any model and machine, message them, read their events, and approve their tool calls.
verify: curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.omnara/omnara"
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | my.harbor/harbor (domain-verified namespace on harbor.my) |
| Version | 1.0.67, active, isLatest: true |
| Transport | Remote, streamable HTTP at https://app.harbor.my/mcp |
| Auth | OAuth 2.1 with PKCE (S256) and dynamic client registration. No API key to create or paste. |
| Repository | Hosted service, so the server's source is private. Our CLI for the same API is public: HarborMyNotes/harbor-cli (MIT). |
| License | Proprietary hosted service, with a free plan |
| Website | https://harbor.my/bring-your-own-ai/ |
What it does: lets an assistant search, read, write and organize someone's notes, notebooks, tags and tasks in Harbor, and open the files attached to them. Encrypted notes never leave the server as readable text.
Harbor is Evernote-compatible, so people moving off Evernote can bring years of notes with them and use them from Copilot and VS Code.
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=my.harbor/harbor"
Thanks for running this thread.
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | io.github.speedyapply/jobspy |
| Version | 1.4.0, active, isLatest |
| Package and transport | PyPI python-jobspy (extra mcp), stdio, run as uvx --from "python-jobspy[mcp]" mcp-jobspy |
| Repository | https://github.com/speedyapply/JobSpy |
| License | MIT |
What it does: searches LinkedIn, Indeed, Glassdoor, ZipRecruiter and regional job boards. search_jobs returns job previews and can save the full records to a file; get_job_details returns full records from a search without new requests. No API key.
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.speedyapply%2Fjobspy/versions/latest"
|
Requesting onboarding for Clerk's official MCP server to github.com/mcp.
|
and others
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…