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!

[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.

[oceanwaves630]

Onboarding request: ai.khive/khive

Please consider khive 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-14.

Field	Value
Registry name	ai.khive/khive
Version	1.0.0, active, isLatest: true
Transport	Remote, Streamable HTTP at https://khive.ai/v1/mcp
Auth	OAuth. An unauthenticated request gets 401 with WWW-Authenticate pointing at the protected-resource metadata (authorization server https://auth.khive.ai, scope khive:mcp). Clients without OAuth can send an API key as Authorization: ApiKey <key>.
Repository	Hosted service. The open-source engine is ohdearquant/khive.
License	Engine: Apache-2.0. The hosted service is a paid plan.
What it does	Persistent memory, a knowledge graph and a task list for agents, kept in the user's own workspace across sessions and clients. 22 tools, each with a title and a read-only or destructive hint.
Docs	https://www.khive.ai/docs

Check:

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

Leo, khive AI

[jmlawrence]

Please consider Hoot Lens for initial onboarding to github.com/mcp. We publish the existing com.hootlens/mcp identity and are requesting curation, not a duplicate Registry entry.

Hoot Lens gives coding agents recorded website evidence: timed visit narratives, click maps, recurring snags and linked JavaScript errors. Agents can trace a finding to a page, release, device and recorded moment before proposing a fix.

Field	Value
Official Registry identity	com.hootlens/mcp
Current version	1.1.0; active, isLatest: true, read from the Registry on 14 October 2026
Remote	Streamable HTTP at https://mcp.hootlens.com/mcp
Authentication	Account-authorized OAuth with project access and scopes enforced by the hosted API
Local package	npm @hootlens/mcp 1.1.0, stdio; Node.js 20 or newer
Public source	Parallel-Platforms/hootlens-mcp, release tag mcp-v1.1.0
License	MIT for the public MCP bridge source; the hosted service is governed by Hoot Lens terms
Setup	Connection guide
Reviewer path	https://mcp.hootlens.com/demo, anonymous synthetic Fieldnote data, read and replay only
Support	Public issues, support@hootlens.com

The release record links verified npm signature/provenance evidence to public source f06d28882ce38f9bce4d4b55d31c61189cc92415 and its release workflow. Provenance verifies source/build origin, not a security certification or universal client compatibility.

Verification at 4:28 PM Pacific on 14 October 2026:

curl 'https://registry.modelcontextprotocol.io/v0.1/servers/com.hootlens%2Fmcp/versions/latest'
curl 'https://api.mcp.github.com/v0.1/servers?search=hootlens'

The upstream entry is active/latest 1.1.0. GitHub's API returned zero entries for hootlens, Hoot Lens and com.hootlens; an unfiltered control returned a real server. The upstream manifest currently omits its optional repository field, so the public repository is linked explicitly above. We are not assuming the empty results indicate a sync defect.

Please consider onboarding this identity so future versions can sync. Happy to provide additional metadata or reviewer instructions. Thank you.

[jianpingliu]

Please onboard RealtyCrawl to the curated GitHub MCP Registry.

• Registry name: io.github.realtycrawl/realtycrawl
• Version: 1.0.0, verified active and isLatest: true on 2026-10-14 (America/Los_Angeles).
• Remote endpoint: https://realtycrawl.dev/mcp
• Transport: Streamable HTTP.
• Auth: per-user API key in Authorization: Bearer YOUR_API_KEY.
• Repository: https://github.com/realtycrawl/realtycrawl-mcp
• License: MIT for the public MCP client; hosted data operations require a RealtyCrawl account, API key, and credits.
• Documentation: https://docs.realtycrawl.dev

Five tools discover platforms and current capabilities, inspect endpoint schemas, and execute explicitly budgeted operations for source-linked real estate observations. Discovery includes research/unavailable operations: check capabilities before execution; it is not a guarantee of live source coverage. Metadata is free.

Verification:

curl 'https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.realtycrawl%2Frealtycrawl'

Registry readback returned version 1.0.0 with status active and isLatest: true. GitHub's curated registry currently returns no matching servers. No credentials are included.

[Coding-jpg]

Onboarding request: ai.glasser/glasser

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

Field	Details
Registry name	ai.glasser/glasser
Version	0.1.3; active; isLatest: true (verified 2026-10-15)
Transport	Remote Streamable HTTP
Endpoint	https://api.glasser.ai/mcp?utm_source=mcp-registry&utm_medium=mcp_directory
Authentication	OAuth sign-in; API key for clients without browser-based sign-in
Repository	https://github.com/glasser-ai/plugins
License	MIT for the public plugin configuration and skill; the hosted Glasser service has separate terms and paid API usage
Documentation	https://glasser.ai/docs/mcp-server

Glasser lets AI agents discover specialist data APIs, inspect endpoint contracts and prices, and retrieve data through one account and balance. Data retrieval is paid per call.

Registry verification: https://registry.modelcontextprotocol.io/v0.1/servers?search=glasser

The GitHub MCP Registry search returned no matching Glasser server today. Thank you for considering this onboarding request.

[bartekrutkowski]

Onboarding request: Watchgoose

• Registry name: io.github.bartekrutkowski/watchgoose-mcp
• Version: 1.1.1 (status active, isLatest: true)
• Transport / auth:
  • Remote Streamable HTTP: https://mcp.watchgoose.com/mcp. OAuth 2.1 with PKCE (S256), RFC 9728 protected-resource metadata and dynamic client registration. Consent is per project and read-only by default.
  • npm package watchgoose-mcp (stdio) with a project-scoped API key in WATCHGOOSE_API_KEY.
• Repository: https://github.com/bartekrutkowski/watchgoose-mcp
• License: MIT
• Description: Cron job and scheduled-task monitoring. Check status, schedules and status history for cron jobs, backups, systemd timers and Kubernetes CronJobs, and, with explicit read-and-write consent, create, update, pause, resume or delete checks. Listed in the Claude connector directory and the ChatGPT plugin directory.

Verification

$ curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=watchgoose"
io.github.bartekrutkowski/watchgoose-mcp 1.1.1  active  isLatest=true
  remote: https://mcp.watchgoose.com/mcp   package: npm watchgoose-mcp

$ curl -s "https://api.mcp.github.com/v0.1/servers?search=watchgoose"
{"servers":[],"metadata":{"count":0,...}}

Thanks!

[alexbjorlig]

Onboarding request: 21RISK (com.21risk/mcp)

Published to the official MCP Registry first, following the process in this thread. Values read from the registry on 2026-10-15.

Field	Value
Registry name	com.21risk/mcp (domain-verified namespace via HTTP proof on 21risk.com)
Version	1.0.0, active, isLatest: true (published 2026-10-15)
Remote	Streamable HTTP at https://21risk.com/api/mcp
Auth	OAuth 2.1 with PKCE (S256) and dynamic client registration. An unauthenticated request gets 401 with WWW-Authenticate pointing at RFC 9728 protected-resource metadata. At sign-in the user chooses read-only or full access per organization.
Repository	None public: 21RISK is a proprietary hosted service. Docs: https://21risk.com/docs/mcp-server
License	Proprietary hosted service. Terms: https://21risk.com/compliance/user-terms-of-services
What it does	Lets an assistant read and update a company's 21RISK data: risk management for industrial sites, covering audits, compliance, actions, claims and insurance values. The user's own 21RISK permissions always apply.
Also listed in	Claude connectors directory

A 21RISK account is required; a free account is enough to try it.

Verification:

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

[mmatus3]

Onboarding request: com.artifactbridge/artifactbridge

Please consider ArtifactBridge for github.com/mcp and the VS Code MCP gallery. We run the server. I read the values below from the registry on 2026-10-15.

Field	Value
Registry name	com.artifactbridge/artifactbridge (domain-verified namespace)
Version	0.1.0, active, isLatest: true
Transport	Remote Streamable HTTP: https://app.artifactbridge.com/mcp
Auth	OAuth 2.1 with PKCE (S256) and dynamic client registration (RFC 7591). No API key.
Repository	https://github.com/omnim-ai/artifactbridge-plugin (public plugin and skills for the server)
License	MIT (plugin repository)
Website	https://www.artifactbridge.com

What it does: ArtifactBridge gives coding agents governed access to a team's documents. Agents search, read, comment, and propose changes. A human approves every change before it is published.

Verification:

curl -s "https://registry.modelcontextprotocol.io/v0.1/servers/com.artifactbridge%2Fartifactbridge/versions/latest"

Thank you.

[LauraBuzas]

Onboarding request: com.opentext/sdp-remote-mcp

Please consider adding the OpenText Core Software Delivery Platform MCP server to the github MCP registry.

Field	Value
Registry name	com.opentext/sdp-remote-mcp (domain-verified namespace)
Version	1.0.0, active, isLatest: true
Transport	Remote Streamable HTTP: https://almoctane-{region}.saas.microfocus.com/mcp
Auth	OAuth 2.1 (interactive browser flow) · API access key (headless or service use)
Repository	https://github.com/opentext/OpenText-Model-Context-Protocol-Server
What it does	Connects the AI client to your OpenText Core Software Delivery Platform workspace and interact with delivery data without leaving the IDE.
License	OpenText End User License Agreement
Website	OpenText-Model-Context-Protocol-Server

Verification:

curl https://registry.modelcontextprotocol.io/v0.1/servers?search=com.opentext/sdp-remote-mcp

Thank you.

[Ed-Relight]

Onboarding request: ai.memestack/mcp (MemeStack)

Field	Value
Official registry name	ai.memestack/mcp
Latest version	1.4.0
Registry entry	https://registry.modelcontextprotocol.io/v0.1/servers/ai.memestack%2Fmcp/versions/latest
Transport	Remote, streamable-http at https://mcp.memestack.ai/mcp
Authentication	None (anonymous; 19 free read tools, 2 paid per call via x402 USDC or L402 Lightning)
Namespace proof	HTTP-verified on memestack.ai
Repository / docs	https://github.com/Ed-Relight/memestack-mcp (MIT) · https://memestack.ai/mcp-server
Description	Search memes, infographics, charts and screenshots by meaning, in-image text or visual similarity, with citation blocks.
Tool annotations	19 read-only tools carry readOnlyHint: true; generate_meme and submit_image carry readOnlyHint: false, destructiveHint: false

[dvir-daniel]

Onboarding request: sh.openpath/openpath (Openpath)

Please consider Openpath for github.com/mcp and the VS Code MCP gallery. We run the server. Values read from the official registry on 2026-10-15.

Field	Value
Registry name	sh.openpath/openpath
Version	3.6.0, active, isLatest: true
Remotes	https://openpath.sh/mcp/search (Streamable HTTP, no authentication) and https://openpath.sh/mcp (OAuth, for messages and the user's own listings)
Tools (no-auth endpoint)	search, get_listing, both read-only
Homepage / docs	https://openpath.sh, https://openpath.sh/docs/connect

Openpath is an open directory of real-world listings for AI agents: live jobs from employers' own job boards (Austin, TX and remote), each with the employer's Apply link, and local businesses around Austin, each with an Openpath inbox. Results are plain Markdown, one listing per result. Also listed in the Claude connectors directory, Smithery and Glama.

[NeedMohCompute]

Onboarding request: com.liquidcompute/gcat (Liquid Compute GPU Test)

Please consider Liquid Compute GPU Test for github.com/mcp and the VS Code MCP gallery. We run the server. Values read from the official registry on 2026-10-15.

Field	Value
Registry name	com.liquidcompute/gcat (domain-verified namespace)
Version	1.0.0, active, isLatest: true
Transport	Remote Streamable HTTP: https://api.liquidcompute.co/mcp
Auth	OAuth 2.1 with dynamic client registration and client ID metadata documents, scope gpu_tests. An unauthenticated request gets 401 with WWW-Authenticate pointing at the RFC 9728 protected-resource metadata. No API key.
Repository	https://github.com/Liquid-Compute/gcat (listing files and agent skill; the server is hosted)
License	MIT for the repository; the hosted service is covered by https://liquidcompute.com/terms
Website	https://liquidcompute.com/gpu-test
Pricing	Free; needs a Liquid Compute account (public sign-up)

What it does: runs GPU acceptance tests on NVIDIA GPU nodes the user administers. Liquid Compute connects over SSH from its own servers, runs NVIDIA DCGM diagnostics, a CUTLASS GEMM benchmark, HBM and PCIe bandwidth tests and NCCL all-reduce, and reports each measurement against the GPU profile's thresholds (A10, H100, H200, B200, B300; single nodes and 2- or 4-node RDMA clusters). Nothing is installed on the node. Adding nodes and starting a test require the user's explicit confirmation, enforced server-side. 10 tools, all annotated (read-only, or destructive for start and stop).

Verification:

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

[ngisvold]

Onboarding request: com.makepartsnow/manufacturing (Make Parts Now)

Please consider Make Parts Now for github.com/mcp and the VS Code MCP gallery. We run the server. Values read from the official registry on 2026-10-15.

Field	Value
Registry name	com.makepartsnow/manufacturing (HTTP-verified namespace on makepartsnow.com)
Version	1.0.0, active, isLatest: true
Transport	Remote Streamable HTTP: https://makepartsnow.com/mcp
Auth	Optional API key, Authorization: Bearer mpn_agent_.... initialize, tools/list, the catalog and sign-up work without it; the create_agent_account tool returns a free key for quoting and ordering.
Repository	None: hosted, closed-source service. Public listing packages: https://github.com/makepartsnow/makepartsnow-claude
License	Proprietary hosted service; Terms, Privacy
Website	https://makepartsnow.com/developers

What it does: instant quotes and ordering for custom parts from CAD files: SLS nylon and FDM 3D printing, and CNC-machined 6061 aluminum or C360 brass, made in-house and shipped within the US. 18 tools; a person pays through a Stripe Checkout link, or an agent pays in USDC via x402.

Verification:

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

[aduermael]

Onboarding request: io.github.aibakery/houston

Please consider Houston for the curated GitHub MCP Registry.

Houston lets agents read, write, and combine connected apps and databases through a shared runtime, with reusable workspace code and per-person permissions. Connector credentials stay on Houston.

Field	Value
Registry name	io.github.aibakery/houston
Version	0.1.0; active; isLatest: true, verified 2026-10-16
Transport	Remote Streamable HTTP
Endpoint	https://ok-houston.com/mcp
Authentication	OAuth authorization code with S256 PKCE, refresh tokens, and dynamic client registration
Website / signup	https://ok-houston.com / https://ok-houston.com/continue
Documentation	https://ok-houston.com/skill
Source / license	Core hosted service source is private and is not offered under an open-source license; hosted-service terms: https://ok-houston.com/terms. The separate connector catalog is public at https://github.com/aibakery/houston-hub.
Contact	hello@ok-houston.com

Verification:

curl 'https://registry.modelcontextprotocol.io/v0.1/servers/io.github.aibakery%2Fhouston/versions/latest'
curl 'https://api.mcp.github.com/v0.1/servers?search=io.github.aibakery%2Fhouston'

The upstream entry is active/latest. An unauthenticated initialize request returns HTTP 401 with a WWW-Authenticate pointer to https://ok-houston.com/.well-known/oauth-protected-resource/mcp. Authorization metadata is available at https://ok-houston.com/.well-known/oauth-authorization-server. Houston is an early-stage product; no uptime SLA or broad production adoption is claimed.