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: 662 comments 23 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:
Thanks! |
Onboarding request: Alexein AI (
|
| Field | Value |
|---|---|
| Registry name | ai.alexein/memory (domain-verified over HTTP on alexein.ai) |
| Version | 1.0.0, status active, latest |
| Remote | streamable-http, https://api.alexein.ai/v1/mcp |
| Auth | OAuth 2.1: authorization code + S256 PKCE, dynamic client registration, RFC 9728 protected-resource metadata |
| Repository | Hosted service, no public server repository. Client plugins: Alexein-AI/copilot-plugin |
| Description | Persistent personal memory for AI assistants: search what you told it before and save new facts. |
| Website / docs | https://alexein.ai · https://docs.alexein.ai |
| Privacy | https://alexein.ai/legal/privacy |
| Contact | zainali@alexein.ai |
Tested with GitHub Copilot in VS Code and Copilot CLI: both sign in by OAuth and list the tools.
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=ai.alexein/memory"
|
Onboarding request:
Website: https://cubelv.com/en/ · Docs: https://cubelv.com/en/mcp/ Thank you! |
|
Following up on our 9 Nov request to have QIE Wallet appear in the GitHub MCP Registry / Copilot gallery. The server is already live on the official MCP Registry as digital.qie/wallet (active, v0.1.0, published 3 Nov 2026). Remote endpoint: https://mcp.qie.digital/mcp (Streamable HTTP, no auth, six read-only tools). https://api.mcp.github.com/v0.1/servers?search=qie still returns no results as of 17 Nov 2026. Happy to provide any extra metadata you need for the gallery sync. |
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | com.shaftware/resorcerer (domain-verified namespace) |
| Version | 1.0.1, status: active, isLatest: true |
| Transport | Remote, streamable HTTP |
| Endpoints and auth | https://app.resorcerer.ai/api/mcp, OAuth 2.1 with PKCE and dynamic client registration |
| Repository | https://github.com/resorcerer/resorcerer |
| License | proprietary hosted service |
| Website | https://www.resorcerer.ai |
What it does: Resorcerer is an organizational resource planning tool.
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=resorcerer"
curl "https://api.mcp.github.com/v0.1/servers?search=resorcerer"
Contact: kyle@shaftware.com
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | com.shaftware/componecat (domain-verified namespace) |
| Version | 1.0.1, status: active, isLatest: true |
| Transport | Remote, streamable HTTP |
| Endpoints and auth | https://app.componecat.ai/api/mcp, OAuth 2.1 with PKCE and dynamic client registration |
| Repository | https://github.com/componecat/componecat |
| License | proprietary hosted service |
| Website | https://www.componecat.ai |
What it does: Componecat is a software component catalog: a hierarchical, richly-typed registry of every system, service, library, and resource your organization operates.
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=componecat"
curl "https://api.mcp.github.com/v0.1/servers?search=componecat"
Contact: kyle@shaftware.com
Onboarding request: Genaya (
|
| Field | Value |
|---|---|
| Registry name | io.github.genaya-app/genaya |
| Version | 1.2.0 (active, isLatest) |
| Remote | streamable-http, https://api.genaya.com/mcp |
| Auth | OAuth 2.1 (authorization code + PKCE, dynamic client registration); an API key bearer mode is also supported |
| Repository | https://github.com/genaya-app/genaya-claude-plugins |
| License | MIT (repository) |
| Docs | https://developer.genaya.com/mcp |
What it does: Genaya is an operations platform for service businesses (clinics, agencies, field services, construction). The server lets an assistant ask about the schedule, clients, invoices, payments, calls and team, and prepare changes (create a client, book an appointment, send an invoice) that run only after the user confirms. Tools: whoami, ask_genaya, genaya_act, confirm_action, cancel_action, undo_action, list_actions.
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.genaya-app/genaya"
curl "https://api.mcp.github.com/v0.1/servers?search=genaya"
Thank you!
|
Onboarding request: io.improvado/mcp (Improvado) for GitHub MCP Registry
Not listed yet on GitHub's side: |
Onboarding request: Elfsight (
|
| Field | Value |
|---|---|
| Registry name | com.elfsight/elfsight (namespace verified via DNS on elfsight.com) |
| Version | 1.0.0 (active, isLatest) |
| Remote | streamable-http, https://mcp.elfsight.com/mcp |
| Auth | OAuth 2.1 (authorization code + PKCE, dynamic client registration); no API keys |
| Repository | https://github.com/elfsight/elfsight-mcp |
| License | MIT |
| Docs | https://github.com/elfsight/elfsight-mcp#readme |
What it does: Elfsight makes no-code widgets for websites (reviews, social feeds, forms, pricing tables and more). The server lets an assistant browse the apps, projects and widgets of the user's Elfsight workspace, create widgets from templates, update and publish their settings, and get install code. Changes stay a draft until published; nothing can be deleted. Tools: list_app_catalog, list_account_apps, list_projects, list_widgets, get_widget, get_widget_limit, list_widget_templates, get_install_code, get_widget_edit_links, create_widget, duplicate_widget, rename_widget, update_widget_settings, publish_widget, discard_widget_changes.
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.elfsight/elfsight"
curl "https://api.mcp.github.com/v0.1/servers?search=com.elfsight/elfsight"
Thank you!
Onboarding request: BrowserPair (
|
| Field | Value |
|---|---|
| Registry name | com.browserpair/browserpair (namespace verified via HTTP proof on browserpair.com) |
| Version | 1.1.0 (active, isLatest) |
| Remote | streamable-http, https://mcp.browserpair.com |
| Auth | OAuth 2.1 with PKCE (dynamic client registration and client ID metadata documents) |
| Repository | https://github.com/BrowserPair/browserpair-integrations |
| License | MIT (integration repository) |
| Docs | https://docs.browserpair.com/remote-mcp |
What it does: BrowserPair lets AI agents work in the user's own signed-in Chrome through a paired Chrome extension: open pages, read dashboards, fill forms and check results, with user approval for sensitive steps and results verified on the page.
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.browserpair/browserpair"
|
Please consider onboarding Capable ( Capable is an MCP-native CRM for founders and small B2B teams. An assistant can find contacts, companies and deals, prepare meeting context, and propose CRM updates from notes or conversations. Users review proposed changes field by field before saving them.
Verification: curl -s 'https://registry.modelcontextprotocol.io/v0.1/servers/run.capable%2Fcrm/versions/latest'
curl -s 'https://api.mcp.github.com/v0.1/servers?search=run.capable'The GitHub Registry search currently returns no entries. Please let us know if any additional metadata or validation is needed for review. Thank you! |
|
Requesting onboarding to github.com/mcp for a remote server.
Contact: hello@tapline.sh |
Onboarding request: Pressable (
|
| Field | Value |
|---|---|
| Registry name | com.pressable/mcp (namespace verified via DNS on pressable.com) |
| Version | 1.0.0, status: active, isLatest: true |
| Remote | streamable-http, https://mcp.pressable.com |
| Auth | OAuth 2.1 (authorization code + PKCE, dynamic client registration), signing in with a Pressable account. A Pressable MCP token sent as Authorization: Bearer also works. |
| Repository | None: proprietary hosted service. Setup docs: https://pressable.com/knowledgebase/get-started-with-pressable-mcp/ |
| License | Proprietary hosted service |
| Website | https://pressable.com/mcp/ |
What it does: Lets agents manage Pressable WordPress hosting: sites, backups, plugins, caching, domains and logs, acting with the signed-in user's own access.
Tested in VS Code: adding https://mcp.pressable.com as an HTTP server with no token completes the Pressable sign-in, and the tools load.
Verification:
curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.pressable"
Onboarding request: Rigsdata (
|
| Field | Value |
|---|---|
| Registry name | dk.rigsdata/rigsdata (namespace verified via DNS on rigsdata.dk) |
| Version | 1.0.0, active, isLatest |
| Remote | streamable-http, https://mcp.rigsdata.dk/mcp |
| Auth | OAuth 2.1 (authorization code + PKCE), protected resource metadata at https://mcp.rigsdata.dk/.well-known/oauth-protected-resource |
| Repository | None public: Rigsdata is a hosted service. Docs: https://rigsdata.dk/docs |
| License | Proprietary hosted service (commercial subscription) |
| What it does | Search and read Danish public-sector documents from an AI assistant: the Danish Parliament, public consultations, ministries, agencies, municipalities and the EU, with links to the sources. |
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=dk.rigsdata/rigsdata"
Onboarding request: Tidy Byte Tools (
|
| Field | Value |
|---|---|
| Registry name | io.github.tidybytetools/tidy-byte-tools |
| Version | 0.1.1 (active, isLatest) |
| Package and transport | PyPI tidy-byte-tools 0.1.1, stdio. Start with uvx tidy-byte-tools mcp |
| Repository | https://github.com/tidybytetools/tidy-byte-tools |
| License | MIT |
| Website | https://tidybytetools.github.io |
What it does: One local MCP server that installs our free lite tools together. An assistant can fix broken JSON, pull tables from a text PDF, turn documents into Markdown, hash files, encode or decode Base64, split Markdown into chunks, and check links. It runs on your computer. No API key. The server has 15 tools. Most of them only read local files. Three can write a file you ask for (save_chunks_jsonl, convert_to_markdown when you set an output path, and extract_pdf_tables). check_links requests the URLs you give it. The other tools work offline.
We also publish two related local servers, already active and isLatest in the official registry, if you want those listed too:
io.github.tidybytetools/json-repair-lite1.0.1, PyPIjson-repair-lite, stdio (uvx json-repair-lite mcp), MIT, https://github.com/tidybytetools/json-repair-lite — fixes broken JSON, including text that a language model wrote.io.github.tidybytetools/base64-lite1.0.1, PyPIbase64-lite, stdio (uvx base64-lite mcp), MIT, https://github.com/tidybytetools/base64-lite — encode or decode Base64 for text and local files, with URL-safe and data-URI options.
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.tidybytetools/tidy-byte-tools"
curl "https://api.mcp.github.com/v0.1/servers?search=tidybytetools"
Thank you!
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…