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!

[nofait-platform-team]

Onboarding request: io.github.no-fait/infinite-audience

Please consider Infinite Audience, published by NO FAIT (dba Infinite Audience), for initial onboarding to the GitHub MCP Registry, following the registry-first, manual-curation process described in this discussion.

Infinite Audience lets AI assistants discover audiences, build segments, match customer data, and deliver data to activation channels. Some actions may incur billable usage; access is authenticated and governed by server-side scopes.

Field	Value
Official MCP Registry name	io.github.no-fait/infinite-audience
Registry entry	https://registry.modelcontextprotocol.io/v0.1/servers/io.github.no-fait%2Finfinite-audience/versions/latest
Published version	1.0.3 (active, isLatest: true)
Transport	Remote Streamable HTTP
Production endpoint	https://mcp.infiniteaudience.ai/mcp
Authentication	First-party OAuth with PKCE and Dynamic Client Registration
Product website	https://infiniteaudience.ai
Documentation and connection guide	https://docs.infiniteaudience.ai/agents/mcp/
Repository / licensing	Proprietary hosted service; implementation and publisher manifest are maintained in the private no-fait/platform repository. No public source package is required to connect.
Support	support@infiniteaudience.ai · https://infiniteaudience.ai/contact
Privacy / terms	https://nofait.ai/privacy · https://nofait.ai/terms

Publication and verification (2026-10-09): A fresh readback of the official Registry's canonical latest-version endpoint confirms version 1.0.3, status: active, and isLatest: true. The Registry reports publication on September 27, 2026. GitHub's registry API returns zero entries for infinite-audience.

curl -sS 'https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.no-fait%2Finfinite-audience'
curl -sS 'https://api.mcp.github.com/v0.1/servers?search=infinite-audience'

Could the curation team review this existing remote server for inclusion and let us know if additional public metadata or a dedicated reviewer account is required? Thank you.

[emmafar]

Hi! Requesting onboarding of BoardMark to the GitHub MCP registry.

Official MCP Registry name: ai.boardmark/boardmark (domain-verified, version 1.0.26)
Transport: remote, Streamable HTTP — https://mcp.boardmark.ai/mcp
Auth: OAuth 2.1 (DCR + Client ID Metadata Documents), or a personal access token
Repository (client configs, MIT): https://github.com/i-c-develop/boardmark
Docs: https://mcp.boardmark.ai/connect.md
What it does: issue board (issues, sprints, comments, project docs as markdown) — agents work with the signed-in user's own permissions.
Publisher: I C Develop Co., Ltd — support@boardmark.ai

Thanks!

[emmafar]

Adding verification for the BoardMark request above (values read from the registry today, 2026-10-10):

Registry name	Version	Transport	Remote URL	Repository	License
ai.boardmark/boardmark	1.0.26 (active, isLatest)	streamable-http	https://mcp.boardmark.ai/mcp	i-c-develop/boardmark	MIT

Check: curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=ai.boardmark/boardmark" — and api.mcp.github.com/v0.1/servers?search=boardmark still returns total: 0.

An unauthenticated initialize POST (Accept: application/json, text/event-stream) returns 401 with an RFC 9728 challenge:

• mcp.boardmark.ai/mcp → 401, WWW-Authenticate: Bearer realm="board-mcp", resource_metadata="https://mcp.boardmark.ai/.well-known/oauth-protected-resource", scope="board"

OAuth 2.1 + PKCE with Dynamic Client Registration and Client ID Metadata Documents; no API keys needed. BoardMark has a free plan, so a reviewer can sign in through the OAuth flow with a fresh account — happy to provide a populated test account too. Thanks for curating this!

[AminDhouib]

Requesting initial GitHub MCP Registry onboarding for the Devino Solutions servers, following the OSS-registry-first, manual-curation process described in this thread. Devino Solutions (14930398 Canada Inc., https://devino.ca) builds and runs all of them; contact hello@devino.ca.

All 14 are published and active + isLatest on the official registry (domain-verified namespaces, except upAPI which is under io.github), none appears on github.com/mcp yet (api.mcp.github.com/v0.1/servers?search=<name> returns total: 0 for each). Every server is a hosted remote over Streamable HTTP with OAuth 2.1 + PKCE and dynamic client registration; no API keys. Client configs, docs links and per-server READMEs are in one public MIT repo: https://github.com/DevinoSolutions/mcp-servers.

Registry name	Version	Transport	Remote URL	Repository	License	What it does
now.sendly/sendly	1.0.0	streamable-http	https://app.sendly.now/api/mcp	mcp-servers/sendly	MIT	Send transactional email, draft and run campaigns, build onboarding workflows, manage contacts and segments, and fix deliverability with Sendly.
io.superbooks/superbooks	1.0.0	streamable-http	https://app.superbooks.io/mcp	mcp-servers/superbooks	MIT	Work with your SuperBooks books: categorize transactions, match receipts, draft and send invoices, chase unpaid ones, and read P&L, runway and spending reports.
now.voicelabs/voicelabs	1.0.0	streamable-http	https://app.voicelabs.now/api/mcp	mcp-servers/voicelabs	MIT	Generate speech from text in your VoiceLabs voices, transcribe audio to text, and manage your voice library, including consented voice cloning.
io.notifly/notifly	1.0.0	streamable-http	https://api.notifly.io/mcp	mcp-servers/notifly	MIT	Manage Notifly notification workflows, subscribers and topics, trigger delivery across email, SMS, push, chat and in-app, and check whether a message landed.
com.usepostify/postify	1.0.0	streamable-http	https://app.usepostify.com/api/mcp	mcp-servers/postify	MIT	Draft, schedule and publish social posts to your connected LinkedIn, X, Instagram, TikTok and other channels, and read post analytics in your Postify calendar.
com.getbioflow/bioflow	1.0.0	streamable-http	https://app.getbioflow.com/api/mcp	mcp-servers/bioflow	MIT	Edit and publish your BioFlow link-in-bio page: add, reorder or remove links and blocks, go live on a schedule, and read page views, clicks and signups.
io.dodomain/mcp	1.0.0	streamable-http	https://app.dodomain.io/api/mcp	mcp-servers/dodomain	MIT	Connect your customers' custom domains to your product with doDomain: preflight a domain, start a guided DNS connect session, verify records and check health.
com.nowgetitdone/getitdone	1.0.1	streamable-http	https://app.nowgetitdone.com/api/mcp	mcp-servers/getitdone	MIT	Create, update and track tasks and projects in your GetItDone team workspaces: capture to-dos from notes, review your workload and dig into any task.
com.aishorty/shorty	1.0.0	streamable-http	https://aishorty.com/api/mcp	mcp-servers/shorty	MIT	Summarize YouTube videos, web pages, articles and documents, transcribe audio and video, add captions, and search your saved summaries with Shorty.
io.snapvisor/snapvisor	1.0.0	streamable-http	https://mcp.snapvisor.io/	mcp-servers/snapvisor	MIT	Review SnapVisor visual regression builds: see what changed in screenshot diffs, approve or reject builds, handle flaky changes and join review threads. MCP access needs a paid SnapVisor plan.
com.getuptimely/uptimely	1.0.0	streamable-http	https://app.getuptimely.com/api/mcp	mcp-servers/uptimely	MIT	Manage uptime monitors, incidents and status pages in Uptimely: check what is down, add monitors, run incident response step by step and draft postmortems.
io.github.DevinoSolutions/upapi-mcp	0.2.0	streamable-http (also npm @upapi/mcp, stdio)	https://app.upapi.io/api/mcp	mcp-servers/upapi (source: upapi-mcp)	MIT	Call a catalog of ready-to-use APIs such as web search, Wikipedia, GitHub, scraping, screenshots, PDF and OCR through one upAPI account, with no signup at each upstream service.
net.unotes/unotes	1.0.0	streamable-http	https://unotes.net/api/mcp	mcp-servers/unotes	MIT	Search a library of university course material: past exams, assignments, lab reports and lecture notes, plus your uNotes flashcards and quizzes. All tools read-only.
com.trycaly/caly	1.0.0	streamable-http	https://mcp.trycaly.com/mcp	mcp-servers/caly	MIT	Find open meeting times, book, reschedule and cancel meetings, and read your event types, bookings and working-hours schedules in Caly.

Verification. Registry values above were read from the registry today (2026-10-09), not from memory:

for n in now.sendly/sendly io.superbooks/superbooks now.voicelabs/voicelabs io.notifly/notifly \
         com.usepostify/postify com.getbioflow/bioflow io.dodomain/mcp com.nowgetitdone/getitdone \
         com.aishorty/shorty io.snapvisor/snapvisor com.getuptimely/uptimely \
         io.github.DevinoSolutions/upapi-mcp net.unotes/unotes com.trycaly/caly; do
  curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=$n"
done

An unauthenticated initialize POST to each remote URL (Accept: application/json, text/event-stream) returns 401 with an RFC 9728 WWW-Authenticate challenge pointing at the protected-resource metadata, which is the expected response for a probe:

• app.sendly.now/api/mcp → 401, WWW-Authenticate: Bearer resource_metadata="https://app.sendly.now/.well-known/oauth-protected-resource/api/mcp"
• app.superbooks.io/mcp → 401, WWW-Authenticate: Bearer resource_metadata="https://app.superbooks.io/.well-known/oauth-protected-resource"
• app.voicelabs.now/api/mcp → 401, WWW-Authenticate: Bearer error="invalid_token", resource_metadata="https://app.voicelabs.now/.well-known/oauth-protected-resource"
• api.notifly.io/mcp → 401, WWW-Authenticate: Bearer error="invalid_token", resource_metadata="https://api.notifly.io/.well-known/oauth-protected-resource/mcp"
• app.usepostify.com/api/mcp → 401, WWW-Authenticate: Bearer error="invalid_token", resource_metadata="https://app.usepostify.com/.well-known/oauth-protected-resource"
• app.getbioflow.com/api/mcp → 401, WWW-Authenticate: Bearer error="invalid_token", resource_metadata="https://app.getbioflow.com/.well-known/oauth-protected-resource"
• app.dodomain.io/api/mcp → 401, WWW-Authenticate: Bearer error="invalid_token", resource_metadata="https://app.dodomain.io/.well-known/oauth-protected-resource"
• app.nowgetitdone.com/api/mcp → 401, WWW-Authenticate: Bearer resource_metadata="https://app.nowgetitdone.com/.well-known/oauth-protected-resource", scope="workspaces:read tasks:read tasks:write projects:read"
• aishorty.com/api/mcp → 401, WWW-Authenticate: Bearer error="invalid_token", resource_metadata="https://aishorty.com/.well-known/oauth-protected-resource"
• mcp.snapvisor.io/ → 401, WWW-Authenticate: Bearer error="invalid_token", resource_metadata="https://mcp.snapvisor.io/.well-known/oauth-protected-resource"
• app.getuptimely.com/api/mcp → 401, WWW-Authenticate: Bearer error="invalid_token", resource_metadata="https://app.getuptimely.com/.well-known/oauth-protected-resource"
• app.upapi.io/api/mcp → 401, WWW-Authenticate: Bearer resource_metadata="https://app.upapi.io/api/auth/.well-known/oauth-protected-resource"
• unotes.net/api/mcp → 401, WWW-Authenticate: Bearer error="invalid_token", resource_metadata="https://unotes.net/.well-known/oauth-protected-resource"
• mcp.trycaly.com/mcp → 401, WWW-Authenticate: Bearer resource_metadata="https://mcp.trycaly.com/.well-known/oauth-protected-resource"

Most of the apps have a free tier, so a reviewer can sign in through the OAuth flow with a fresh account; happy to provision test accounts (including a paid SnapVisor seat) or answer anything else. Thanks for curating this.

[jianpingliu]

Onboarding request: io.github.ricciflow-api/soldfetch

Please consider SoldFetch for the GitHub MCP Registry. The server is already published in the official MCP Registry.

Field	Value
Registry name	io.github.ricciflow-api/soldfetch
Version	1.0.0
Official registry	https://registry.modelcontextprotocol.io/?q=io.github.ricciflow-api/soldfetch
Endpoint	https://soldfetch.com/api/mcp
Transport	Streamable HTTP
Authentication	User-provided SoldFetch API key via Authorization: Bearer or API-KEY; no OAuth
Repository	https://github.com/ricciflow-api/soldfetch-mcp
Documentation	https://docs.soldfetch.com/guides/ai-agents
Public server card	https://soldfetch.com/.well-known/mcp/server-card.json
License	MIT for the public metadata and connection examples; the hosted service implementation is not included in that repository

SoldFetch provides three tools: search_ebay_sold, search_ebay_category, and get_ebay_item. These expose eBay sold and active listing search, category browsing, and public item details for resale research. Each successful data tool call costs one SoldFetch request; initialization and tool discovery consume zero data units. Displayed listing prices are not verified accepted-offer amounts, and sale dates and exact product identity are unverified.

Authenticated MCP initialization and discovery have been verified against the production endpoint, with all three tools returned. We understand that first-time inclusion is manually curated and would appreciate consideration.

[Kuifje23]

Onboarding request: nl.fermat360/fermat-360

Requesting onboarding of Fermat 360 to the GitHub MCP Registry.

Registry name	nl.fermat360/fermat-360 (domain-verified)
Version	1.0.1 (active, isLatest)
Transport	Streamable HTTP, remote: https://fermat360.nl/mcp
Auth	OAuth 2.1 with PKCE (S256); clients identified by Client ID Metadata Document; protected-resource metadata per RFC 9728
Clients	VS Code, Claude, Claude Code, ChatGPT
Docs	https://fermat360.nl/mcp-koppeling
Repository	https://github.com/Kuifje23/fermat360-mcp
Publisher	Fermat 360
Access	Paid subscription for law firms

Fermat 360 answers questions about Dutch law from Dutch case law, legislation and EU law, with numbered citations that link to the source documents.

Verify:

curl -s 'https://registry.modelcontextprotocol.io/v0/servers?search=nl.fermat360/fermat-360'

An unauthenticated POST to https://fermat360.nl/mcp returns 401 with WWW-Authenticate: Bearer resource_metadata="https://fermat360.nl/.well-known/oauth-protected-resource/mcp". Happy to provide a test account.

[DenRakEiw]

Request to onboard io.github.DenRakEiw/scumble (Scumble, a free, open-source desktop editor for AI inpainting; agents get 113 tools: select by text, inpaint into layers, masks, filters, PSD/ORA export).

• Registry: io.github.DenRakEiw/scumble, version 0.1.45 (latest, active)
• Package: MCPB over stdio, https://github.com/DenRakEiw/scumble/releases/download/v0.1.45/scumble-0.1.45.mcpb (SHA-256 in the registry entry); the bundle starts the installed Scumble's MCP server (Windows; installer, Microsoft Store or portable)
• Repository: https://github.com/DenRakEiw/scumble, GPL-3.0; docs: https://github.com/DenRakEiw/scumble/blob/main/docs/MCP.md
• curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.DenRakEiw/scumble&version=latest"

[ayeshLK]

Onboarding request: io.github.ayeshLK/archsmith

Please consider ArchSmith for the GitHub MCP Registry and the MCP servers gallery in VS Code. It is already published in the Official MCP Registry.

Field	Value
Registry name	io.github.ayeshLK/archsmith
Current version	0.8.1
Official registry	https://registry.modelcontextprotocol.io/?q=io.github.ayeshLK%2Farchsmith
Package	@archsmith/mcp-server
Transport	Local stdio
Install command	npx -y @archsmith/mcp-server
Repository	https://github.com/ayeshLK/archsmith
Server documentation	https://github.com/ayeshLK/archsmith/tree/main/packages/mcp-server
npm package	https://www.npmjs.com/package/@archsmith/mcp-server
License	Apache-2.0
Credentials	None

ArchSmith is a deterministic architecture-diagram renderer. Its MCP server lets agents read the live schema and governed registries, validate diagram IR, and render SVG without embedding an LLM or exposing per-diagram styling controls.

It exposes the get_schema, render, validate, list_registries, and get_registry tools, along with schema, registry, and rendered-diagram resources.

Verification:

• The Official MCP Registry record is active and marked as the latest version.
• A search of https://api.mcp.github.com/v0.1/servers?search=archsmith currently returns zero results, so this is not a duplicate.
• The server is exercised through a real MCP client in its automated test suite and requires no environment variables or external credentials.

[sequico]

Onboarding request: io.github.sequico/server-noonien

Please consider server-noonien for the GitHub MCP Registry. It is already published in the Official MCP Registry (active, isLatest).

Field	Value
Registry name	io.github.sequico/server-noonien
Current version	1.0.1
Official registry	https://registry.modelcontextprotocol.io/?q=io.github.sequico%2Fserver-noonien
Package	server-noonien (npm)
Transport	Local stdio
Install command	npx -y server-noonien
Repository	https://github.com/sequico/server-noonien
License	MPL-2.0
Credentials	None

server-noonien is shared, serverless, conflict-free memory for AI agents: a multi-machine drop-in for the MCP memory knowledge graph. It exposes the same nine tools as @modelcontextprotocol/server-memory (create_entities, create_relations, add_observations, delete_entities, delete_observations, delete_relations, read_graph, search_nodes, open_nodes) plus the memory://knowledge-graph resource, and converges per-node shards across machines — over a shared folder, an S3-compatible bucket, or peer to peer with no shared area at all (the companion nooniend daemon).

Verification:

• curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.sequico/server-noonien" → status: active, isLatest: true, version 1.0.1.

Thanks!

[byron-allsourcedata]

Onboarding request: io.agentpixel/agentpixel

Please consider AgentPixel for the GitHub MCP Registry. Values below were read from the official registry on 2026-10-10.

Field	Value
Registry name	io.agentpixel/agentpixel (domain-verified namespace on agentpixel.io)
Version	0.1.1, active, isLatest: true
Transport	Remote, Streamable HTTP: https://agentpixel.io/mcp
Auth	OAuth 2.1 with PKCE (S256) and dynamic client registration, or the account API key as Authorization: Bearer. Signup tools need no credential.
Repository	https://github.com/byron-allsourcedata/agentpixel-mcp
License	MIT for the repository; the hosted service is proprietary
Docs	https://agentpixel.io/connect
Privacy / terms	https://allsourcedata.io/privacy / https://allsourcedata.io/terms
Support	joey@allsourcedata.io

What it does: a consent-first website pixel for agents. Visitors accept "identify this visit" before any identification runs; the agent starts a 30-day trial (no card), installs the tag, configures the consent bar, verifies installation and reads consented contacts. All 12 tools carry a title and readOnlyHint/destructiveHint annotations, plus output schemas.

Verification:

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

Publisher: AllSource Data Corporation. Disclosure: I am the CEO. A synthetic evaluation account is available for review on request.

[PranavNagrecha]

Onboarding request: io.github.PranavNagrecha/salesforce-intelligence

Requesting initial onboarding for sf-intelligence, following the OSS-registry-first process in this thread. I'm the maintainer. Values below were read from the official registry on 10 October 2026.

Field	Value
Registry name	io.github.PranavNagrecha/salesforce-intelligence (GitHub namespace)
Version	0.4.0, active, isLatest: true
Package / transport	npm sf-intelligence, local stdio: npx -y sf-intelligence mcp --vault /absolute/path/to/org-kb (or set SFI_VAULT)
Auth	None. Runs locally against retrieved org metadata; no API keys, no Salesforce login at query time
Try it without a Salesforce org	npx -y sf-intelligence demo (bundled synthetic org)
Repository	https://github.com/PranavNagrecha/Salesforce-Intelligence
Manifest	https://github.com/PranavNagrecha/Salesforce-Intelligence/blob/main/packages/cli/server.json
Website / docs	https://sfi.auditforce.cloud
License	MIT with Commons Clause (source-available)

What it does: Ask your AI what breaks before you change Salesforce. Offline, read-only, cited answers: questions like "can I delete this field?" or "what runs when an Opportunity is saved?" are answered from the org's retrieved metadata, with citations. Not affiliated with Salesforce.

Verification

curl "https://registry.modelcontextprotocol.io/v0/servers?search=salesforce-intelligence"

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

Thanks!

[ivenxu]

Onboarding request: io.github.feimacode/open-design

Following the OSS-registry-first process in this thread (publish to the official MCP Registry, then request GitHub MCP Registry onboarding; versions sync after onboarding), please consider Open Design for the GitHub MCP Registry.

Field	Value
Official registry name	io.github.feimacode/open-design
Latest version	0.2.0 (active, isLatest), published 2026-10-10
Package / transport	npm @feimacode/open-design-agent-kit-mcp 0.2.0, stdio (npx -y @feimacode/open-design-agent-kit-mcp)
Auth	None. Optional OPEN_DESIGN_FIGMA_TOKEN (secret) only for importing Figma frames
Repository	https://github.com/feimacode/open-design-agent-kit (server in packages/mcp-server)
Manifest	server.json
License	MIT

What it does

A design library and workflow for coding agents: 163 skills, 114 design templates, 152 brand design systems and 167 remixable examples. Ask the agent for a deck, landing page, dashboard or prototype and it writes real HTML files into the project, then checks and exports them (PNG, PDF, PowerPoint, MP4/GIF, standalone HTML) through the server's 23 tools.

The server never calls a model and needs no account or API key: the agent's own model does the generation, and the server supplies the library and the bookkeeping. It uses the client's MCP roots to find the workspace, so it writes into the open folder when installed from the VS Code @mcp gallery.

Verification
curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.feimacode/open-design"

Thanks for considering it.

[SokolskyNikita]

Onboarding request: io.github.SokolskyNikita/annas-mcp

Please consider annas-mcp for the GitHub MCP Registry. I'm the maintainer. Values below were read from the official registry on 2026-10-10.

Field	Value
Registry name	io.github.SokolskyNikita/annas-mcp
Version	0.2.0, active, isLatest: true
Package and transport	npm annas-mcp, stdio
Repository	https://github.com/SokolskyNikita/annas-mcp
License	MIT
What it does	Searches Anna's Archive for books and journal articles by title, author or DOI, and downloads the file the user picks. It uses the user's own Anna's Archive membership and runs locally with no telemetry.

Verification:

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

[gjkim]

Onboarding request: net.softhills/mcp

Hello GitHub MCP Registry team,

We would like to request onboarding of the official Softhills MCP server to the GitHub MCP Registry so developers can discover and install it through the VS Code MCP Gallery.

The server is already published in the official MCP Registry.

Field	Value
Registry name	net.softhills/mcp
Title	Softhills
Version	1.1.0
Status	active / isLatest: true
Deployment	Remote-only
Transport	Streamable HTTP
Endpoint	https://ai.softhills.net/mcp
Authentication	No authentication required
Icon	https://ai.softhills.net/icon-256.png
Repository	No public repository. Developed and operated in-house by Softhills.
Availability	Free to use, subject to the terms of use below.
Terms of use	https://ai.softhills.net/terms.html
Privacy policy	https://ai.softhills.net/privacy.html

Description: Official MCP server for Softhills 3D/2D Visualization SDKs, API documentation, and code examples.

The server exposes 12 tools, all declared read-only, for searching and retrieving SDK documentation, API references, code examples, changelogs, and migration guides.

This is a proprietary service developed and operated by Softhills. Access to the MCP service is free of charge; this does not imply an open-source license for the server or Softhills SDKs.

Official Registry entry: https://registry.modelcontextprotocol.io/v0.1/servers/net.softhills%2Fmcp/versions/1.1.0

Registry verification: curl -sS "https://registry.modelcontextprotocol.io/v0.1/servers?search=net.softhills%2Fmcp"

Please consider onboarding Softhills to the GitHub MCP Registry. We would be happy to provide any additional information needed for review.

Thank you.

[adamgusky]

Onboarding request: com.blawgy/blawgy

Following the process in this thread (published to the official MCP Registry first, now requesting GitHub MCP Registry onboarding). I maintain the server. Values below were read from the registry on 2026-10-10.

Field	Value
Registry name	com.blawgy/blawgy (domain-verified namespace)
Version	1.0.0, active, isLatest: true
Deployment	Remote only, Streamable HTTP
Endpoint	https://app.blawgy.com/mcp
Auth	OAuth 2.1 with dynamic client registration and PKCE (RFC 9728 protected resource metadata served on 401), or a Blawgy API key as a bearer token
Repository	https://github.com/adamgusky/blawgy-mcp
License	MIT
Website	https://blawgy.com/mcp
Icon	https://blawgy.com/favicon-512.png

What it does. Blawgy is a done-for-you SEO content service. The MCP server lets an agent read Search Console traffic, rankings and indexing, run keyword research, manage the content plan, and write, update and publish blog posts to WordPress, Shopify, Webflow, Wix, Framer, Ghost and Duda. 166 tools; destructive ones ask for confirmation. Included on every paid Blawgy plan.

Verification

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

{"servers":[{"server":{"name":"com.blawgy/blawgy","title":"Blawgy","version":"1.0.0","websiteUrl":"https://blawgy.com/mcp","repository":{"url":"https://github.com/adamgusky/blawgy-mcp","source":"github"},"remotes":[{"type":"streamable-http","url":"https://app.blawgy.com/mcp"}]},"_meta":{"io.modelcontextprotocol.registry/official":{"status":"active","isLatest":true,"publishedAt":"2026-10-11T03:33:13Z"}}}],"metadata":{"count":1}}

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

Thanks for considering it.

[Matthew-bk]

Onboarding request: ai.bankrolled/agent-hub

Please consider Bankrolled.ai Agent Hub for the GitHub MCP Registry. It is published in the official MCP Registry (domain-verified namespace). I maintain the server. Values below were read from the registry on 2026-10-11.

Field	Value
Registry name	ai.bankrolled/agent-hub (domain-verified, bankrolled.ai)
Version	1.3.0, active, isLatest: true
Deployment	Remote only, Streamable HTTP
Endpoint	https://bankrolled.ai/mcp
Auth	None
Repository	https://github.com/Bankrolled/bankrolled-ai-docs (documentation; the hosted service is not open source)
License	CC BY 4.0 for the documentation repository; the hosted service is proprietary
Docs	https://bankrolled.ai/llms.txt
Server card	https://bankrolled.ai/.well-known/mcp/server-card.json
Icon	https://bankrolled.ai/wp-content/uploads/2026/08/cropped-mark-cropped-192x192.jpg
Contact	agents@bankrolled.com

What it does. Free, sourced money facts for the US, UK, Canada, Australia and New Zealand. Four tools, all free: health_check, pricing_list (catalog and supported queries), money_fact (deposit-protection limits plus ISA, 401(k), Roth IRA and TFSA limits) and scheme_lookup (deposit-insurance scheme by country). Every answer carries the official source, an as-of date and a bankrolled.com citation.

Verification

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=ai.bankrolled/agent-hub"