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!

[etienne-tillier]

Onboarding request: com.mybestsim/esim-comparator (MyBestSim eSIM comparator)

Published to the official MCP Registry first (DNS-verified namespace on mybestsim.com); requesting onboarding to github.com/mcp and the VS Code MCP gallery. Values read from the registry on 2026-10-19.

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.

[bersimao]

Onboarding request: io.github.bersimao/b1-mcp-server

Published to the official MCP Registry first; requesting onboarding to github.com/mcp. Values read from the registry on 2026-10-19.

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.

[hasantoprakkaya]

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.

• Official registry: io.sociality/sociality-mcp
• Version/status: 0.0.1, active, isLatest: true
• Transport: remote Streamable HTTP at https://api.sociality.io/mcp
• Authentication: OAuth 2.0 with dynamic client registration; scope mcp:use
• Repository: https://github.com/socialityio/sociality-mcp
• License: MIT for the public registry metadata/documentation repository; the hosted service is operated by Sociality.io.
• Product / docs: https://sociality.io/mcp · https://sociality.io/docs

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!

[asherdale]

onboarding request: com.omnara/omnara (Omnara)

requesting initial onboarding to github.com/mcp and the VS Code MCP gallery. we (Omnara, YC S25) build and run this server.

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"

[cloudmanic]

Onboarding request: my.harbor/harbor (Harbor Notes)

Harbor is a notes app made by Cloudmanic Labs. We run this server ourselves. Values below were read from the registry on 2026-10-19.

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.

[kirkwat]

Onboarding request: io.github.speedyapply/jobspy (JobSpy)

Published to the official MCP Registry first; requesting onboarding to github.com/mcp and the VS Code MCP gallery. Values read from the registry on 2026-10-20.

Field	Value
Registry name	io.github.speedyapply/jobspy
Version	1.4.0-1, active, isLatest
Package and transport	PyPI mcp-jobspy, stdio, run as uvx mcp-jobspy@latest
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"

[eatmorespinach]

Requesting onboarding for Clerk's official MCP server to github.com/mcp.

• Registry name: io.github.clerk/mcp-server
• Version: 0.1.0, active + isLatest
• Transport: remote, streamable HTTP at https://mcp.clerk.com/mcp, OAuth
• Repository: hosted service, no public source. Docs: https://clerk.com/docs/guides/ai/mcp/clerk-mcp-server
• License: proprietary (hosted by Clerk)
• What it does: gives AI coding assistants Clerk SDK snippets and setup guides, and lets them manage Clerk apps, users, and domains.
• Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.clerk/mcp-server"

[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!