MCP Server Published But Not Visible on github.com/mcp Registry

[Wolfe-Jam]

📌 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):

1. Publish to the open-source MCP Registry first. Your entry should be active and isLatest.
2. Request onboarding here. Adding a new server to github.com/mcp is a manual curation step.
3. After that, new versions sync automatically from the open-source registry. No need to ask again for updates.

Include all of these in your request:

• Registry name (e.g. io.github.you/server or a domain-verified namespace), linked to its registry entry
• Version, active + isLatest
• Package and transport (npm / PyPI / cargo, stdio), or the remote endpoint and auth (streamable HTTP, OAuth / API key)
• Repository
• License
• What it does, in one or two lines
• Verification: the registry curl below, so the values can be checked

Check before you post (read the values from the registry, not from memory):

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=<your-server>"

Check whether you're already listed on GitHub's side:

curl "https://api.mcp.github.com/v0.1/servers?search=<your-server>"

_{Community notes from this thread. Corrections welcome.}

---

Original question (Oct 2025):

Hi community! Looking for clarification on how the GitHub MCP Registry works.
The Situation
We successfully published claude-faf-mcp to GitHub's MCP Registry (Anthropic-approved steward), but it's not appearing on github.com/mcp yet. We're curious about the process.
Quick Details

Server: claude-faf-mcp
Namespace: io.github.Wolfe-Jam
GitHub: https://github.com/Wolfe-Jam/claude-faf-mcp
npm: https://npmjs.com/package/claude-faf-mcp (3,600+ downloads, 800+ weekly)
Status: Published successfully (v2.6.1 via CLI)
Credentials: Official Anthropic MCP steward (PR #2759 merged)

Questions

Is github.com/mcp a curated list (vs automatic sync)?
If curated, what are the selection criteria?
How do we check publication status?
Any feedback on what might help visibility?

Why We Ask
claude-faf-mcp is the first persistent "Project DNA" layer in MCP — helps developers standardize AI context across teams. Visibility on github.com/mcp would help the ecosystem discover and adopt it.
Context

Previously posted: modelcontextprotocol/registry #690
Anthropic registry: ✅ Accepted and merged
Looking for guidance from anyone familiar with the curation process

Thanks for any insights! 🙏

[ghost]

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:

• https://github.com/Wolfe-Jam/claude-faf-mcp
• Add claude-faf-mcp to MCP servers registry modelcontextprotocol/servers#2759

[ghost]

🎉 Update: Additional Milestone Since Posting

.faf is now IANA-registered as application/vnd.faf+yaml

This makes claude-faf-mcp:

• Built on an official Internet-standard format
• Only persistent project context MCP server with IANA-registered
  foundation
• Increased long-term stability and interoperability

Full details: https://www.faf.one/blog/iana-registration

Still curious about the github.com/mcp curation process and happy to
provide any additional info that might help.

[hstaudacher]

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.

[ghost]

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: ***@***.***>

[Wolfe-Jam]

Hey @hstaudacher - following up from November.

Just published both FAF packages to the open source registry today:

• io.github.Wolfe-Jam/claude-faf-mcp v3.3.7
• io.github.Wolfe-Jam/faf-mcp v1.2.1

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.

[Wolfe-Jam]

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 mcp-registry-validator with zero schema and zero lint issues:

Server	Registry	Schema	Lint
claude-faf-mcp	npm + MCP	0	0
faf-mcp	npm + MCP	0	0
grok-faf-mcp	npm + MCP	0	0
gemini-faf-mcp	PyPI + MCP	0	0
rust-faf-mcp	npm + MCP	0	0
wjttc	npm + MCP	0	0

All published via mcp-publisher, all on 2025-12-11 schema, all under namespace io.github.Wolfe-Jam.

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.

[Wolfe-Jam]

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: grok-faf-mcp is a distinct candidate on its own merit — the first MCP server for Grok, URL-based (zero install), just shipped v1.3.1 and registry-coherent. Flagging it specifically, not asking for blanket inclusion.

Is there an ETA for the sync, or is github.com/mcp staying curated? Either answer's fine — closing the loop on this thread.

[trent-j]

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.

[cx-anand-nandeshwar]

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

[Wolfe-Jam]

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 one.faf/* namespace on the OSS registry — one.faf/claude-faf-mcp and one.faf/faf-mcp (both active + latest; my solo io.github.Wolfe-Jam entries deprecated — they served their purpose). So those are the canonical names now if onboarding moves forward. We've also added copilot-instructions emit (so .faf feeds GitHub Copilot directly), and a full GitHub version is in testing.

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. 🙏

[trent-j]

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.

[Wolfe-Jam]

Wow! what amazing news, thank you for your patience and steer, much appreciated.

[Wolfe-Jam]

Thanks again, trent-j 🙏 — two more of the FAF family are now published on the official MCP registry and ready whenever onboarding has room:

• Grok FAF — one.faf/grok-faf-mcp · https://github.com/Wolfe-Jam/grok-faf-mcp
• Gemini FAF — one.faf/gemini-faf-mcp · https://github.com/Wolfe-Jam/gemini-faf-mcp

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.

[edithatogo]

Onboarding request: io.github.edithatogo/fyi-mcp

Following the process clarified in this thread (OSS registry first; github.com/mcp initial onboarding is manual curation; versions sync after onboard):

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 / edithatogo does 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

[AkashGoenka]

Onboarding request: io.github.AkashGoenka/coldstart

Following the OSS-registry-first process described in this discussion:

• Official registry name: io.github.AkashGoenka/coldstart
• Latest version: 2.2.17
• Package: @cstart/coldstart (npm, stdio)
• Repository: https://github.com/AkashGoenka/coldstart
• Website: https://coldstartmcp.dev/
• Documentation: https://coldstartmcp.dev/docs/

coldstart provides self-maintaining codebase memory for AI coding agents: an AST index for exact code navigation plus agent-written notes that flag themselves stale when code changes.

The package includes the required mcpName marker and matching server.json, and the latest version is published to the official MCP Registry.

Please consider onboarding it to the GitHub MCP Registry so future versions can sync automatically. Thank you!

[happy520ai]

Onboarding request: io.github.happy520ai/unified-ai-system

Following the OSS-registry-first and manual-curation process confirmed in this discussion:

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.

[cpellan561]

Onboarding request: to.derive/derive

Following the OSS-registry-first process confirmed in this thread (publish to the open source registry, then request manual onboarding; versions sync after):

Field	Value
Official registry name	to.derive/derive
Latest version	1.0.0 (active, isLatest)
Transport	Remote, Streamable HTTP at https://derive.to/mcp
Auth	OAuth 2.1, PKCE (S256), Dynamic Client Registration
Repository	https://github.com/derive-to/derive
Manifest	https://github.com/derive-to/derive/blob/main/server.json
Website	https://derive.to
Licence	FSL-1.1-ALv2 (converts to Apache 2.0)

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 readOnlyHint / destructiveHint annotations, so annotation-aware clients auto-approve the reads and prompt on the writes.

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:

curl -sS "https://registry.modelcontextprotocol.io/v0/servers?search=to.derive"

returns to.derive/derive v1.0.0, status: active, isLatest: true.

github.com/mcp status (2026-08-12): a search for derive surfaces no card, and https://github.com/mcp/to.derive/derive returns 404.

Could the curation team consider onboarding this so future OSS registry versions sync automatically? Happy to provide any further metadata or validation.

[OlyaTi]

Onboarding request for a server already published to the OSS registry, following the format used earlier in this thread.

• Registry name: io.github.mnemoverse/mcp-memory-server
• Latest version: 0.8.1 (isLatest: true)
• What it is: persistent memory for AI agents, shared across tools: write a memory in one MCP client, recall it in another. Importance-scored writes, associative recall, feedback-tuned ranking, shared memory rooms.
• Remote: https://mcp.mnemoverse.com/mcp (Streamable HTTP, OAuth 2.1 + PKCE, RFC 9728 protected-resource metadata, dynamic client registration; vscode.dev is in the DCR allowlist, and loopback callbacks work for VS Code Desktop)
• Package: npm: @mnemoverse/mcp-memory-server (stdio, API-key auth)
• Repo: https://github.com/mnemoverse/mcp-memory-server (MIT)
• Verification:
  curl "https://registry.modelcontextprotocol.io/v0/servers?search=mnemoverse" returns the entry above; an unauthenticated POST https://mcp.mnemoverse.com/mcp returns 401 with a WWW-Authenticate: Bearer challenge and a resource_metadata pointer, per spec.
• Tool annotations: all ten remote tools carry title plus readOnlyHint/destructiveHint; the two destructive delete tools are deliberately not exposed on the remote endpoint.

Happy to provide a populated test account for review. Thanks for considering.

[rafaelgaspar]

Requesting onboarding for a new server:

Field	Value
Official registry name	io.github.rafaelgaspar/longhorn-mcp
Latest version	0.1.1 (active / isLatest)
Package / transport	npm — longhorn-mcp, stdio (npx -y longhorn-mcp)
Repository	github.com/rafaelgaspar/longhorn-mcp
Manifest	server.json
Documentation	README
License	MIT
Description	MCP server for the Longhorn distributed storage manager API. Full read/write coverage of Longhorn's REST API — volumes, snapshots, backups, backing images, nodes, settings, engine images, recurring jobs, and more — plus a --read-only mode, stdio and Streamable HTTP transports, and an official Helm chart for in-cluster deployment.

OSS registry verification:

curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.rafaelgaspar/longhorn-mcp"

returns the server with "status": "active" and "isLatest": true.

Publishing is automated via GitHub Actions OIDC on every tagged release (.github/workflows/release.yaml), so future Official Registry versions should sync automatically once onboarded. Would appreciate this being added to the GitHub MCP Registry — thanks!

[littlezheng]

Onboarding request: ai.idphoto/mcp (IDPhoto.ai)

Requesting initial onboarding to github.com/mcp and the VS Code MCP gallery. We build and run this server. Values below were read from the registry on 2026-10-20.

Field	Value
Registry name	ai.idphoto/mcp (DNS-verified namespace on idphoto.ai)
Version	0.1.0, active, isLatest: true
Transport	Remote, streamable HTTP at https://mcp.idphoto.ai/mcp
Auth	None required (3 free photos per day). Optional X-IDP-API-Key / X-IDP-API-Secret headers use the caller's own idphoto.ai API quota.
Repository	Hosted service, source is private. Website: https://idphoto.ai
License	Proprietary (hosted by IDPhoto.ai)

What it does: turns a portrait into a compliant passport, visa or ID photo, and looks up 300+ official photo specs. Four tools: make_id_photo, list_photo_specs, get_photo_spec, get_usage.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=ai.idphoto"

Thanks!

[0nitsoga]

Requesting initial GitHub MCP Registry onboarding for KanbanMCP, following the OSS-registry-first, manual-curation process described in this thread. We (Onitsoga Labs) build and run this server.

Field	Value
Registry name	com.kanbanmcp/kanbanmcp
Version	0.1.0, active, isLatest
Namespace	com.kanbanmcp, DNS-verified on kanbanmcp.com
Registry entry	https://registry.modelcontextprotocol.io/v0.1/servers?search=com.kanbanmcp/kanbanmcp
Endpoint	https://kanbanmcp.com/ (Streamable HTTP)
Auth	OAuth 2.1 (PKCE S256, dynamic client registration, client ID metadata documents)
Tools	31, with readOnlyHint / destructiveHint annotations
Repository	Hosted service, source not public
License	Proprietary hosted service (Free plan available)
Docs	https://kanbanmcp.com/docs
Privacy	https://kanbanmcp.com/privacy
Support	https://kanbanmcp.com/contact

What it does: KanbanMCP is a hosted kanban board for AI agents. Agents claim cards, check in while they work, and hand off with structured notes, so the next agent picks up where the last one left off. Briefs, rules and history stay in the board as shared memory across agents. Users sign in once and choose the persona and boards each connection can reach.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.kanbanmcp/kanbanmcp"

[ziyadbasheer]

Onboarding request: app.aide/aide (Aide)

Requesting initial onboarding to github.com/mcp and the VS Code MCP gallery. We build and run this server. Values below were read from the registry on 2026-10-20.

Field	Value
Registry name	app.aide/aide (HTTP-verified namespace on aide.app)
Version	1.0.1, active, isLatest: true
Transport	Remote, streamable HTTP at https://app-api.aide.app/mcp
Auth	OAuth 2.1 with PKCE (S256) and dynamic client registration (RFC 7591), scopes aide:read / aide:write. Unauthenticated requests get 401 with a resource_metadata pointer. VS Code's redirect URIs (http://127.0.0.1:33418, https://vscode.dev/redirect) are allowed.
Repository	https://github.com/aideapp/aide-mcp (install manifests for VS Code, Cursor, Gemini CLI, Claude Code and Codex; the server itself is a hosted service)
License	Proprietary hosted service; the install repo is MIT
Website	https://aide.app/mcp

What it does: lets an assistant work in Aide, an AI customer service platform, as the signed-in teammate: search the knowledge base, look up Shopify orders, read, reply to and update helpdesk conversations, refund or cancel orders within the account's approval limits, and read support analytics.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=app.aide/aide"

[BSalaeddin]

Onboarding request: com.trycaly/caly (Caly)

Follow-up to our Devino Solutions request above. We are adding one server that went live after that comment. We build and run it.

Server	Registry name	Version	Endpoint	Registry entry
Caly	com.trycaly/caly	1.0.0	https://mcp.trycaly.com/mcp	latest

Caly is a scheduling app. The server finds open meeting times; books, reschedules and cancels meetings; and reads event types, bookings and schedules. Like the others, it is a hosted Streamable HTTP server with OAuth 2.1 sign-in (PKCE, dynamic client registration, RFC 9728 protected-resource metadata), with no local package and no API key. The registry entry is active, and the com.trycaly namespace is DNS-verified on the product domain.

[ux-xd]

Request to list superbot on the GitHub MCP Registry

Registry name: gg.superbot/superbot (domain-verified namespace gg.superbot; the proof is served at https://superbot.gg/.well-known/mcp-registry-auth)
Version: 1.1.0 (active, isLatest: true, published 2026-10-20)
Transport: remote streamable-http at https://api.superbot.gg/mcp, no package. Auth is OAuth: the anonymous request answers 401 with WWW-Authenticate: Bearer resource_metadata="https://api.superbot.gg/.well-known/oauth-protected-resource", and the authorization server advertises dynamic client registration and PKCE S256.
Repository: https://github.com/superbot-gg/superbot-mcp
License: MIT

What it does: superbot is your own AI agent. Try it now in your browser, free and with no account: https://superbot.gg/chat. The one tool it exposes is called superbot and covers fax, calls, texts, Gmail drafts, calendar and web search.

Verification:

• Official MCP Registry, listed, active, isLatest: true

  curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=gg.superbot/superbot"
  

• GitHub MCP Registry, not currently listed

  curl "https://api.mcp.github.com/v0.1/servers?search=superbot"
  

Requesting onboarding to github.com/mcp. We understand it is a manual curation step; if anything about the entry should change for it to be considered, tell us and we will change it. Install page: https://superbot.gg/add

[alexechoi]

Requesting onboarding for Concord MCP on github.com/mcp.

• Registry name: io.github.Get-Concord-AI/concord-mcp
• Version: 0.14.1 (active, isLatest)
• Package and transport: npm @concord-ai/concord-mcp, stdio
• Repository: https://github.com/Get-Concord-AI/concord-mcp
• License: MIT
• What it does: Cross-harness communication and shared work-state for AI coding agents, with presence, claims, messaging, handoffs and review packets.
• Verification: curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=concord-mcp" shows 0.14.1 active and isLatest; curl "https://api.mcp.github.com/v0.1/servers?search=concord" returns nothing yet.

Thanks!

[lumman-pro]

Onboarding request: co.lumman/calendar (Multi Calendar)

• Registry name: co.lumman/calendar (domain-verified namespace: DNS TXT on lumman.co)

• Version: 1.2.0, active, isLatest: true

• Remote: Streamable HTTP at https://calendar.lumman.co/mcp. OAuth 2.1 with dynamic client registration; no key or client id is needed, nothing to install.

• Repository: https://github.com/lumman-lab/multi-calendar

• License: MIT for the repository; the hosted server is closed source, run by Lumman Ltd, London, under its terms at https://lumman.co/terms.

• What it does: Outlook.com, Hotmail, Microsoft 365 and Google calendars behind one connector - several accounts at once, one search for free time across all of them. It reads, creates, moves and cancels events and answers invitations; booking links, booking pages and group polls let guests pick a time, and circles find time with colleagues or family. Each account's permissions - seeing events, changing events, and inviting and replying - are set by the person, and Lumman keeps no copy of the calendars.

• Docs: https://lumman.co/mcp/multi-calendar - privacy https://lumman.co/privacy

• Verification:

  curl "https://registry.modelcontextprotocol.io/v0.1/servers/co.lumman%2Fcalendar/versions/latest"
  curl "https://api.mcp.github.com/v0.1/servers?search=lumman"   # currently empty
  

Thanks for curating the list.

[DmitryAnansky]

Onboarding request: com.redocly/mcp (Redocly)

Requesting initial onboarding to github.com/mcp and the VS Code MCP gallery. Redocly builds and runs this server. I read the values below from the registry on 2026-10-20.

Field	Value
Registry name	com.redocly/mcp (namespace verified by DNS TXT on redocly.com)
Version	1.0.0, active, isLatest: true
Remote	Streamable HTTP at https://redocly.com/mcp. No auth, no package.
Tools	discover, execute (read only) and submit-feedback, with readOnlyHint and destructiveHint annotations
Repository	https://github.com/Redocly/redocly-plugin (the Redocly plugin for Claude Code, Codex and Cursor, which uses the same server)
License	MIT
Docs	https://redocly.com/docs/realm/customization/mcp-server/redocly-mcp

What it does: searches and reads the Redocly product docs, guides and blog on redocly.com, and reports a wrong or incomplete page to the Redocly docs team.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.redocly/mcp"
curl "https://api.mcp.github.com/v0.1/servers?search=redocly"

The first returns 1.0.0, active, isLatest: true. The second returns nothing yet.

Thanks!

[andredelgado]

Onboarding request: io.github.andredelgado/continente-mcp (Continente MCP)

Requesting initial onboarding to github.com/mcp. I build and maintain this server. Values below were read from the registry on 2026-10-20.

Field	Value
Registry name	io.github.andredelgado/continente-mcp (GitHub-verified namespace)
Version	0.11.0, active, isLatest: true
Package and transport	npm continentept-mcp, stdio; also a Claude Desktop extension (.mcpb), stdio
Repository	https://github.com/andredelgado/continente-mcp
License	MIT

What it does: Shopping on Continente.pt, Portugal's largest supermarket chain, from an AI assistant: search products with prices per kg or litre and promotions, read ingredients and allergens, build a list from favorites and past orders, and make cart changes that are confirmed by reading the cart back. Checkout and payment stay on the website.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.andredelgado/continente-mcp"
curl "https://api.mcp.github.com/v0.1/servers?search=continente"   # not listed yet

Thanks!

[0xRabbithole]

Onboarding request: pro.postkey/postkey (Postkey)

Requesting initial onboarding to github.com/mcp and the VS Code MCP gallery. Postkey builds and runs this server. Values below were read from the registry on 2026-10-20.

Field	Value
Registry name	pro.postkey/postkey (domain-verified namespace: DNS TXT on postkey.pro)
Version	1.0.0, active, isLatest: true (published 2026-10-20)
Transport	Remote, streamable-http: https://postkey.pro/mcp
Auth	OAuth 2.1 with PKCE (S256), dynamic client registration and client ID metadata documents; unauthenticated requests get 401 with WWW-Authenticate / RFC 9728 metadata
Description	The most agentic DM automation tool. AI agents build Instagram DM automations and schedule posts.
Safety	Sends (replies, turning on an automation, scheduling a post) wait for the user's approval in Postkey by default
Repository	None: hosted service
License	Proprietary
Docs	https://postkey.pro/docs/mcp
Privacy / Terms	https://postkey.pro/privacy · https://postkey.pro/terms
Support	support@postkey.pro

Thank you!

[mailows]

Onboarding request: com.mailows/mailows (Mailows)

Requesting initial onboarding to github.com/mcp. Mailows builds and runs this server. Values below were read from the registry on 2026-10-20.

Field	Value
Registry name	com.mailows/mailows (domain-verified namespace mailows.com)
Version	1.0.0, active, isLatest: true (published 2026-10-19)
Transport	Remote, streamable-http: https://mcp.mailows.com/mcp, no package
Auth	OAuth 2.1 with PKCE (S256). No dynamic client registration; the authorization server supports client ID metadata documents. Unauthenticated requests get 401 with protected-resource metadata.
Tools	7: mail_health, mail_list_inboxes, mail_list_messages, mail_read_message, mail_send_message, mail_prepare_attachment_uploads, mail_upload_attachment_chunk (static server card at https://mcp.mailows.com/.well-known/mcp/server-card.json)
Repository	https://github.com/mailows/mailows-grok-plugin
License	Hosted, closed-source service operated by DW Technology LLC
What it does	Email hosting for people and AI agents: each agent gets its own inbox and can list, read and send mail through scoped, revocable OAuth grants. Free plan with public signup. Also reviewed and listed in Claude's connector directory.
Docs	https://www.mailows.com/mcp-manual

Verification

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.mailows/mailows"   # 1.0.0, active, isLatest
curl "https://api.mcp.github.com/v0.1/servers?search=mailows"                              # 0 results today

Thanks!

[violetclaire]

Onboarding request: io.github.violetclaire/popcorn-mcp (POPCORN MCP)

Please consider POPCORN MCP for initial onboarding to the GitHub MCP Registry, following the OSS-registry-first process described in this discussion.

Field	Published state
Official registry	io.github.violetclaire/popcorn-mcp
Metadata version	0.1.4, active, isLatest: true (checked 2026-10-21 UTC)
Package / transport	npm @violetclaire/popcorn-mcp@0.1.3, stdio
Repository	violetclaire/popcorn-temporal-anchor, packages/mcp
Documentation	MCP README, service catalog and agent docs
License	POPCORN Read-and-Use Terms: custom terms, free sample/checker/client use, with restrictions on software redistribution and independent issuer operation. This is not an MIT/OSI license claim.
Auth / payments	No account or key for local hashing, offline verification, historical samples, or the public catalog. Fresh receipts cost $0.001 USDC on Base. Paid tools default to a dry run; a call must set approve_payment: true, and the local process must have a dedicated payer key in EVM_PRIVATE_KEY. No wallet key is a tool argument.

The published package exposes six tools: popcorn_sample, popcorn_catalog, popcorn_hash, popcorn_verify, popcorn_time, and popcorn_witness. It provides signed time and payload-digest witness receipts. A receipt does not prove action execution or grant authorization. Offline verification requires independently trusted issuer keys; historical samples are not a fresh clock reading.

Validation on 2026-10-21 UTC: the pinned npm package installed and its offline sample passed without payment or network requests during verification; a stdio MCP client discovered all six tools. The source checkout contains a newer seventh tool, popcorn_verify_v2, which is not advertised here as part of npm 0.1.3.

Registry verification:

curl 'https://registry.modelcontextprotocol.io/v0.1/servers/io.github.violetclaire%2Fpopcorn-mcp/versions/latest'

That response reports active/latest metadata 0.1.4 and npm package 0.1.3. GitHub's gallery lookup currently returns 404 Server not found:

curl 'https://api.mcp.github.com/oss/v0.1/servers/io.github.violetclaire%2Fpopcorn-mcp/versions/latest'

Please let us know if the curation team needs any additional metadata or validation. Thank you.

[emviedv]

Onboarding request: com.overlayqa/mcp (OverlayQA)

Requesting initial onboarding to github.com/mcp and the VS Code MCP gallery. OverlayQA builds and runs this server. Values below were read from the registry on 2026-10-21.

Field	Value
Registry name	com.overlayqa/mcp (domain-verified namespace overlayqa.com)
Version	0.6.1, active, isLatest: true (published 2026-10-21)
Transport	Remote, streamable-http: https://api.overlayqa.com/mcp. Also an npm package for local stdio use: @overlayqa/mcp
Auth	OAuth 2.1 with PKCE (S256) and dynamic client registration (https://api.overlayqa.com/mcp/oauth/register). Unauthenticated requests get 401 with protected-resource metadata (/.well-known/oauth-protected-resource/mcp). Scopes: overlayqa:read, overlayqa:write, overlayqa:scan
Tools	31: scan_accessibility, scan_contrast, audit_tokens, scan_and_create_issues, run_auto_review, compare_visual, get_review_result, create_issue, list_issues, get_issue, update_issue, move_issue, verify_issue, get_issue_verifications, list_projects, create_project, list_project_members, list_comments, create_comment, update_comment, delete_comment, get_comment_attachment, list_labels, create_label, rename_label, delete_label, set_issue_label, list_client_reviews, create_client_review, update_client_review, set_client_review_recipients
Repository	https://github.com/OverlayQA/mcp (MIT; the stdio client). The hosted endpoint is operated by OverlayQA
What it does	Design QA for AI coding agents: run WCAG accessibility (axe-core), color-contrast and design-token audits and AI visual reviews on any URL, then file and manage QA issues, comments, labels and client review links in OverlayQA. Free account with public signup (free tier included). Also listed in Claude's connector directory
Docs	https://overlayqa.com/mcp/

Verification

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.overlayqa/mcp"   # 0.6.1, active, isLatest
curl "https://api.mcp.github.com/v0.1/servers?search=overlayqa"                           # 0 results today

Thanks!

[tahercoolguy]

Onboarding request: SAIFS AI — 9 hosted servers under the DNS-verified ai.saifs namespace

Following the OSS-registry-first, manual-curation process confirmed in this thread (publish to the official registry, request initial onboarding, versions sync afterwards). Also sent to partnerships@github.com.

All 9 are remote Streamable HTTP servers, active / isLatest in the official MCP Registry, each linked to its own folder in our public docs repo.

Server	Registry name	Ver	Endpoint	What it does
Customer Intelligence & Segmentation	ai.saifs/customer-intelligence	1.0.2	https://customer-tiering-mcp-latest.saifs.ai/mcp	A/B/C/D customer tiers, at-risk accounts, daily sales call list
Demand Forecasting	ai.saifs/demand-forecasting	1.0.1	https://demand-forecaster-mcp.saifs.ai/mcp	Per-SKU demand forecasts with ranges, incl. slow/intermittent movers
Inventory Intelligence & Optimizer	ai.saifs/inventory-intelligence-optimizer	1.0.1	https://inventory-optimizer-mcp.saifs.ai/mcp	Order quantities, reorder points, overstock, cash tied up in stock
Lead Intelligence	ai.saifs/lead-intelligence	1.0.1	https://lead-scoring-mcp.saifs.ai/mcp	Pipeline conversion odds, value at risk, channel attribution, call queue
Marketing Intelligence & Optimization	ai.saifs/marketing-intelligence	1.0.1	https://marketing-analysis-mcp.saifs.ai/mcp	Channel ROI / budget mix, bundles, A/B verdicts, CAC/LTV
Hiring Fairness & Selection ROI	ai.saifs/hiring-fairness	1.0.1	https://hiring-fairness-mcp.saifs.ai/mcp	Group-level adverse-impact checks and test validity/ROI (never scores individuals)
Media Generator — Images, Videos & Audios	ai.saifs/media-generator-images-videos	1.0.1	https://mcp.saifs.ai/mcp	Images, logos, video, music, songs and text-to-speech for marketing
Synthetic Data — Random User	ai.saifs/synthetic-data-random-user	1.0.1	https://synthetic-mint-mcp.saifs.ai/mcp	Fake user profiles for demos, QA and UI fixtures
Indian Railways IRCTC	ai.saifs/indian-railways-irctc	1.0.1	https://transport-agent-claude.saifs.ai/mcp	Train search, routes, live status, station boards, PNR (info only)

• Publisher: SAIFS AI — https://saifs.ai
• Repository: https://github.com/Saify-Technologies/saifs-ai-mcps-docs (one folder per server with README, full tool list, VS Code mcp.json config and server.json; each server.json links its folder via repository.subfolder)
• Auth: OAuth 2.1 on every server. Unauthenticated requests return 401 with WWW-Authenticate: Bearer and an RFC 9728 resource_metadata pointer; dynamic client registration and PKCE S256 are supported.
• Privacy: https://saifs.ai/privacy_policy
• Data handling: the analytics servers (customer, demand, inventory, lead, marketing, hiring) each offer a local-engine tool for large files, so bulk business data never has to leave the user's machine.

Verification (2026-10-21)

curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=ai.saifs"
→ all 9 servers, status: active, isLatest: true

curl -s "https://api.mcp.github.com/v0.1/servers?search=ai.saifs"
→ {"servers":[],"metadata":{"count":0,"total":0}}

Could the curation team consider onboarding these so future official-registry versions sync automatically? We're happy to provide test accounts, a demo, or any metadata changes needed. Thanks!

[ArthurMillet8]

Hi team, we'd like to request onboarding of our server to the GitHub MCP Registry.

• Registry name: ch.wejob/wejob, active on registry.modelcontextprotocol.io under a DNS-verified namespace: https://registry.modelcontextprotocol.io/v0/servers?search=wejob
• Remote: streamable-http at https://mcp.wejob.ch/mcp. It's public, needs no authentication and is read-only.
• Repository: https://github.com/WeJob-IT/WeJob-MCP (MIT, actively maintained)
• Docs: https://wejob.ch/mcp-wejob

What it does: WeJob is a Swiss job platform with a strong focus on IT roles. The server lets an agent search and read public job offers, training programs and company profiles, with the same filters and sorting as wejob.ch.

Tools: wejob_search_jobs, wejob_get_job, wejob_search_companies, wejob_get_company, wejob_search_formations, wejob_get_formation, plus the standard search and fetch.

Why it fits GitHub users: developers can ask Copilot or any MCP client to find IT jobs or trainings in Switzerland without leaving their editor. The server doesn't touch any private candidate or recruiter data.

Happy to provide anything else you need. Thanks!