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!

[isaacaskew]

Onboarding request: VenuNite Events

Please onboard VenuNite Events into the GitHub MCP Registry.

• Registry name: io.github.isaacaskew/venunite-events
• Version: 0.3.3, confirmed active and isLatest: true on October 24, 2026.
• Registry record: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.isaacaskew%2Fvenunite-events/versions/0.3.3
• Remote endpoint: https://mcp.venunite.com/v1/mcp/ — Streamable HTTP. Event search requires no signup, API key, or local installation. The optional ticket-handoff tool requires a VenuNite API key and explicit user continuation to an external seller; it does not purchase or reserve tickets.
• Public repository: https://github.com/isaacaskew/venunite-events — client configurations, setup documentation, and the published server manifest.
• License: MIT for the public client configuration package. The hosted service and event data remain subject to VenuNite's service terms and source rights.
• What it does: Searches US concerts, comedy, theater, trivia, festivals, community events, and family activities by location, dates, interests, and budget. Returns event details, VenuNite pages, and available original source links. Coverage varies by location.
• Access: Free personal search with a 90-day lookahead; paid plans for commercial and bulk use. Current limits: https://venunite.com/developers/mcp

Verification:

curl 'https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.isaacaskew%2Fvenunite-events&version=latest'

An anonymous live check on October 24 successfully initialized the server, discovered both tools, and returned three events from search_events. GitHub's registry search currently returns no matching server. Thank you for considering the listing.

[AlexGrona]

Onboarding request: Velox TriFit

Please consider onboarding Velox TriFit to github.com/mcp and the VS Code MCP gallery. We maintain this service under Velox-XR.

Correction, 24 October 2026: this existing request now points to the current unified MCP connection. The initial 1.1.0 publication selected the legacy documentation-only endpoint; version 2.0.0 supersedes it under the same registry identifier. This is not a second listing.

• Registry name: io.github.Velox-XR/velox-trifit-developer
• Version/status: 2.0.0, active, isLatest: true; independently verified after publication at 2026-10-24T14:35:07Z.
• Remote: Streamable HTTP at https://studio.v3lox.com/partner/trifit/mcp; no local package required.
• Authentication/capabilities: five public guidance tools require no account or key. Thirteen account/guest tools require OAuth and user consent, including photo upload and virtual try-on. The full server is not read-only; permissions and allowance still apply.
• Repository: https://github.com/Velox-XR/trifit-partner-api-example — SDK examples, client configurations, skills and manifest; the MCP service is hosted.
• License: MIT for the public repository; hosted services have separate terms.
• Website: https://studio.v3lox.com/partner-api

The server provides official DressMe API documentation, SDK examples and backend-integration guidance for web/mobile developers, alongside authenticated TriFit capabilities. Coding-agent configurations restrict documentation tasks to four public tools: search, fetch, get_integration_example and get_partner_access_requirements. The additional public tool is get_partner_application_guide.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.Velox-XR%2Fvelox-trifit-developer/versions/2.0.0"
curl "https://api.mcp.github.com/v0.1/servers?search=velox-trifit"

Native Codex CLI and GitHub Copilot CLI each passed all four documentation calls against this current endpoint on 24 October 2026, with no TriFit login, account access, uploads or generation. The successful guarded publication workflow also checked the 18-tool authentication metadata and repeated the four anonymous calls: https://github.com/Velox-XR/trifit-partner-api-example/actions/runs/40103119691

These checks do not establish VS Code UI, hosted Copilot mixed-auth compatibility or authenticated generation. GitHub curated onboarding remains pending; official registry publication is not a claim of GitHub approval. Thank you for considering the listing.

[antonbaider]

Onboarding request: io.github.getremcp/docsy

Please consider Docsy for inclusion in the GitHub MCP Registry (GitHub.com / VS Code / Copilot).

Field	Details
Official MCP Registry ID	io.github.getremcp/docsy
Version	1.0.9, current registry release
Transport	Remote Streamable HTTP
MCP URL	https://docsy.remcp.site/mcp/registry
Authentication	OAuth 2.1; unauthenticated 401 is expected
Public repository	https://github.com/getremcp/docsy-plugin
Documentation	https://github.com/getremcp/docsy-plugin/blob/main/docs/GETTING-STARTED.md and https://docsy.remcp.site/docs
License	MIT (public plugin)
What it does	Read-only, source-cited current and version-specific documentation for developer libraries, frameworks and SDKs
MCP tools	resolve-library-id, list-library-versions, query-docs, search, fetch

Docsy is published in the official MCP Registry under the organization-owned getremcp namespace. Please note the public plugin repository is the release distribution; the hosted indexing infrastructure is separate.

Maintainer: @antonbaider.

[micthiesen]

Hi, I maintain artifacts.boo. Could you consider it for the GitHub MCP Registry?

• Official Registry: boo.artifacts/artifacts, v1.0.0, active and latest: https://registry.modelcontextprotocol.io/v0.1/servers/boo.artifacts%2Fartifacts/versions/1.0.0
• Remote Streamable HTTP: https://{workspace}.artifacts.boo/mcp. The user creates a hosted workspace, then uses its address with OAuth sign-in or a workspace agent token.
• Repository: https://github.com/micthiesen/artifacts.boo
• License: FSL-1.1-ALv2, source-available, with each release converting to Apache 2.0 after two years.
• Agents publish interactive pages; people comment, approve or fill in forms, and the agent reads their answers.
• Hosted setup: https://artifacts.boo/help

GitHub's Registry search for boo.artifacts returned no entries on 24 October. Does this workspace-template setup fit your curation requirements?

[usamaejaz]

Onboarding request: io.github.socialbu/socialbu

Please consider SocialBu for the GitHub MCP catalog. SocialBu's official hosted MCP server lets users create and schedule social posts, manage connected accounts and queues, read analytics, and work with automations, inbox conversations, and social listening after authorizing their SocialBu account.

Field	Value
Official Registry name	io.github.socialbu/socialbu
Active latest version	1.0.3 (Registry record)
Transport	Streamable HTTP
Endpoint	https://socialbu.com/mcp
Authentication	OAuth 2.0 with dynamic client registration; users authorize in SocialBu
Repository	https://github.com/socialbu/socialbu-agent
Manifest	https://github.com/socialbu/socialbu-agent/blob/main/server.json
Documentation	https://socialbu.com/mcp-server
Package license	MIT
Contact	[email protected]

The public repository contains client manifests and reusable agent instructions; the server is hosted by SocialBu. A SocialBu account is required. The existing Registry identity is active and marked isLatest, and future releases publish updates under that same identity.

[SaiSatya16]

Requesting onboarding to github.com/mcp for a remote server, following the format in the "Update, Oct 2026" note above.

• Registry name: cloud.adcopilot/adcopilot (domain-verified for adcopilot.cloud): https://registry.modelcontextprotocol.io/v0.1/servers?search=cloud.adcopilot

• Version: 1.0.0, active, isLatest

• Remote endpoint and auth: https://mcp.adcopilot.cloud/mcp, Streamable HTTP, OAuth 2.1 with dynamic client registration and PKCE (S256). No API key.

• Repository: https://github.com/AtromxIntelligence/adcopilot-claude-plugin

• License: MIT for that repository (the Claude Code plugin that bundles the connector). The hosted service is a commercial product under https://adcopilot.cloud/terms.

• What it does: Google Ads, GA4, Search Console and Tag Manager for AI assistants. Every change is proposed first.

• Docs: https://adcopilot.cloud/docs/

• Verification:

  curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=cloud.adcopilot"
  

Publisher: Atromx Intelligence Private Limited, [email protected].

[sirmrdrgod]

Onboarding Request | Requesting onboarding to github.com/mcp for a local MCP server

Field	Value
Registry name	io.github.Wallet-Wall/walletwall
Official Registry	https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.Wallet-Wall/walletwall
Version	0.2.0, active, isLatest
Package	mcpb
Transport	Local stdio
Repository	https://github.com/Wallet-Wall/walletwallrus-copilot
License	Apache-2.0
Release	https://github.com/Wallet-Wall/walletwallrus-copilot/releases/tag/v0.2.0
What it does	Read-only stablecoin evidence analysis for source authority, freshness, finality, conflicts, provenance, deployment identity, and deterministic vault technical-readiness evaluation.
Safety model	Non-custodial and read-only. Does not hold keys, request seed phrases, sign or broadcast transactions, move funds, or provide trading or investment advice.

Verification

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.Wallet-Wall/walletwall"

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

The first query returns the current Official MCP Registry record. The second is expected to return no GitHub MCP Registry result until initial onboarding is completed.

Onboarding request

Please onboard io.github.Wallet-Wall/walletwall into the GitHub MCP Registry so WalletWall can be discovered and installed through github.com/mcp and downstream GitHub MCP discovery surfaces.

If additional metadata, validation evidence, packaging changes, or compatibility checks are required for curation, please let us know and we’ll provide them.

Publisher: Wallet-Wall
Contact: sirmrdrgod

[bfzli]

Onboarding request: sh.nextmail/mcp

Please consider Nextmail for the GitHub MCP Registry (github.com/mcp and the VS Code MCP gallery). Nextmail's official hosted MCP server lets an agent work in the user's Nextmail mailbox once they authorize it: read and search email, draft and send replies, and keep contacts and calendars up to date.

Field	Value
Official Registry name	sh.nextmail/mcp (domain-verified namespace)
Version	1.0.4, active, isLatest: true
Transport	Streamable HTTP
Endpoint	https://api.nextmail.sh/mcp
Authentication	OAuth 2.1 with PKCE and dynamic client registration; an unauthenticated request gets a 401 with the protected resource metadata
Repository	https://github.com/nextmailhq/mcp
Manifest	https://github.com/nextmailhq/mcp/blob/main/server.json
Documentation	https://nextmail.sh/docs/mcp/overview
License	MIT

Verification:

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

GitHub's registry search for nextmail returned no entries on 25 October 2026. Thank you for considering it.

[ivanaka]

Onboarding request: com.pondchat/pondchat

Field	Value
Registry name	com.pondchat/pondchat
Version	1.0.0 (active, isLatest: true in the official registry)
Transport	streamable-http — https://pondchat.com/api/mcp
Repository	https://github.com/ivanaka/pondchat (MIT)
Description	Ephemeral, no-signup P2P video/text chat rooms — agents can mint room links for humans and read/write room chat.
Homepage	https://pondchat.com
Docs	https://pondchat.com/docs/api/mcp.md

[steven-wu-nexrex]

Onboarding request: ai.nexrex/nexrex

Please consider NexRex for github.com/mcp. NexRex's official hosted MCP server lets a runner or coach work with their NexRex account after authorizing it: review activities, recovery and training plans and propose plan changes; coaches can also look up their roster and draft plans for athletes.

Field	Value
Official Registry name	ai.nexrex/nexrex (domain-verified namespace)
Version	1.0.0, active, isLatest: true
Transport	Streamable HTTP
Endpoint	https://mcp.nexrex.ai/mcp
Authentication	OAuth 2.1 with PKCE (S256), Client ID Metadata Documents; no API key
Repository	None. NexRex is a hosted commercial service and the server is not open source
License	Proprietary (Terms)
Docs	https://docs.nexrex.ai/api-reference/mcp-server
Support	[email protected]

Verification:

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

[ErikThiart]

Onboarding request: za.co.simcloud/simcloud

Please consider adding SIMcloud to the GitHub MCP Registry. It is already published in the official MCP Registry:

• Name: za.co.simcloud/simcloud
• Version: 0.2.0 — active, isLatest: true (verified 25 October 2026)
• Transport: Remote Streamable HTTP
• Endpoint: https://simcloud.co.za/api/mcp.php
• Authentication: OAuth with PKCE S256; customers connect their own SIMcloud accounts
• Documentation: https://simcloud.co.za/api/ai.html
• Public integration repository: https://github.com/ErikThiart/simcloud-codex-plugin — MIT licensed

SIMcloud connects AI clients to South African airtime, data bundles, SMS, VAS vouchers, prepaid electricity, wallet balance and network lookup. Purchases and messaging use the connected customer's own account.

Source disclosure: The hosted server implementation is private. The official registry currently references https://github.com/ErikThiart/simcloud, which is a private repository. The public repository linked above contains the integration/plugin package; its MIT licence applies to that package.

Registry verification:

curl -sS 'https://registry.modelcontextprotocol.io/v0.1/servers?search=za.co.simcloud%2Fsimcloud'

GitHub registry search currently returns no SIMcloud entry. Please consider onboarding the existing server so future versions can sync from the official registry. Thank you.

[aadilghani1]

Onboarding request: io.github.Pushary/pushary

Pushary is a remote human-in-the-loop server: an agent asks a person, and the person answers from a push notification on their phone (approve, choose an option, or type a reply).

Field	Value
Registry name	io.github.Pushary/pushary
Version	1.5.2 (in the official MCP Registry since June 2026)
Transport	Streamable HTTP at https://pushary.com/api/mcp/mcp
Auth	OAuth (401 with resource_metadata), or an API key
Repository	https://github.com/Pushary/pushary-skill
Docs	https://pushary.com/docs/agents

I've also emailed [email protected]. Thanks!

[wm2]

Onboarding request: io.github.app-kit-dev/mcp

Please consider App-Kit for github.com/mcp. It is a hosted remote MCP server for website SEO audits, text readability and grammar checks, image conversion/compression and PDF ↔ images. It works anonymously with a free tier; a free token (no email) raises the limits.

Field	Value
Registry name	io.github.app-kit-dev/mcp
Version	0.1.3 — active, isLatest: true (checked 25 October 2026)
Transport	Remote Streamable HTTP, stateless: https://mcp.app-kit.dev/mcp
Auth	None required (anonymous free tier); optional Authorization: Bearer mcpf_... free token
Repository	https://github.com/app-kit-dev/mcp (docs, client configs, server.json)
License	MIT (repository)
Homepage	https://app-kit.dev/mcp
What it does	SEO audit (400 checks, 0–100 score, top losses), text check (readability, keyword stuffing, grammar EN/RU), image convert/compress to WebP/AVIF, PDF to images and images to PDF

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=app-kit"
curl "https://api.mcp.github.com/v0.1/servers?search=app-kit"   # currently empty

Thanks!

[seankarltonlee]

Requesting onboarding for TickerMint.

• Registry name: io.github.seankarltonlee/tickermint, v1.0.1 (active, isLatest)
• Remote: streamable HTTP at https://api.tickermint.cards/mcp, no auth, read-only (every tool has readOnlyHint true)
• What it does: daily market prices for trading cards (Pokemon, One Piece, Lorcana, Riftbound, Yu-Gi-Oh, Gundam), price history since February 2024, set totals and cost to complete, movers, record highs and lows, sealed product prices. 11 tools; every result carries its source, date and the page URL to cite.
• Docs: https://tickermint.cards/developers
• Terms: https://tickermint.cards/legal

Thanks for considering it.

[arach]

On behalf of Hudson Kit, please onboard Arc to the GitHub MCP Registry.

Arc gives agents tools to author, validate, lay out, render, and diff architecture diagrams as code. It exposes 10 tools and 3 resources, including SVG, PNG, HTML, ASCII, and animation export.

• Registry name: io.github.hudsonkit/arc
• Version: 0.14.1 — active and latest in the official MCP Registry.
• Package: @hudsonkit/[email protected]
• Transport: local stdio, launched with npx -y @hudsonkit/[email protected]. Node.js 22+; no authentication or API key required.
• Repository and setup: hudsonkit/arc — packages/mcp
• Website: hudsonkit.com/arc
• License: MIT

PNG export requires local Chrome/Chromium; GIF/MP4 export also requires ffmpeg. This listing uses the published stdio server, not a hosted endpoint.

Registry verification:

curl 'https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.hudsonkit/arc'