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!

[podonos-eunseo]

Onboarding request: ai.onepin/onepin

Please consider Onepin for github.com/mcp and the VS Code MCP gallery. We run the
server. Values below were read from the registry and the live endpoint on 2026-10-13.

Field	Value
Registry name	ai.onepin/onepin (domain-verified namespace — DNS TXT on the onepin.ai apex)
Version	1.0.1, active, isLatest: true
Package / transport	Remote only — Streamable HTTP at https://mcp.onepin.ai
Auth	OAuth 2.1, no API key. RFC 9728 protected-resource metadata at /.well-known/oauth-protected-resource; authorization server https://clerk.onepin.ai with dynamic client registration (/oauth/register) and PKCE (S256). Every request requires a token, including initialize.
Repository	https://github.com/podonos/onepin-mcp (MIT) — client configuration and the registry entry. The server itself is a hosted service and its source is not public.
Documentation	https://docs.onepin.ai
What it does	AI Voice Production Agent: picks from 30+ TTS models, fixes pronunciation, validates every line.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=ai.onepin/onepin"
curl "https://mcp.onepin.ai/.well-known/oauth-protected-resource"

[KaracaTR]

Onboarding request: io.github.coredence/coredence

Please consider Coredence for github.com/mcp and the VS Code MCP gallery. Values below were read from the registry on 2026-10-13.

Field	Value
Registry name	io.github.coredence/coredence
Version	1.9.6, active, isLatest: true
Package / transport	mcpb package, stdio (local; no remote endpoint, no auth)
Repository	github.com/coredence/coredence — docs and manifests; also an Agent Plugin (plugin.json + mcp.json) that starts coredence mcp
License	Proprietary, free to use (coredence.com/license)

What it does: gives the assistant the rules a developer actually works by, distilled from their own Claude Code, Cursor and Codex sessions, commits and notes, with every rule linked to the moments it came from. Five read-only tools: identity, rules, evidence, axes, topics. The server opens the identity database read-only and makes no network requests.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.coredence/coredence"

Not yet listed on GitHub's side (api.mcp.github.com search for coredence returns 0).

[Izzy-Gottz]

Onboarding request: finance.aggregate/aggregate

Please consider Aggregate for github.com/mcp and the VS Code MCP gallery. We run the server. Values below were read from the registry and the live endpoint on 2026-10-13.

Field	Value
Registry name	finance.aggregate/aggregate (domain-verified namespace: DNS TXT on aggregate.finance)
Version	0.1.0, active, isLatest: true
Package / transport	Remote only: Streamable HTTP at https://app.aggregate.finance/mcp
Auth	OAuth 2.1 with PKCE and dynamic client registration; RFC 9728 protected-resource metadata at /.well-known/oauth-protected-resource/mcp. A bearer key for clients without OAuth
Repository	Open-sourcing at launch (AGPL-3.0), later this month; the registry entry gets the repository and an npm package in 0.1.1
License	AGPL-3.0
What it does	Gives an AI a company's finances in one reconciled ledger: banks, cards, payments, invoices, bills, payroll and the cap table, across several companies plus a private personal space. It can't move money; the user picks which companies and kinds of data each AI sees.
Contact	support@aggregate.finance

Verification:

curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=finance.aggregate/aggregate"

[pyungjae9492]

Onboarding request: Neopress (ai.neopress/mcp)

Following the process in this thread, I'd like to request onboarding of a remote server that is already published on the open-source MCP Registry.

Registry name	ai.neopress/mcp (DNS-verified neopress.ai namespace)
Version	1.0.1, active and isLatest
Transport	Remote Streamable HTTP, https://mcp.neopress.ai/mcp
Auth	OAuth 2.1 with PKCE (RFC 9728 protected-resource metadata, dynamic client registration)
Repository	Closed source; the hosted endpoint is operated by inblog Inc.
License	Proprietary hosted service
Website	https://neopress.ai
Support	https://app.neopress.ai/support

What it does

Neopress is the AI website builder for SEO, GEO, and growth. Connect it to Claude, ChatGPT, Cursor, or any MCP client to create and edit pages, run a multilingual CMS with collections and forms, publish to your live site, and ask what's working with built-in analytics and Google Search Console data. Every action stays within the sites, roles, and plan of the signed-in account. Tools carry read-only and destructive annotations.

Example prompts:

• Create a landing page for our spring campaign and publish it after I review it.
• Add Korean translations for our three latest blog entries.
• Which pages brought the most visitors last week, and what should I improve next?

Verification

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

The same server has also been submitted to the OpenAI Plugins Directory and the Claude Connectors Directory. Happy to provide a review account or anything else the curation process needs.

[pyungjae9492]

Onboarding request: Inblog (ai.inblog/mcp)

Following the process in this thread, I'd like to request onboarding of a remote server that is already published on the open-source MCP Registry.

Registry name	ai.inblog/mcp (domain-verified inblog.ai namespace)
Version	0.1.1, active and isLatest
Transport	Remote Streamable HTTP, https://inblog.ai/api/mcp
Auth	OAuth 2.1 with PKCE (RFC 9728 protected-resource metadata, dynamic client registration)
Repository	Closed source; the hosted endpoint is operated by inblog Inc.
License	Proprietary hosted service
Docs	https://inblog.ai/docs/developer-tools/mcp-connector

What it does

Inblog is the company blog platform for SEO and AI search. Connect it to Claude, ChatGPT, Cursor, or any MCP client to draft, schedule, and publish posts with images, organize tags, authors, and redirects, customize your blog's design, review leads captured by your blog forms, and see which posts and search keywords bring readers in. Every action stays within the blogs and plan of the signed-in account. Tools carry read-only and destructive annotations.

Example prompts:

• Turn this outline into a post with a cover image and schedule it for Monday at 9 a.m.
• Which posts drove the most traffic last month, and which search keywords brought readers in?
• Show me this week's new leads from our blog forms.

Verification

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

The same server is searchable in the ChatGPT Plugins Directory and the Claude Connectors Directory. Happy to provide a review account or anything else the curation process needs.

[thepetenetwork]

Onboarding request: Penny (ai.mypenny/mypenny)

Following the process in this thread: published to the official registry first, now asking for manual onboarding.

Field	Value
Registry name	ai.mypenny/mypenny, version 0.4.3 (active, isLatest), published 2026-10-09. Namespace is DNS-verified on mypenny.ai.
Registry entry	https://registry.modelcontextprotocol.io/v0.1/servers/ai.mypenny%2Fmypenny/versions/latest
What it does	Hosted memory for AI tools. One store of a person's notes, tasks, projects and trackers that every MCP client they connect can read and write.
Endpoint	https://app.mypenny.ai/mcp, remote Streamable HTTP
Auth	OAuth 2.0 authorization code with PKCE (S256) and dynamic client registration. initialize and tools/list answer without a token.
Tools	7: penny_session_start, penny_read, penny_write, penny_edit, penny_delete, penny_start_setup, penny_get_skill. Each has a title and readOnlyHint / destructiveHint.
Repository	The server is hosted and closed source, so there is no server repository. Client plugins (MIT): https://github.com/HelperLabs/mypenny-plugin
Docs	https://mypenny.ai/get-started
Privacy, terms, security	https://mypenny.ai/privacy, https://mypenny.ai/terms, https://mypenny.ai/security
Access	Public sign-up at https://mypenny.ai. Paid, with a 14-day free trial, no card.

server.json as published

{"$schema":"https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json","name":"ai.mypenny/mypenny","description":"Portable AI memory you own. Keep memories and notes across Claude, ChatGPT, and other AI tools.","title":"Penny","version":"0.4.3","websiteUrl":"https://mypenny.ai","icons":[{"src":"https://app.mypenny.ai/mypenny-coin-128.png","mimeType":"image/png","sizes":["128x128"]},{"src":"https://app.mypenny.ai/mypenny-coin.svg","mimeType":"image/svg+xml","sizes":["any"]}],"remotes":[{"type":"streamable-http","url":"https://app.mypenny.ai/mcp"}]}

I'm a co-founder. Happy to answer questions or set up a test account.

Thanks!

[gtm-api]

Onboarding request: com.gtm-api/linkedin-mcp

• Registry name: com.gtm-api/linkedin-mcp (domain-verified namespace)

• Version: 1.2.0, active, isLatest: true

• Remote: streamable HTTP at https://mcp.gtm-api.com/mcp. OAuth 2.1 with dynamic client registration; a gtm_live_ API key also works as a bearer token for headless clients.

• Package: npm @gtm-api/linkedin-mcp 1.3.1, a stdio launcher that bridges command-spawning clients to the same endpoint.

• Repository: https://github.com/gtm-api/linkedin-mcp

• License: MIT

• What it does: a managed LinkedIn MCP server for AI agents. Search, Sales Navigator, connection requests, messages and enrichment run on LinkedIn accounts the user owns and connects, with daily limits enforced per account on the server. gtm-api.com is not affiliated with LinkedIn.

• Verification:

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

Thanks for curating the list.

[mayur-tolexo]

Onboarding request: com.neevcloud/sandbox

Please consider NeevCloud Sandbox for github.com/mcp and the VS Code MCP gallery. We run the server. Values below were read from the registry on 2026-10-14.

Field	Value
Registry name	com.neevcloud/sandbox (domain-verified namespace: DNS TXT on the neevcloud.com apex)
Version	1.0.0, active, isLatest: true (published 2026-10-13)
Remote	Streamable HTTP at https://mcp.sandboxes.{region}.ai.neevcloud.com/mcp; region is a pick list, currently as-south-1
Auth	NeevCloud project API key as Authorization: Bearer (marked secret in the listing). An optional x-sandbox-name header picks the sandbox and defaults to default
Repository	None public; this is a proprietary hosted service
License	Proprietary
Docs	https://docs.ai.neevcloud.com/agentic-studio/overview/sandbox-mcp-server

What it does: gives an agent an isolated cloud sandbox as native tools: run commands, edit files, manage processes, and take snapshots to undo changes. The sandbox is created on first use, so the only setup is a URL and an API key.

Verification:

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

[sergimaker7]

Onboarding request: Sakaira (com.sakaira/mcp)

• Registry name: com.sakaira/mcp (domain-verified namespace)
• Latest version: 1.0.0, active, isLatest: true
• Transport: remote, Streamable HTTP at https://mcp.sakaira.com/mcp; auth is OAuth 2.1 with dynamic client registration (no API key)
• Repository: https://github.com/sakairahq/sakaira-marketplace (README; the server itself is a hosted service, source not public)
• License: the server is a proprietary hosted service; the repository is Apache-2.0
• Description: Make AI images, video, voiceovers and music, and edit video, from your assistant. 69 models and 27 tools, paid in credits, 100 free credits to start.
• Website / docs: https://sakaira.com · https://sakaira.com/mcp

Verification:

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

[mihneadevries]

Hi, please consider listing Retasc in the GitHub MCP Registry.

• Registry name: com.retasc/retasc (title Retasc)
• Version: 1.0.1 (latest)
• Transport: streamable-http at https://mcp.retasc.com/mcp
• Auth: API key sent as Authorization: Bearer <key> (no OAuth)
• Repo: https://github.com/Retasc/skills
• License: MIT
• Docs: https://docs.retasc.com
• Description: Retasc is a work queue for AI coding agents. Two agents can never hold the same issue. Run npx @retasc/cli@latest bind in the folder to connect Claude Code, Codex, Cursor or another MCP client.

Verification:

$ curl -s 'https://registry.modelcontextprotocol.io/v0/servers?search=com.retasc/retasc'
{"server":{"name":"com.retasc/retasc",
 "description":"Retasc is a work queue for AI coding agents. Two agents can never hold the same issue.",
 "title":"Retasc","version":"1.0.1","websiteUrl":"https://retasc.com",
 "icons":[{"src":"https://retasc.com/icon-512.png","mimeType":"image/png","sizes":["512x512"]}],
 "remotes":[{"type":"streamable-http","url":"https://mcp.retasc.com/mcp"}]},
 "_meta":{"io.modelcontextprotocol.registry/official":{"status":"active",
 "publishedAt":"2026-10-13T11:38:58.285924Z","isLatest":true}}}

Thanks!

[allpree]

Onboarding request: Cite42 (dev.cite42/mcp)

Published to the official MCP Registry first, following the process in this thread. I read the values below from the registry on 2026-10-14.

Field	Value
Registry name	dev.cite42/mcp (domain-verified namespace)
Version	0.8.1, active, isLatest: true
Remote	Streamable HTTP at https://mcp.cite42.dev, OAuth sign-in
Package	npm @cite42/mcp 0.8.1, stdio, API key in CITE42_API_KEY
Repository	https://github.com/Cite42/mcp
License	MIT

What it does: checks whether ChatGPT, Claude, Perplexity, Gemini and Google AI Overviews mention a brand when asked a buyer question, and which sources they cite. It also returns keyword search volume, Google Trends, Reddit and YouTube data. Pay per call, no subscription.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers/dev.cite42%2Fmcp/versions/latest"

Not listed on GitHub's side yet: curl "https://api.mcp.github.com/v0.1/servers?search=cite42" returns 0 servers.

[axalaia]

Onboarding request: NOTIFY (io.github.n0t1fy/notify-sms-georgia)

Following the process in this thread: published to the official MCP Registry first, now asking for onboarding to github.com/mcp.

Field	Value
Registry name	io.github.n0t1fy/notify-sms-georgia (GitHub organization namespace)
Version	0.1.0, active, isLatest: true (published 2026-10-14)
Remote	Streamable HTTP at https://api.n0t1fy.dev/mcp
Auth	None needed to start: the create_test_key tool returns a free test key, with no account and no OAuth. An optional Authorization: Bearer sk_test_… header takes a test key from the NOTIFY dashboard.
Tools	create_test_key, send_message, get_message
Repository	Hosted service; the source is not public. Examples (Node, Python, curl): https://github.com/n0t1fy/examples
License	Proprietary hosted service; the examples repository is MIT
Docs	https://n0t1fy.dev/api#mcp-server
What it does	SMS verification codes for Georgia (+995). A coding agent can get a test key, send a test code and read its delivery status in one session; test sends are simulated, so nothing is sent or charged. Real sends use a live key from the dashboard, in the application's own code. Checked end to end with Claude Code.

Verification (values read from the registry on 2026-10-14):

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=notify-sms-georgia"

Thank you!

[111mihir]

Please consider Idiolect AI for initial GitHub MCP gallery onboarding. I maintain the service at Idiolect AI / Moshpit Labs.

• Registry name: app.idiolect/idiolect-ai
• Version: 1.0.2; the upstream registry reports active and isLatest: true.
• Upstream registry entry
• Public MCP repository
• Public MCP repository license: MIT. The hosted service is governed by Idiolect AI terms.
• Endpoint: https://idiolect.app/api/mcp
• Transport: Streamable HTTP
• Authentication: per-user OAuth with browser authorization and dynamic client registration. Discovery is public; writing and profile tools require sign-in.
• Purpose: Write, rewrite and refine emails, messages, posts and docs using a portable, user-owned Writing Profile. Tools return writing; they do not send or publish it.
• Website, support, privacy

Native VS Code / GitHub Copilot OAuth, writing and refinement were verified on 13 October 2026, including the selected profile, saved output and refinement parent. This request is for interactive MCP discovery; it does not claim remote OAuth support in Copilot cloud agent or code review.

Verification on 14 October 2026:

curl 'https://registry.modelcontextprotocol.io/v0.1/servers?search=app.idiolect%2Fidiolect-ai'
curl 'https://api.mcp.github.com/v0.1/servers?search=app.idiolect%2Fidiolect-ai'

The upstream registry returns the active/latest version above; the GitHub gallery query returns zero entries. Please onboard the existing registry identity rather than creating a duplicate. Happy to supply any additional review information.

[KKKKhazix]

Please consider AIHOT for initial onboarding to github.com/mcp.

AIHOT helps users read and search curated AI news in Chinese, follow multi-source hot topics, and get daily, weekly, and monthly briefings with source links.

• Registry: io.github.KKKKhazix/aihot
• Version: 2.0.0; the official registry reports active and isLatest: true.
• Remote endpoint: https://aihot.news/api/mcp (Streamable HTTP).
• Authentication: none. Public, read-only; no account, API key, or OAuth is required.
• Repository: https://github.com/KKKKhazix/AIHOT
• License: MIT for the published engine code; hosted service and data usage are covered separately by https://aihot.news/terms.
• Documentation: https://aihot.news/agent?tab=mcp

Verified on 14 October 2026: the server exposes eight read-only tools. Latest-news, keyword-search, and daily-briefing calls succeeded both directly and through Grok's custom MCP connector. GitHub's registry search currently returns no AIHOT entry.

Verification: https://api.mcp.github.com/v0.1/servers?search=aihot

Please onboard the existing registry identity so future versions can sync. Thank you!

[brianmacy]

Onboarding request: Senzing (com.senzing/mcp)

Published to the official MCP Registry (DNS-verified com.senzing namespace); requesting onboarding to github.com/mcp.

Field	Value
Registry name	com.senzing/mcp
Version	1.38.2, active, isLatest: true (published automatically on every release)
Remote	Streamable HTTP at https://mcp.senzing.com/mcp
Auth	None. Public, free to use; no account, API key or OAuth
Repository	https://github.com/Senzing/mcp (README is the listing page; includes server.json)
License	Proprietary documentation license (LICENSE); hosted server provided AS-IS. Privacy policy
Publisher	Senzing, Inc.

What it does: entity resolution for Identity Intelligence — dedupe, match and link people and company records across systems. The server grounds an assistant in Senzing's own documentation and indexed code (data mapping to the Senzing Entity Specification, SDK code for Python/Java/C# plus community Rust/TypeScript, error troubleshooting, sample data). It needs no live Senzing instance and sends no user data to Senzing; mapping and resolution run locally.

Also listed in the Claude Connectors Directory.