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!

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

[kleash]

Onboarding request: io.github.kleash/airscp

I maintain this server and am asking for it to be listed on github.com/mcp. It is published in the official MCP Registry already. I read these values from the registry on 2026-10-11.

Field	Value
Registry name	io.github.kleash/airscp (GitHub namespace)
Version	1.1.0, active, isLatest: true
Package and transport	MCPB (airscp.mcpb from the GitHub release, SHA-256 in the entry), stdio, local; no API key
Platform	macOS 13.1+ (it runs the AirSCP app installed on the Mac)
Repository	https://github.com/kleash/airscp
License	Apache-2.0
Docs for agents	https://kleash.github.io/airscp/llms.txt
Icon	https://raw.githubusercontent.com/kleash/airscp/main/docs/assets/icon.png

What it does. AirSCP is a free, open-source Mac app for SSH servers and Windows desktops: a two-pane SCP/SFTP browser with a transfer queue, Synchronize, Find Files, a Linux monitor, tunnels, jump hosts and proxies, a terminal, and a built-in Remote Desktop client. Its MCP server (16 tools: snapshot, go, open, click, type, menu, drop, guide…) lets an agent drive the app the way its user does. The user turns it on in Settings, every action shows in the app, and agents never see saved passwords.

Verification

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.kleash/airscp&version=latest"

{"servers":[{"server":{"$schema":"https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json","name":"io.github.kleash/airscp","description":"Drive AirSCP, the Mac app for SCP/SFTP file transfers, SSH servers and Windows Remote Desktop","title":"AirSCP","repository":{"url":"https://github.com/kleash/airscp","source":"github"},"version":"1.1.0","websiteUrl":"https://kleash.github.io/airscp/ai-agents.html","icons":[{"src":"https://raw.githubusercontent.com/kleash/airscp/main/docs/assets/icon.png","mimeType":"image/png","sizes":["512x512"]}],"packages":[{"registryType":"mcpb","identifier":"https://github.com/kleash/airscp/releases/download/v1.1.0/airscp.mcpb","fileSha256":"2ace8189c2d3185298e3e9436f7208e77e7c530e1a582275101d5ea7815fa98a","transport":{"type":"stdio"}}]},"_meta":{"io.modelcontextprotocol.registry/official":{"status":"active","statusChangedAt":"2026-10-09T18:50:12.951246Z","publishedAt":"2026-10-09T18:50:12.951246Z","updatedAt":"2026-10-09T18:50:12.951246Z","isLatest":true}}}],"metadata":{"count":1}}

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

Thanks for considering it.

[flowradev]

Hi GitHub MCP team,

Please onboard Flowra to the GitHub MCP Registry. It is published in the official MCP Registry as io.github.flowradev/mcp (v1.0.2, active, latest), a remote streamable-HTTP server at https://mcp.flowra.dev/mcp with OAuth sign-in.

One MCP server for your apps' tools and your own custom tools, plus hosted AI agents and workflows with approval gates and a run ledger.

Site: https://flowra.dev
Docs: https://docs.flowra.dev/guides/mcp
Repo: https://github.com/flowradev/flowra-cursor-plugin
Contact: team@flowra.dev

Thanks,
The Flowra team

[ahjephson]

Please could you onboard Roslyn Workbench MCP to github.com/mcp?

It is a local MCP server for Roslyn-powered C# code inspection and safe, transactional refactoring. It runs over stdio, defaults to inspection-only, and keeps workspace analysis and source changes on the user's machine. Mutation modes are explicitly enabled by the user.

• Registry name: io.github.lantean-code/roslyn-workbench-mcp
• Version: 1.0.1; verified as active and isLatest: true in the official Registry.
• Registry entry: https://registry.modelcontextprotocol.io/v0.1/servers/io.github.lantean-code%2Froslyn-workbench-mcp/versions/1.0.1
• Package: https://www.nuget.org/packages/Lantean.Roslyn.Workbench.Mcp/1.0.1
• Runtime and transport: .NET 10, dnx, local stdio; also distributed as a .NET tool. There is no hosted endpoint.
• Repository: https://github.com/lantean-code/roslyn-workbench-mcp
• Licence: MIT.
• Documentation: https://lantean-code.github.io/roslyn-workbench-mcp/1.0.1/

Registry verification:

curl 'https://registry.modelcontextprotocol.io/v0.1/servers/io.github.lantean-code%2Froslyn-workbench-mcp/versions/1.0.1'

The GitHub Registry search currently returns no entry for roslyn-workbench-mcp. Please let us know if NuGet/dnx requires any additional metadata or installation validation for onboarding.

[RhinoRank]

Onboarding request: io.rhinorank.app/rhino-rank

Please consider Rhino Rank for the GitHub MCP Registry. It is published in the official MCP Registry with a domain-verified namespace (HTTP proof on app.rhinorank.io). We run the server. Values below were read from the registry on 2026-10-11.

Field	Value
Registry name	io.rhinorank.app/rhino-rank
Version	1.0.0 (active, latest)
Remote	https://app.rhinorank.io/mcp, streamable HTTP
Auth	OAuth 2.1 with dynamic client registration and PKCE; a personal API key as a Bearer token also works
Repository / license	None: a hosted, closed-source service. Setup docs: https://app.rhinorank.io/mcp/setup
Privacy	https://www.rhinorank.io/privacy-policy/#ai-assistants

Quote, order and manage link building and press releases in a Rhino Rank account: the link catalogue, quotes, orders and coupons, the monthly Managed Service, press-release briefs and approval, account details and support requests.

[mishafyi]

Onboarding request: io.github.mishafyi/apple-docs-2.0-mcp

Please consider Apple Docs 2.0 MCP for github.com/mcp. I maintain it. Values below were read from the registry on 2026-10-12.

Field	Value
Registry name	io.github.mishafyi/apple-docs-2.0-mcp
Version	2.0.5, active, isLatest: true
Package and transport	npm apple-docs-2.0-mcp, local stdio (npx -y apple-docs-2.0-mcp); no hosted endpoint, no API key
Repository	https://github.com/mishafyi/Apple-Docs-2.0-MCP
License	MIT

What it does: gives coding agents Apple's developer documentation: search with developer.apple.com's own results, full pages with signatures and OS availability, an offline index of 336,629 pages, and 1,700 WWDC sessions (2014–2026) with transcripts and code.

Verification:

curl 'https://registry.modelcontextprotocol.io/v0.1/servers/io.github.mishafyi%2Fapple-docs-2.0-mcp/versions/2.0.5'

GitHub's registry search currently returns no entry for apple-docs.

[shsunmoonlee]

Onboarding request: so.transcribe/mcp

Please consider transcribe.so for github.com/mcp. We run the server. Values below were read from the registry on 2026-10-12.

Field	Value
Registry name	so.transcribe/mcp (domain-verified namespace)
Version	1.7.0, active, isLatest: true
Remote	https://transcribe.so/mcp, streamable HTTP
Auth	OAuth 2.1 with dynamic client registration and PKCE (discovery at /.well-known/oauth-protected-resource/mcp); a tsk_live_ API key as a Bearer token also works
Repository	https://github.com/shsunmoonlee/transcribe-agent (client plugins, skills and CLI for the hosted server)
License	MIT (client repository); the server itself is a hosted service
Docs	https://transcribe.so/developers/docs#mcp

What it does: turns a YouTube link, podcast page, media URL or upload into a transcript with speaker labels and timestamps, then lets the agent search who said what and when, ask questions answered with timestamped citations, export SRT/VTT subtitles and render captioned clips.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=so.transcribe"
curl "https://api.mcp.github.com/v0.1/servers?search=so.transcribe"   # currently 0 results

Contact: support@transcribe.so

Thanks!

[Rawilli]

Onboarding request — RowAttest (remote server)

• Registry name: com.rowattest/rowattest — https://registry.modelcontextprotocol.io/v0.1/servers?search=rowattest
• Version: 1.0.0, active, isLatest: true (published 2026-10-10)
• Package and transport: remote only — streamable HTTP at https://app.rowattest.com/mcp, API key in the Authorization header (Bearer rak_...). initialize, tools/list and server/discover answer without a key; every tools/call needs one.
• Repository: https://github.com/rowattest (organization profile; the server is a hosted service and its source is not public). Documentation: https://rowattest.com/mcp
• License: proprietary hosted service; terms at https://rowattest.com/terms
• What it does: runs an eight-stage tenant-isolation test against a staging Supabase project and issues a signed, independently verifiable attestation. The six tools let an assistant list projects, start a run, follow it, and read the findings and the signed report.
• Verification: curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=rowattest" returns the entry above; curl "https://api.mcp.github.com/v0.1/servers?search=rowattest" currently returns 0 servers.

Thank you.

[Hugo-Dz]

Hey! Could you onboard Sprite Fusion to the GitHub MCP Registry? Pixel art generation for game development :)

• Registry name: com.spritefusion/pixel-art-generator (version 1.0.0, active, latest)
• Remote: https://www.spritefusion.com/mcp (Streamable HTTP)
• Auth: OAuth 2.1, no API key needed
• Source: proprietary hosted service
• Docs: https://www.spritefusion.com/docs/pixel-art-generator/api/mcp

Cheers!

[Tumerit]

Onboarding request: io.github.Tumerit/tethered

Please consider Tethered Task Sessions for the GitHub MCP Registry and VS Code MCP gallery. We publish and maintain Tethered. It is already published in the Official MCP Registry.

Field	Value
Registry name	io.github.Tumerit/tethered
Version	0.2.6; active, isLatest: true (verified 2026-10-12)
Package / transport	MCPB from GitHub Releases, local stdio
Platform / requirements	macOS; Tethered 1.2.0+ must be installed and running on the same Mac and user account, with Task Sessions enabled, a saved profile, and Tethered Pro access
Authentication	Uses the installed app’s local authenticated connection; no hosted MCP endpoint or user-supplied cloud API key
Repository	https://github.com/Tumerit/Tethered (public distribution and integration documentation; app source is proprietary)
License	Proprietary Tethered app; no open-source/MIT license is claimed
Installation / plugins	https://github.com/Tumerit/Tethered/blob/main/Integrations/README.md
Contact	support@tetheredmac.com

What it does: Tethered is a macOS power and background-process management app. This MCP integration lets a coding assistant apply a user-created task profile while running local work, such as a build, test suite, or data-processing job.

A profile can request Automatic, Low Power, or High Power mode (where supported), keep the Mac awake using a saved Caffeinate preset, and reduce competing background activity. The user chooses whether to deprioritize selected apps or other background apps, suspend background apps, or suspend apps above a configured memory threshold. Those process actions can run throughout the session or activate when macOS reports warning or critical memory pressure, with configured exceptions and frontmost-app protection.

The agent can list saved profiles, start a session, inspect its status, report task progress, and end its session. For example: “Use my Build profile while compiling, keep the Mac awake, then end the session when the build finishes.” Ending or expiring the session releases its temporary controls and resumes apps Tethered suspended. Users configure the profiles and can end a session directly in Tethered.

Installation: The MCPB locates the required installed Tethered app and launches its bundled native adapter. The 0.2.5 launcher initialized and listed eight tools; 0.2.6 preserves that launcher and updates only metadata/documentation.

Package SHA-256: 7f144aa20fd1ff6faa1e1765f2386d192dbc4749bc2457474c7cdeef618bd462.

Registry verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.Tumerit%2Ftethered/versions/0.2.6"

GitHub MCP Registry search for Tethered currently shows no results. Please let us know if MCPB or native macOS integrations require additional installation metadata for onboarding. Thank you.

[onderceylan]

Onboarding request: ai.letsship/ship

Registry name: ai.letsship/ship
Version: 0.24.0
Transport: remote, Streamable HTTP at https://mcp.letsship.ai/mcp
Repository: github.com/letsship/mcp
License: MIT

What it does: SHIP is an agentic SDLC platform. Assign a Linear, Jira or GitHub issue to a team of AI coding agents that plans, builds, reviews and tests the change in your own GitHub repository, and opens a pull request with proof it works. The server exposes 71 tools to file a mission, follow it through its stages, send an instruction to the agent that runs next, and read the proof a run
produced, such as test traces and screenshots.

Auth: OAuth 2.1 with PKCE (S256), supporting both client ID metadata documents and dynamic client registration, so no client needs pre-registering. initialize and tools/list answer without a token; the first tool call returns 401 with WWW-Authenticate: Bearer resource_metadata=.... A SHIP personal access token also works as a bearer.

Verification:

curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=ai.letsship" | jq '.servers[0].server | {name, version, title}'

{
  "name": "ai.letsship/ship",
  "version": "0.24.0",
  "title": "SHIP"
}

Namespace ownership was proven by DNS: an apex TXT record on letsship.ai
carrying the Ed25519 public key, which is what grants ai.letsship/*

GitHub registry status: published to the official registry and resolving there, but not yet visible on github.com/mcp. Happy to supply anything else useful for onboarding.

[edwinorange]

Onboarding request for a remote server already published to the OSS registry.

Registry name: io.github.edwinorange/emboss
Version: 1.7.0 (active, isLatest: true)
Remote: https://api.getemboss.ai/mcp (Streamable HTTP; OAuth 2.1 with PKCE, RFC 9728 protected-resource metadata and dynamic client registration, or an Emboss API key as a bearer token; initialize and tools/list answer without sign-in)
Repository: https://github.com/GetEmboss-ai/emboss-claude-plugin (MIT)
What it does: makes any PDF form fillable, fills it from data or supporting documents, reads it back, and faxes the result. 27 tools, each with a title and read-only or destructive hints.
Verification: curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.edwinorange/emboss" returns the entry above; curl "https://api.mcp.github.com/v0.1/servers?search=emboss" shows it is not listed yet.

Thanks for considering it.

[podonos-eunseo]

Onboarding request: ai.onepin/onepin

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

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

Verification:

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

[KaracaTR]

Onboarding request: io.github.coredence/coredence

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

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

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

Verification:

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

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