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!

[walidelhelw]

Onboarding request: EL7.AI (ai.el7/mcp)

Published to the open-source MCP Registry first, per the notes above. Values read from the registry on 2026-11-04.

Field	Value
Registry name	ai.el7/mcp (DNS-verified namespace el7.ai)
Version	1.1.0, active, isLatest: true
Remote endpoint	https://mcp.el7.ai/mcp (streamable HTTP)
Auth	OAuth 2.1 (PKCE, dynamic client registration; discovery via /.well-known/oauth-protected-resource/mcp), or a per-user API key as a Bearer token
Repository	https://github.com/walidelhelw/el7-mcp (docs, client configs, icons)
License	MIT for the repository contents; the hosted service is proprietary
What it does	Financial market intelligence for your AI: markets news, economic calendar, 8 central banks, COT positioning, stocks, earnings, gold and oil. 82 read-only tools; every answer carries its source date and an el7.ai link. English first, with full Arabic support.

Verification

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

Docs: https://el7.ai/en/mcp

[komako-workshop]

Onboarding request: Stringers / 什么值得做 (io.github.komako-workshop/stringers)

Published to the open-source MCP Registry first, per the notes above. Values read from the registry on 2026-11-04.

Field	Value
Registry name	io.github.komako-workshop/stringers
Version	0.2.0 (active, isLatest)
Transport	Remote, streamable HTTP: https://stringers.io/mcp/{token}
Auth	Per-user token in the URL path (registry variables, isSecret); free token at https://stringers.io
Repository	https://github.com/komako-workshop/stringers
License	MIT

What it does: daily, evidence-backed verdicts on which small-product directions are worth building for indie developers and small teams, plus read-only access to the 15 data libraries behind them (payment-verified indie revenue, App Store / Google Play charts, ad libraries, GitHub, Product Hunt, Hacker News, X). Tools: today, directions, direction, data. Content is in Chinese.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.komako-workshop/stringers"

[cdutsov]

Request to add ch.overpass/overpass to github.com/mcp

Registry name	ch.overpass/overpass
Version	1.0.0 (active, latest)
Remote	https://api.overpass.ch/v1/mcp (Streamable HTTP)
Auth	API key in X-API-Key or Authorization: Bearer. Public sign-up with a free plan at https://overpass.ch/signup. initialize and tools/list answer without a key.
Tools	overpass_query, overpass_examples, geocode, reverse_geocode, elevation, elevation_profile, account_status (all read-only)
Website	https://overpass.ch/guides/overpass-mcp-server
Repository	https://github.com/cdutsov/overpass-mcp (documentation and server.json; the server is hosted)
License	Hosted service; data © OpenStreetMap contributors, ODbL
Description	Overpass API on the full planet with history, plus geocoding and elevation. Needs an API key.

Check:

curl -s 'https://registry.modelcontextprotocol.io/v0/servers?search=ch.overpass'

[fonciq-dev]

Onboarding request: ca.fonciq/fonciq

Field	Value
Registry name	ca.fonciq/fonciq (domain-verified namespace)
Version	1.1.2 (active, isLatest)
Transport	Remote, streamable HTTP: https://mcp.fonciq.ca/v1/
Auth	OAuth 2.1 (dynamic client registration + PKCE, via fonciq.ca) or API key
Repository	Hosted remote server; source is private
License	Proprietary hosted service
Docs	https://mcp.fonciq.ca and https://fonciq.ca/mcp
What it does	Connects AI assistants to Québec land and property workflows for notaries, brokers, appraisers and firms. Independent service, not affiliated with the Registre foncier du Québec or the Government of Québec.

Also listed in Claude's connector directory: https://claude.ai/directory/fonciq

Verification:

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

[tidybytetools]

Onboarding request: three small local servers from Tidy Byte Tools (io.github.tidybytetools/*)

These are published to the open-source MCP Registry first, as the notes above ask. I read the values from the registry on 2026-11-04. All three are Python packages on PyPI that run over stdio. They're MIT licensed and need no API key or auth.

Registry name	Version	Package / transport	Repository	What it does
io.github.tidybytetools/pdf-table-pull-lite	1.2.1 (active, isLatest: true)	PyPI pdf-table-pull-lite, stdio	https://github.com/tidybytetools/pdf-table-pull-lite	Pulls tables out of local text PDFs as CSV.
io.github.tidybytetools/doc2md-lite	1.1.1 (active, isLatest: true)	PyPI doc2md-lite, stdio	https://github.com/tidybytetools/doc2md-lite	Turns local text PDFs and HTML into Markdown and keeps tables as tables.
io.github.tidybytetools/link-check-lite	1.1.1 (active, isLatest: true)	PyPI link-check-lite, stdio	https://github.com/tidybytetools/link-check-lite	Checks a list of links and reports status codes, final URLs and redirects.

License: MIT for all three. Auth: none.

Verification:

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

None of them are on GitHub's side yet. curl "https://api.mcp.github.com/v0.1/servers?search=tidybytetools" returns 0 results.

[shangxiang0907]

Onboarding request: ApplyKoala (com.applykoala/mcp)

Published to the open-source MCP Registry first, as the notes above ask. I read the values from the registry on 2026-11-04.

Registry name	Version	Transport	Auth	What it does
com.applykoala/mcp (domain-verified)	1.0.0 (active, isLatest: true)	Remote, streamable HTTP: https://applykoala.com/mcp	OAuth (the user signs in to their ApplyKoala account)	A job-search record for your AI: it saves job postings, researches companies, keeps your career stories, tracks applications and runs mock interviews.

Repository: none public. ApplyKoala is a hosted service; the source is private.
License: proprietary (hosted service).
Website: https://applykoala.com/mcp

Verification:

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

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

Thanks!

[alexanderbering]

Onboarding request: ZenBrain (ai.zensation/zenbrain)

Published to the official MCP Registry first, per the notes above. Values read from the registry on 2026-11-04.

Field	Value
Registry name	ai.zensation/zenbrain
Version	0.3.1, status: active, isLatest: true
Package and transport	npm @zensation/mcp 0.3.1, stdio (npx -y @zensation/mcp)
Repository	https://github.com/zensation-ai/zenbrain
License	Apache-2.0
What it does	Long-term memory for agents: five tools (store, recall, forget, consolidate, health) over one local SQLite file, no account and no network call of its own. Published to npm with build provenance.

Verification:

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

[carlsverre]

Onboarding request: Antithesis Snouty (com.antithesis/snouty)

Published to the official MCP Registry first, per the notes above. Values were read from the registry on 2026-11-04.

Field	Value
Registry name	com.antithesis/snouty
Version	v0.9.0, status: active, isLatest: true
Package and transport	npm snouty 0.9.0, stdio (npx -y snouty)
Repository	https://github.com/antithesishq/snouty
License	Apache-2.0
What it does	Provides access to the Antithesis API optimized for Agents. Tools for querying and managing Antithesis runs, documentation, and configuration.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.antithesis/snouty"

[BDYCTRL]

Onboarding request: Buzzmark (ai.buzzmark/mcp)

Published to the open-source MCP Registry first, per the notes above. Values read from the registry on 2026-11-04.

Field	Value
Registry name	ai.buzzmark/mcp (domain-verified namespace, HTTP proof on buzzmark.ai)
Version	1.0.0, status: active, isLatest: true
Remote endpoint	https://buzzmark.ai/mcp (streamable HTTP)
Auth	OAuth 2.1 with PKCE (S256), dynamic client registration and client ID metadata documents, public clients
Repository	https://github.com/piiklabs/buzzmark-cursor-plugin (public plugin repo; the server itself is a hosted service)
License	Proprietary hosted service; plugin repo MIT
Publisher	Piik Labs AB (Sweden)
Docs	https://buzzmark.ai/ai-apps/mcp
What it does	A ghostwriter that writes, plans and schedules social media posts for founders and growing businesses, in their own voice, on Instagram, LinkedIn, Facebook, X, Threads and TikTok. It never posts on the spot: it saves drafts and schedules posts onto the user's Buzzmark calendar.

Verification:

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

[obkaro]

Onboarding request: Worktable (io.github.worktable/worktable)

Published to the open-source MCP Registry first, per the notes above. Values read from the registry on 2026-11-04.

Field	Value
Registry name	io.github.worktable/worktable (GitHub org namespace, published through GitHub Actions OIDC)
Version	0.1.39, status: active, isLatest: true
Transport	Remote, streamable HTTP: https://app.worktable.cloud/api/mcp
Auth	OAuth 2.1 (dynamic client registration and client ID metadata documents, PKCE)
Repository	https://github.com/worktable/worktable-dev
License	AGPL-3.0
What it does	An open-source workspace where people and their agents create and revise Docs, interactive HTML tools, drawings and structured Records, with comments and threads between them.

Each stable release republishes automatically from the repository's workflow.

Verification:

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

[arpit551]

Onboarding request for the GitHub MCP Registry:

• Registry name: com.flownato/flownato-mcp
• Version: 1.0.0, status active, isLatest: true
• Transport: remote, Streamable HTTP at https://agent.flownato.com/mcp
• Auth: OAuth 2.1 authorization code with PKCE (protected-resource metadata at https://agent.flownato.com/.well-known/oauth-protected-resource/mcp)
• Repository: https://github.com/flownato/flownato-mcp
• License: MIT
• What it does: read-only mobile UI/UX research for designers and developers. It searches real app screens, user flows and UI patterns, and every answer links the source screens. Public sign-up; a free account can use every tool.
• Check:

  curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=com.flownato/flownato-mcp"
  

Thank you!

[Davidobot]

Onboarding request: Ink (ist.ego.ink/ink)

Published to the official MCP Registry first, per the notes above. Values were read from the registry on 2026-11-04.

Field	Value
Registry name	ist.ego.ink/ink (domain-verified namespace)
Version	0.1.0, active, isLatest: true
Transport	Remote, Streamable HTTP at https://ink.ego.ist/mcp
Auth	OAuth 2.1 with S256 PKCE, DCR or CIMD, scope ink.rewrite. Protected resource metadata at https://ink.ego.ist/.well-known/oauth-protected-resource/mcp
Repository	The server is a hosted service. The open client plugin is at https://github.com/Egoist-Machines/ink-claude-plugin
License	Hosted service under the Ink terms. The client plugin is MIT
What it does	Rewrites pasted drafts into plain, natural wording while keeping the meaning, and warns if a name, number, date, quote, citation or link drops out.
Docs	https://ink.ego.ist/agents and https://ink.ego.ist/auth.md

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=ist.ego.ink"

Not yet listed on GitHub's side (https://api.mcp.github.com/v0.1/servers?search=ist.ego.ink returns 0 results).

Publisher: Egoist Machines, Inc. Contact: support@ego.ist

[mcpserverlister]

Requesting manual onboarding to the GitHub MCP Catalog.

• Registry name: io.github.sudomichael/mcpserverlist-mcp
• Version: 0.1.0; official registry status: active; isLatest: true
• Remote endpoint: https://mcpserverlist.io/mcp; transport: streamable HTTP; authentication: none
• Repository: https://github.com/sudomichael/mcpserverlist-mcp
• License: MIT
• What it does: Check if your MCP server is ready for MCP directories, then get it submitted.

Verification:

curl 'https://registry.modelcontextprotocol.io/v0.1/servers/io.github.sudomichael%2Fmcpserverlist-mcp/versions/0.1.0'

This requests curation review; it does not assert catalog acceptance.

[khmuhtadin]

Onboarding request: 1ToolRing

• Registry name: com.1toolring/mcp (domain-verified namespace, HTTP auth on 1toolring.com)
• Version: 1.0.1, active, isLatest: true
• Remote endpoint and auth: https://mcp.1toolring.com/mcp, streamable HTTP, OAuth 2.1 (dynamic client registration, PKCE); an API key as a Bearer token also works
• Repository: https://github.com/khmuhtadin/1toolring-mcp (public connection details and client configs; the server is hosted)
• License: MIT (repository contents); service terms at https://1toolring.com/terms/
• What it does: one key and one prepaid balance for live data AI agents need: Google search results, keyword and SEO data, Google Maps places, e-commerce prices and exchange rates. Four tools (discover_tools, inspect_tool, run_tool, get_tool_run) with title and readOnly/destructive annotations; the price is shown before every run and failed runs are not charged.
• Verification:

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

Thanks!

[Oltramare-AI]

Onboarding request: Antevo Tremor Watch (ch.antevo/tremor-watch)

Thank you for onboarding the four Antevo servers from our request of 18 October. They are live on github.com/mcp. This is the one server we have published since then. It uses the same domain-verified namespace and the same repository, and it was checked active and isLatest: true on 5 November 2026.

Field	Tremor Watch
Registry name	ch.antevo/tremor-watch
Version	1.0.0
Remote (streamable HTTP)	https://api.antevo.ch/mcp/tremor/mcp
Auth	none
Repository	https://github.com/ANTEVO-CH/antevo-mcp (MIT)
Documentation	https://antevo.ch/tremor-watch/

What it does: each week, it counts how many of 753 market relationships broke from their own past, by family and by pair. This is the Antevo Tremor Index, which goes back to 1997. It has four read-only tools and needs no account.

Verification

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=ch.antevo%2Ftremor-watch"
curl "https://api.mcp.github.com/v0.1/servers?search=ch.antevo"   # four of five today; tremor-watch missing

Thank you. Contact: contact@antevo.ch