Repository navigation
Replies: 307 comments 13 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:
|
| Field | Value |
|---|---|
| Official Registry name | ai.nexrex/nexrex (domain-verified namespace) |
| Version | 1.0.0, active, isLatest: true |
| Transport | Streamable HTTP |
| Endpoint | https://mcp.nexrex.ai/mcp |
| Authentication | OAuth 2.1 with PKCE (S256), Client ID Metadata Documents; no API key |
| Repository | None. NexRex is a hosted commercial service and the server is not open source |
| License | Proprietary (Terms) |
| Docs | https://docs.nexrex.ai/api-reference/mcp-server |
| Support | support@nexrex.ai |
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=ai.nexrex"
Onboarding request:
|
|
Onboarding request: io.github.Pushary/pushary Pushary is a remote human-in-the-loop server: an agent asks a person, and the person answers from a push notification on their phone (approve, choose an option, or type a reply).
I've also emailed partnerships@github.com. Thanks! |
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | io.github.app-kit-dev/mcp |
| Version | 0.1.3 — active, isLatest: true (checked 25 October 2026) |
| Transport | Remote Streamable HTTP, stateless: https://mcp.app-kit.dev/mcp |
| Auth | None required (anonymous free tier); optional Authorization: Bearer mcpf_... free token |
| Repository | https://github.com/app-kit-dev/mcp (docs, client configs, server.json) |
| License | MIT (repository) |
| Homepage | https://app-kit.dev/mcp |
| What it does | SEO audit (400 checks, 0–100 score, top losses), text check (readability, keyword stuffing, grammar EN/RU), image convert/compress to WebP/AVIF, PDF to images and images to PDF |
Verification:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=app-kit"
curl "https://api.mcp.github.com/v0.1/servers?search=app-kit" # currently empty
Thanks!
|
Requesting onboarding for TickerMint.
Thanks for considering it. |
|
On behalf of Hudson Kit, please onboard Arc to the GitHub MCP Registry. Arc gives agents tools to author, validate, lay out, render, and diff architecture diagrams as code. It exposes 10 tools and 3 resources, including SVG, PNG, HTML, ASCII, and animation export.
PNG export requires local Chrome/Chromium; GIF/MP4 export also requires ffmpeg. This listing uses the published stdio server, not a hosted endpoint. Registry verification: curl 'https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.hudsonkit/arc' |
Onboarding request:
|
| Field | Value |
|---|---|
| Registry name | io.github.brekkylab/backlot |
| Version | 0.1.0, active, isLatest: true |
| Package and transport | PyPI backlot, local stdio: uvx --with backlot[mcp]==0.1.0 backlot@0.1.0 mcp |
| Auth | None. If no Backlot server is running, it starts one over the bundled corpus. --user <email> answers as that person, under the per-document ACL. |
| Repository | https://github.com/brekkylab/backlot |
| License | Apache-2.0 |
Verification:
curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.brekkylab/backlot"
curl -s "https://api.mcp.github.com/v0.1/servers?search=io.github.brekkylab/backlot" # currently emptyThanks!
Onboarding request: Email Validation (org.email-validation/validate)Please consider onboarding Email Validation to github.com/mcp and the VS Code MCP gallery. It is already published in the Official MCP Registry.
What it does: Check email addresses from your AI client, one at a time or a whole list: each result comes with a status, a reason and what to do next. Unknown results are free. Verification: The Official Registry check returns org.email-validation/validate v1.0.0, active and latest. The GitHub Registry check returned 0 servers on October 25, 2026, and a search on github.com/mcp found no entry for Email Validation. Please consider onboarding it so future Official Registry versions can sync automatically. Thank you! |
Onboarding request: HODDS —
|
| Field | Value |
|---|---|
| Publisher | VORAN |
| Registry name | ai.hodds/hodds |
| Official entry | Version 0.4.0 / latest |
| Version / status | 0.4.0 — active, isLatest: true, checked 26 October 2026 at 07:01 UTC |
| Transport | Remote Streamable HTTP at https://hodds.ai/mcp |
| Authentication | Five public read tools require no token. Public send_feedback writes feedback. Thirteen account tools require an organisation bearer token. |
| Repository | Hosted service with a private implementation; no public source repository. Public documentation and metadata are linked below. |
| License | CC BY 4.0 for the published catalogue and discovery data, as specified in terms, section 4.3. This is not a source-code license. |
| Website / documentation | hodds.ai / Connection guide |
| Manifest / privacy | server.json / Privacy |
| Support | contact@hodds.ai |
Verification:
curl 'https://registry.modelcontextprotocol.io/v0.1/servers/ai.hodds%2Fhodds/versions/latest'
curl 'https://api.mcp.github.com/v0.1/servers?search=hodds'The official entry is active and latest. GitHub's registry search returned zero entries on 26 October 2026 at 07:01 UTC.
Please let us know whether the public documentation and hosted endpoint are sufficient for your curation process, or whether a public integration/documentation repository is required.
Thank you for considering HODDS.
|
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:
|

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…