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!

[tareq7]

Onboarding request: Muslim Prayer Reminder MCP

Please onboard Muslim Prayer Reminder MCP to the GitHub MCP Registry at https://github.com/mcp.

It is already published in the Official MCP Registry, but GitHub's catalog currently returns no matching entry.

• Registry name: io.github.tareq7/muslim-prayer-mcp
• Official registry version: 1.1.1, verified active and isLatest: true on October 17, 2026.
• Official registry entry: https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.tareq7%2Fmuslim-prayer-mcp
• Remote transport: Streamable HTTP, publicly accessible without authentication.
• Remote endpoint: https://muslim-prayer-mcp.najetareqz.workers.dev/mcp
• Local package: [email protected], npm/npx with stdio transport.
• Repository: https://github.com/tareq7/muslim-prayer-mcp
• License: MIT.
• Website: https://tareq7.github.io/muslim-prayer-mcp/
• Existing ChatGPT plugin: https://chatgpt.com/plugins/plugin_asdk_app_6a9bca660b2c8191a1146aa615cad6f5

The server calculates daily prayer timetables and next-prayer countdowns, checks reminder status, and saves calculation preferences. It supports 12 calculation methods, Shafi/Hanafi Asr conventions, Arabic/English reminder text, and explicit calculation-authority and high-latitude approximation disclosures. Prayer location comes from a supported city, supplied coordinates/timezone, or a saved fixed location; it is not inferred from the connector's IP.

It exposes five tools: get_prayer_status, get_today_prayer_times, get_next_prayer, configure_prayer_preferences, and get_prayer_preferences. The remote tools/list and a Riyadh status request were verified successfully on October 17. Preference configuration writes saved settings; identified status checks can write reminder-deduplication state. Reminder status is returned when queried, rather than delivered as background phone notifications.

Registry verification:

curl 'https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.tareq7%2Fmuslim-prayer-mcp'

The latest result is version 1.1.1 with _meta["io.modelcontextprotocol.registry/official"].status equal to active and isLatest equal to true.

GitHub catalog check:

curl 'https://api.mcp.github.com/v0.1/servers?search=io.github.tareq7%2Fmuslim-prayer-mcp'

This currently returns an empty servers array. Requesting the initial manual onboarding described in the accepted answer here; please let me know if further information is needed for curation.

[georgiynefedov]

Onboarding request: com.synoptic/synoptic (Synoptic)

Please consider Synoptic for github.com/mcp and the VS Code MCP gallery. We operate the hosted server. Values read from the official registry on 2026-10-17.

Field	Value
Registry name	com.synoptic/synoptic (DNS-verified namespace for synoptic.com)
Version	1.0.0, active, isLatest
Remote endpoint	https://mcp.api.synoptic.com/mcp (streamable HTTP)
Auth	OAuth 2.1 with PKCE (S256); Client ID Metadata Documents and dynamic client registration. search, streams_all, get_stream and fetch also work without signing in.
Repository	Hosted, closed-source service; docs at https://docs.synoptic.com/s/mcp/mcp
License	Proprietary hosted service (terms)
What it does	Find, read and publish live news and data feeds: Twitter/X and Telegram monitors, press releases, SEC filings, IPOs, court dockets, economic releases. 70 tools, each with a title and read-only/destructive annotations.

Verification:

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

[hendricius]

Onboarding request: ai.loafy/loafy (Loafy: Sourdough Bread Baking)

Please consider Loafy for github.com/mcp and the VS Code MCP gallery. We operate the hosted server ourselves.

Field	Value
Registry name	ai.loafy/loafy (HTTP-verified namespace on loafy.ai)
Version	1.1.0, active, isLatest: true (checked 17 Oct 2026)
Transport	Streamable HTTP, remote endpoint https://loafy.ai/mcp
Auth	OAuth 2.1 with dynamic client registration and PKCE; guests can connect without an account
Repository	none public (hosted service); docs at https://loafy.ai/claude
License	proprietary hosted service; book content CC BY-SA 4.0
What it does	Sourdough baking: dough calculators, a bake planner, search and read the open book The Sourdough Framework, and with a free Loafy account a personal bake journal, starters and containers. 19 tools, 3 prompts.

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

[oschwald]

Please consider onboarding MaxMindDB to the GitHub MCP Registry.

• Registry name: io.github.oschwald/maxminddb
• Version: 0.3.0, verified as active and isLatest: true.
• Package: public multi-architecture OCI image ghcr.io/oschwald/maxminddb-mcp:0.3.0 (Linux AMD64 and ARM64), using stdio.
• Repository: https://github.com/oschwald/maxminddb-mcp
• License: ISC.

The server queries GeoIP2, GeoLite2, and custom MMDB files for IP locations and network ownership. It supports batch lookups, filtered and resumable network queries, database inspection, comparisons, and database downloads. Users supply existing databases or their own MaxMind credentials. This is an unofficial project and is not endorsed by MaxMind Inc.

Release CI publishes new versions to the official MCP Registry. The registry entry includes Docker launch settings, a persistent database volume, and credential prompts with the license key marked as secret.

Native installations are also available through the universal MCPB, which includes all five supported platform builds and Claude Desktop settings. Repository manifests support Claude, Cursor, and Antigravity.

Verification:

curl 'https://registry.modelcontextprotocol.io/v0.1/servers/io.github.oschwald%2Fmaxminddb/versions/latest'

The server and plugin identifiers are now maxminddb. The repository, executable, and config paths remain maxminddb-mcp.

[mustafaalfredji]

Onboarding request: io.mysocial/mysocial

Please consider Mysocial for onboarding into the GitHub MCP Registry.

Field	Value
Registry name	io.mysocial/mysocial
Latest version	0.1.4 — active, isLatest: true (checked 18 October 2026)
Requested transport	Hosted streamable-http: https://app.mysocial.io/mcp
Authentication	OAuth 2.1 with PKCE and dynamic client registration
Repository	https://github.com/mysocialio/mysocial-intelligence
License	Public plugin/metadata repository: MIT. Hosted service/backend: proprietary.
Documentation	https://mysocial.io/mcp/

Mysocial provides social media intelligence for creators, marketing teams and agencies: content research, Content Memory, ideas and brand context for AI assistants. Platform availability varies by feature and permissions. Free tools/basic context and paid research plans are available.

This request is for the hosted remote endpoint. The official registry entry also carries a legacy npm/stdio package; please do not treat this as a request to install or onboard that local package.

Verification:

curl 'https://registry.modelcontextprotocol.io/v0.1/servers?search=io.mysocial%2Fmysocial'
curl 'https://api.mcp.github.com/v0.1/servers?search=mysocial'

The first currently returns version 0.1.4 as active/latest; the GitHub registry search currently returns no servers. Thank you for considering it.

[FirstClassTree]

Onboarding request: com.shapelessai/shapeless

Please consider ShapelessAI for onboarding into the GitHub MCP Registry. (We first asked in a separate discussion, #3349, before reading the notes at the top of this thread; this comment replaces it.)

Field	Value
Registry name	com.shapelessai/shapeless (domain-verified namespace)
Version	0.3.1, active, isLatest: true
Transport	remote, streamable HTTP: https://shapelessai.com/mcp
Auth	OAuth 2.1 with dynamic client registration and PKCE (S256); an API key as Bearer also works
Repository	https://github.com/FirstClassTree/shapelessai
License	MIT
Website	https://shapelessai.com

What it does: a social media team an agent can call. It drafts, schedules and publishes posts to the user's own connected accounts (LinkedIn, X, Instagram, TikTok, YouTube, Facebook, Threads, Bluesky), and makes the media for them (images, carousels, short video, voiceover). Posts wait for the user's approval unless they ask to publish now; every tool carries readOnlyHint / destructiveHint annotations.

Also listed in the ChatGPT plugin directory (since 2026-10-10) and graded A on Glama.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.shapelessai/shapeless"
curl "https://api.mcp.github.com/v0.1/servers?search=shapeless"   # not listed yet (2026-10-18)

Thanks, the ShapelessAI team

[lumman-pro]

Onboarding request: co.lumman/mail (Multi Mail)

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

• Version: 1.1.2, active, isLatest: true

• Remote: Streamable HTTP at https://mail.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-mail

• 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: Gmail, Outlook.com, Hotmail, Microsoft 365, iCloud and Fastmail mailboxes behind one connector - one search across all of them, and reading, drafting, sending and organising mail in each. Attachments (PDF, scanned pages included, Word, Excel, PowerPoint) are read as text. Each mailbox's permissions - reading, drafts, sending, organising and settings - are set by the person, and Lumman keeps no copy of the mail.

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

• Verification:

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

Thanks for curating the list.

[manikanta9176]

Onboarding request: sh.dflow/mcp

Field	Value
Registry name	sh.dflow/mcp
Version	1.0.0 (status active, isLatest: true)
Transport	streamable HTTP, https://app.dflow.sh/api/mcp, OAuth 2.0 (dynamic client registration, no API keys)
Website	https://dflow.sh
Public repository	https://github.com/dflow-sh/plugin (MIT)
Description	Deploy apps, databases, and services in a dFlow workspace.

Published to the official registry on 2026-10-12. Please onboard it to github.com/mcp so it can show up in the VS Code MCP gallery.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers/sh.dflow%2Fmcp/versions/1.0.0"

[mavrovde]

Onboarding request: de.viafrei/mcp

Please consider ViaFrei for onboarding into the GitHub MCP Registry.

Field	Value
Registry name	de.viafrei/mcp (domain-verified namespace)
Version	2.1.25, status active, isLatest: true
Remote endpoint	streamable-http https://mcp.viafrei.de/mcp, sse https://mcp.viafrei.de/sse
Auth	none (public open data, no API key)
Repository	https://github.com/mavrovde/viafrei-mcp
License	Apache-2.0
What it does	Live German mobility data from official open sources for AI assistants: motorway traffic and roadworks, trains and public transport, parking, EV charging, fuel prices, weather warnings. Read-only, 22 tools, German and English; every answer names its source and licence.

A stdio bridge to the same endpoint is on npm as viafrei (npx viafrei).

Verification:

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

Disclosure: I build ViaFrei; this is my own server. Sergii Mavrov

[Oltramare-AI]

Onboarding request: four Antevo servers (ch.antevo/*)

Please consider four remote servers from Antevo for onboarding into the GitHub MCP Registry. All of them are in the domain-verified ch.antevo namespace (DNS TXT on antevo.ch) and checked active and isLatest: true on 18 October 2026.

Field	The 07:00 Brief	Antevo Executive Brief	Antevo Trademark	Antevo Wealth
Registry name	ch.antevo/0700-brief	ch.antevo/executive	ch.antevo/trademark	ch.antevo/wealth
Version	1.0.0	1.0.1	1.0.1	1.0.1
Remote (streamable HTTP)	https://api.antevo.ch/mcp/0700/mcp	https://api.antevo.ch/mcp/executive/mcp	https://trademark.antevo.ch/mcp	https://api.antevo.ch/mcp/wealth/mcp
Auth	none	none	none for screening; OAuth 2.1 (PKCE, DCR) for the signed-in tools, asked for on first use	OAuth 2.1 with PKCE and dynamic client registration

Shared by all four

• Repository: https://github.com/ANTEVO-CH/antevo-mcp, with connection metadata, install links, and the Cursor, Gemini CLI and Kiro manifests.
• License: the repository is MIT. The hosted services are proprietary, run by Antevo (VestAI LTD).
• Documentation: https://antevo.ch/mcp/

What they do

• The 07:00 Brief: a daily editorial morning read on markets and the world: what moved, what to watch, the Risk Radar and sector notes. No account.
• Antevo Executive Brief: markets, macro history and world events, with the dated edition behind every answer. No account.
• Antevo Trademark: screens a brand name across 50+ national and regional trademark registers, with each office's opposition window. Signed in: your watchlist, conflicts, deadlines and holder investigations.
• Antevo Wealth: a household's own balance sheet (net worth, holdings, exposure, risk, real assets). It records holdings only after the user approves each change, and it never trades.

Verification

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=ch.antevo"
curl "https://api.mcp.github.com/v0.1/servers?search=ch.antevo"   # 0 today

Thank you. Contact: [email protected]

[sidgthub]

Onboarding request: Status Is Down (com.statusisdown/mcp )

• Registry name: com.statusisdown/mcp (DNS-verified namespace)
• Version: 1.0.0, active + isLatest
• Transport and auth: remote streamable HTTP at https://statusisdown.com/api/mcp, OAuth 2.0 with Dynamic Client Registration
• Repository: hosted service; source is not public
• License: proprietary hosted service, free plan available
• What it does: Read-only outage intelligence for AI agents: live service status, outage report history, geography and spike detection. Six read-only tools; no write actions.
• Docs: https://statusisdown.com/business/mcp
• Verification:

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

[9-bot]

Onboarding request: br.com.9bot/mcp

Published to the official MCP Registry first (domain-verified namespace); now requesting onboarding to github.com/mcp. Values below were read from the registry today.

Field	Value
Official registry name	br.com.9bot/mcp
Version	1.0.0 (active, isLatest)
Remote	Streamable HTTP at https://mcp.9bot.com.br/mcp
Auth	OAuth 2.1 with PKCE (S256) and dynamic client registration; scopes 9bot.read_only and 9bot.full_access. Metadata at https://mcp.9bot.com.br/.well-known/oauth-authorization-server
Repository	https://github.com/9-bot/mcp
License	MIT (public metadata and docs; the hosted service is operated by 9bot)
Website / docs	https://9bot.com.br/en/ · https://9bot.com.br/en/9bot-docs/
Privacy / Terms	https://9bot.com.br/en/privacy-policy/ · https://9bot.com.br/en/terms-of-use/
Support	[email protected]

What it does: lets AI assistants manage, automate and analyze WhatsApp groups, communities and channels through a 9bot account. Requires a 9bot subscription (7-day trial available).

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=br.com.9bot"
curl "https://api.mcp.github.com/v0.1/servers?search=9bot"   # currently 0 results

Happy to adjust and re-publish anything if needed. Thanks!

[DevaOnBreaches]

Onboarding request: com.xposedornot/xposedornot (XposedOrNot)

Please consider XposedOrNot for github.com/mcp and the VS Code MCP gallery. We run the hosted server and the breach index behind it. Values read from the official registry on 2026-10-19.

Field	Value
Registry name	com.xposedornot/xposedornot (DNS-verified namespace on xposedornot.com)
Version	2.0.0, active, isLatest: true
Transport	remote, streamable HTTP at https://api.xposedornot.com/mcp
Auth	none (public, read-only data)
Repository	https://github.com/XposedOrNot/XposedOrNot-API
License	MIT
Docs	https://xposedornot.com/mcp

What it does: XposedOrNot data breach lookups for agents. Check whether an email appears in known breaches, read its breach history, list breaches by company domain or breach ID, and get breach exposure counts for a domain, plus index metrics and recent breaches. Six read-only tools, each with a title and readOnlyHint annotation. Never returns passwords.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.xposedornot"
curl "https://api.mcp.github.com/v0.1/servers?search=xposedornot"   # 0 results today

Disclosure: I run XposedOrNot. Thanks for curating the list.

[andreibesleaga]

Onboarding request: io.github.andreibesleaga/agentic-system-core
Published in the MCP Registry (version 1.0.0). Local stdio server, npm package agentic-system-core, run as agentic-system-core mcp <bundle_path>. It reads a folder of Markdown notes and writes nothing.
Repository: https://github.com/andreibesleaga/agentic-system-core. I maintain it.

[sergei-gulev]

Onboarding request: ai.mailbeast/mailbeast (MailBeast)

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

Field	Value
Registry name	ai.mailbeast/mailbeast
Version	1.0.1 (active, isLatest: true)
Transport	remote, Streamable HTTP at https://mcp.mailbeast.ai/mcp
Auth	OAuth 2.1 (Client ID Metadata Document and dynamic client registration, PKCE S256); the user picks read-only or read + write on the consent screen
Website	https://mailbeast.ai
Docs	https://developer.mailbeast.ai/mcp-server
Repository	none: hosted service by Mark-Digital, LLC, source is not public
License	Proprietary
Description	Cold email outreach in MailBeast: campaigns with A/B sequences, leads, sending mailboxes and warmup, reply inbox and campaign analytics.

Check (unauthenticated request returns 401 with OAuth discovery):

curl -si -X POST https://mcp.mailbeast.ai/mcp -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'