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

[Wolfe-Jam]

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!

[lbesecker195]

Requesting initial GitHub MCP Registry onboarding for MCP Harbor, following the OSS-registry-first, manual-curation process described in this thread.

Field	Value
Registry name	io.github.lbesecker195/mcp-registry-search-find-mcp-servers-discover-install-mcp-tools-directory-catalog-marketplace
Version	1.0.1 — active, isLatest
Namespace	GitHub-verified, io.github.lbesecker195
Transport	Remote, Streamable HTTP
Endpoint	https://ai.mcpharbor.dev/mcp
Auth	None — no account, no key, no rate-limit gate on discovery
Repository	https://github.com/lbesecker195/MCP_Registry (Apache 2.0)
Website	https://ai.mcpharbor.dev
Agent entrypoint	https://ai.mcpharbor.dev/llms.txt

MCP Harbor is a registry and directory of MCP servers. It mirrors the official MCP Registry and keeps it in sync, alongside listings submitted directly. Each listing carries its server.json manifest, declared tools, environment variables and per-client install configuration.

It exposes three tools, so an agent can do discovery without a browser:

• search_servers — search by name, title, description, tag or tool name
• get_server — one server's manifest and metadata by exact name
• submit_server — publish a new listing, reviewed by a maintainer before it goes live

Verification:

# Active and latest in the official registry
curl -s "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.lbesecker195%2Fmcp-registry-search-find-mcp-servers-discover-install-mcp-tools-directory-catalog-marketplace/versions/latest"

# Live tool list from the endpoint
curl -s -X POST https://ai.mcpharbor.dev/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Happy to supply anything else useful for curation.

[lololosys]

Onboarding request: JobsPipe — dev.jobspipe/mcp in the OSS registry (https://registry.modelcontextprotocol.io, remote streamable-http at https://mcp.jobspipe.dev/mcp, OAuth 2.0 with dynamic client registration, MIT repo https://github.com/jobspipe/mcp). Live job postings from 30+ job boards, ATS feeds and public employment services, one schema. Already listed in the Claude connectors directory and Cursor marketplace. Docs: https://docs.jobspipe.dev/ai-agents/mcp — thanks!

[abhay-avagama]

Onboarding request: co.avagama/openings

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	co.avagama/openings
Latest version	0.1.48 (active / isLatest)
Repository	https://github.com/abhay-avagama/hiring-agent
server.json	https://github.com/abhay-avagama/hiring-agent/blob/main/server.json
Description	Search jobs on verified employer job boards. Every link is the employer's own posting.
Transport	Remote, streamable-http at https://openings.avagama.co/mcp (OAuth 2.1 + PKCE, dynamic client registration)
Namespace proof	DNS-verified on the apex of avagama.co

OSS registry verification

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

returns co.avagama/openings v0.1.48 active/latest.

github.com/mcp status (2026-09-22)

• Search openings / avagama does not surface a curated card for this server
• https://github.com/mcp/co.avagama/openings → 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.

[nikolatodorovic]

Onboarding request: Pressa (LaTeX to PDF)

Following the process described in this thread (official registry first, then manual onboarding here):

Field	Value
Registry name	io.github.pressa-dev/pressa
Version	0.7.2 (active, isLatest)
Transport	Remote Streamable HTTP at https://api.pressa.dev/mcp, and stdio via npm @pressa/mcp
Auth	None required. Keyless it exposes one tool, compile; an optional Authorization: Bearer <key> header adds template, asset and render tools
Repository	https://github.com/pressa-dev/mcp (MIT)
server.json	https://github.com/pressa-dev/mcp/blob/main/server.json
Docs	https://pressa.dev/docs/mcp

Pressa compiles LaTeX to PDF on the server, so an agent with no local TeX Live install still gets the PDF. Failed compiles return a structured diagnosis with a suggested fix instead of a raw TeX log.

Verify:

curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.pressa-dev/pressa"

Thanks!

[Hlobo-dev]

Onboarding request: Wealthnow (io.wealthnow/mcp)

This follows the process described in this thread: publish to the official registry first, then ask for manual onboarding, after which new versions sync.

Field	Value
Registry name	io.wealthnow/mcp, version 2.137.1 (active, isLatest). Namespace is DNS-verified on wealthnow.io.
Registry entry	https://registry.modelcontextprotocol.io/v0.1/servers/io.wealthnow%2Fmcp/versions/latest
Endpoint	https://mcp.wealthnow.io/mcp, remote Streamable HTTP (MCP 2025-06-18)
Auth	OAuth 2.1: 401 with resource_metadata (RFC 9728), dynamic client registration, PKCE S256, rotating refresh tokens. An X-API-Key header works as an alternative.
VS Code	Header auth (X-API-Key or Authorization: Bearer) works today. OAuth sign-in through VS Code's client metadata document (vscode.dev) is built and waiting in our next auth release.
Tools	Market data, fundamentals, SEC filings, insider, 13F and congressional trades, and private markets. All tools are annotated readOnlyHint: true.
Repository	https://github.com/Hlobo-dev/wealthnow-mcp
Docs	https://app.wealthnow.io/docs/mcp-and-sdks
Privacy and terms	https://wealthnow.io/privacy, https://wealthnow.io/terms

Thanks!

[saivendoti]

Requesting initial GitHub MCP Registry onboarding for Scout7, following the OSS-registry-first, manual-curation process described in this thread.

Field	Value
Registry name	ai.scout7/scout7
Version	1.0.0 — active, isLatest
Namespace	DNS-verified on scout7.ai
Registry entry	https://registry.modelcontextprotocol.io/v0.1/servers/ai.scout7%2Fscout7/versions/latest
Transport	Remote, Streamable HTTP
Endpoint	https://mcp.scout7.ai/mcp
Auth	OAuth 2.1 with PKCE (S256) and dynamic client registration
Docs	scout7.ai/mcp
Website	scout7.ai

Run a week of organic marketing on loop from your AI agent. Scout7 plans your week from your brand, then writes SEO blogs, videos, LinkedIn carousels and social posts, schedules everything across your channels, and reports what moved — it even checks whether you're cited by ChatGPT and Claude. You approve before anything goes live.

Also listed on Smithery, cursor.directory and MCP Marketplace. I'm on the Scout7 team, so flagging the relationship up front. Thanks!

[MuratKaragozgil]

Requesting initial GitHub MCP Registry onboarding for TraderSpy, following the OSS-registry-first, manual-curation process described in this thread.

Field	Value
Registry name	app.traderspy/traderspy
Version	3.0.0 — active, isLatest
Namespace	DNS-verified on traderspy.app
Registry entry	https://registry.modelcontextprotocol.io/v0.1/servers/app.traderspy%2Ftraderspy/versions/latest
Transport	Remote, Streamable HTTP at https://mcp.traderspy.app/mcp
Auth	OAuth 2.1 with dynamic client registration, or a free personal API key (Bearer)
Repository	https://github.com/target1m/traderspy-mcp (MIT, server.json at the root)
Tools	17, all read-only, each with readOnlyHint and a title

TraderSpy serves live crypto futures data: AI-generated signals with their realised outcomes, positioning of top traders across Binance, Hyperliquid, Bybit and OKX, prices and candles, 19 technical indicators, funding and open interest, a market screener and a condition backtest. No tool places, closes or modifies an order, and there is no withdrawal or transfer tool. Free accounts get 300 tool calls a day.

I'm on the team behind TraderSpy. Thanks!

[vict0ry]

Requesting initial GitHub MCP Registry onboarding for Doklad.ai, following the OSS-registry-first, manual-curation process described in this thread.

Field	Value
Registry name	ai.doklad/mcp
Version	1.1.0 — active
Namespace	HTTP-verified on doklad.ai (/.well-known/mcp-registry-auth)
Registry entry	https://registry.modelcontextprotocol.io/v0.1/servers/ai.doklad%2Fmcp/versions/latest
Transport	Remote, Streamable HTTP at https://doklad.ai/mcp
Auth	OAuth 2.1 with PKCE and dynamic client registration, or an API key (Bearer)
Repository	https://github.com/vict0ry/doklad-ai-mcp (MIT, server.json at the root)
Tools	17, each with a title and readOnlyHint / destructiveHint / openWorldHint

Doklad.ai is Czech invoicing software for freelancers and small companies. The server lets an assistant list, create, update and email invoices, get invoice PDFs, record received payments (a bookkeeping entry, it moves no money), manage customers and expenses, and summarise invoice stats and cash flow. Access is granted per company on a consent page (owners and admins only), every call is audit-logged, and the rate limit is 60 requests per minute per company. Docs: https://doklad.ai/mcp-fakturace

I run Doklad.ai. Thanks!

[dogrucanemek-alt]

Onboarding request for four servers, all active in the OSS registry:

Registry name	Version	Package	Transport	Repository
io.github.dogrucanemek-alt/cedulon	0.13.1	npm @cedulon/mcp-server	stdio	https://github.com/dogrucanemek-alt/cedulon
io.github.dogrucanemek-alt/conarium	0.2.51	npm @conarium-ai/core	stdio	https://github.com/dogrucanemek-alt/conarium
io.github.verax-ai/verax	0.3.0	npm @verax-ai/body	streamable-http (self-hosted)	https://github.com/verax-ai/verax
com.tugra-ai/tugra	0.1.4	npm tugra	stdio	https://github.com/dogrucanemek-alt/tugra

Happy to provide anything else needed for review. Thanks!

[happy520ai]

Requesting initial GitHub MCP Registry onboarding for Unified AI System, following the OSS-registry-first, manual-curation process described in this thread (I'm the project maintainer).

Field	Value
Registry name	io.github.happy520ai/unified-ai-system
Version	0.8.0 — active, isLatest: true, published 2026-09-25T16:45:29Z
Namespace	io.github.happy520ai (GitHub-derived, no custom domain)
Registry entry	https://registry.modelcontextprotocol.io/v0.1/servers/io.github.happy520ai%2Funified-ai-system/versions/latest
Transport	stdio
Package	OCI only: ghcr.io/happy520ai/unified-ai-system/mcp-server:0.8.0 (linux/amd64, linux/arm64); there is deliberately no npm or PyPI distribution
Repository	https://github.com/happy520ai/unified-ai-system (Apache-2.0, server.json at the root)
Tools	15 MCP tools: gateway health/readiness/chat, prompt enhancement (deterministic and model-backed), knowledge retrieval/ready, workflow health/actions/run, workforce health/agents, and three Agent-governance queries
Expectation	https://github.com/mcp/io.github.happy520ai/unified-ai-system currently returns 404, while io.github.opsloft/tariff-resolver — which used this thread the same way — returns 200, so I assume a curation queue rather than a failed criteria check

Two facts a reviewer can reproduce without installing anything, since a directory listing is only worth having if the artifact behaves:

• The roster is read from the published image, not from prose. node tools/verify-image-roster.mjs 0.8.0 fetches the OCI index over plain HTTPS with an anonymous pull token, verifies every blob against the digest its manifest names, and prints tools 15 from MCP_TOOL_NAMES in layer sha256:c585f08ef7de…. No Docker daemon and no registry login needed. The same command against 0.4.0 prints nine, so the number tracks the artifact.
• Cold stdio handshake is credential-free. Spawned as node packages/mcp-server/src/index.js with the environment
  reduced to PATH and NODE_ENV=production — no provider key of any kind reaches the process — it answers
  initialize at 9,234 ms and tools/list at 9,238 ms with 15 tools under protocol 2025-06-18, serving the local
  fake provider. A container inspect of 0.8.0 reports User: "node", ExposedPorts: null, and five env vars,
  none of them a credential.

Happy to supply anything else the review needs — a server.json diff, the per-release digests, or answers on the security posture.

[MohammadHijjawi97]

Requesting onboarding for io.github.MohammadHijjawi97/since-cutoff, following the OSS-registry-first process described in this thread. I built it.

• Official registry: io.github.MohammadHijjawi97/since-cutoff 0.2.0 (active, isLatest): https://registry.modelcontextprotocol.io/v0.1/servers/io.github.MohammadHijjawi97%2Fsince-cutoff/versions/latest
• Package: PyPI since-cutoff, stdio via uvx since-cutoff mcp, no API key needed
• Repo: https://github.com/MohammadHijjawi97/since-cutoff (MIT)
• Tools: api_changes(package, model | cutoff), project_changes(project_dir, model) and model_cutoff(model). For a Python dependency, they return which public APIs changed between the version that existed at the coding model's training cutoff and the version the project pins, using a static griffe diff. An agent can check this before it writes code from its memory of an older API.

Thanks!

[kisssam6886]

Requesting initial GitHub MCP Registry onboarding for ZoneFoundry, following the OSS-registry-first, manual-curation process described in this thread. I'm the developer.

Field	Value
Registry name	dev.zonefoundry/sonos
Version	1.0.9, active, isLatest
Namespace	DNS-verified on zonefoundry.dev
Registry entry	https://registry.modelcontextprotocol.io/v0.1/servers/dev.zonefoundry%2Fsonos/versions/latest
Transport	Remote, Streamable HTTP at https://relay.zonefoundry.dev/mcp
Auth	OAuth 2.1 with PKCE (dynamic client registration and client ID metadata documents). API key header as a fallback for clients without OAuth.
Repository	https://github.com/kisssam6886/zonefoundry-mcp (manifests and docs; the server is hosted)

It controls the user's own Sonos speakers through the official Sonos cloud: play music, volume, grouping, moving playback between rooms, announcements and reminders. 27 tools; read-only tools carry readOnlyHint. Users sign in with the free ZoneFoundry iOS app.

[stanlee000]

Onboarding request: Norman MCP Server

Hi GitHub MCP Registry team — requesting initial onboarding for Norman, following the OSS-registry-first and manual-curation process described in this discussion.

Norman connects AI assistants to a user's accounting workspace for invoicing, expense and receipt management, bookkeeping, bank reconciliation, and German tax workflows.

• Official registry name: finance.norman/mcp-server
• Published version: 0.1.7 — verified active and isLatest: true on September 27, 2026
• Registry entry: https://registry.modelcontextprotocol.io/v0.1/servers/finance.norman%2Fmcp-server/versions/latest
• Repository and setup documentation: https://github.com/norman-finance/norman-mcp-server
• Manifest: https://github.com/norman-finance/norman-mcp-server/blob/main/server.json
• Hosted endpoint: https://mcp.norman.finance/mcp — Streamable HTTP
• Authentication: OAuth Authorization Code with PKCE (S256) and dynamic client registration; users sign in to their own Norman account
• OAuth discovery: https://mcp.norman.finance/.well-known/oauth-authorization-server
• Website: https://norman.finance/

The official registry entry has been active since February 19, 2026, but a search for norman at https://github.com/mcp currently returns no results.

Could the curation team consider adding Norman so subsequent registry versions can sync? Please let us know if you need any additional metadata or review information.

Thank you!
Stan Kharlap — Norman

[vanshyadav1408]

Requesting initial GitHub MCP Registry onboarding for Omentir, following the OSS-registry-first, manual-curation process described in this thread. I maintain the project.

Field	Value
Registry name	io.github.vanshyadav1408/omentir
Version	1.1.0, active, isLatest (registry entry)
Transport	Remote, streamable HTTP: https://omentir.com/api/agent/v1/mcp
Auth	OAuth 2.1 with dynamic client registration and PKCE (protected resource metadata at https://omentir.com/.well-known/oauth-protected-resource)
Repository	https://github.com/vanshyadav1408/Omentir (MIT, TypeScript)
Docs	https://omentir.com/integrations/mcp

What it does: lets an agent find and score LinkedIn prospects, draft outreach, run human-paced campaigns, and answer replies through an Omentir workspace. The agent never gets the user's LinkedIn password, and it cannot change billing or connect accounts.

Thanks!

[lordhumunguz]

Requesting initial GitHub MCP Registry onboarding for SourceMedium, following the OSS-registry-first, manual-curation process described in this thread. We publish and run this server.

Field	Value
Registry name	com.sourcemedium/source-medium
Version	1.7.1, active, isLatest
Namespace	DNS-verified on sourcemedium.com
Registry entry	https://registry.modelcontextprotocol.io/v0.1/servers/com.sourcemedium%2Fsource-medium/versions/latest
Transport	Remote, Streamable HTTP at https://mcp.sourcemedium.com/mcp
Auth	OAuth sign-in with a SourceMedium account
Access	Read-only: queries a brand's SourceMedium commerce warehouse, Shopify stores and ad accounts
Docs	https://sourcemedium.com/docs/ai-analyst/connect-an-ai-assistant

Thank you!