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!

[ike4est]

Onboarding request: io.github.outcomeci/mcp-server

Please consider OutcomeCI for inclusion in the GitHub MCP Registry. Our server is now published in the official MCP Registry; the record is verified as active and isLatest: true.

Field	Value
Registry name	io.github.outcomeci/mcp-server
Version	1.0.0
Official registry entry	Active/latest record
Repository and manifest	outcomeci/mcp-server · server.json
Transport	Remote Streamable HTTP
Endpoint	https://api.outcomeci.com/v1/mcp
Authentication	Browser-based OAuth; each user signs in to OutcomeCI and authorizes a workspace
Documentation	Connection instructions and tool catalog · Setup guides
License	MIT for the repository’s documentation, metadata, and configuration examples. The hosted backend is not distributed by this repository.
Website	https://outcomeci.com

OutcomeCI connects AI assistants to workspace workflows: discover connector schemas, validate and save workflow definitions, configure triggers, and inspect run logs. Credentials are added through secure deposit links; the MCP tools expose Vault metadata rather than secret values. The server is hosted, with no local package installation required.

Verification:

curl 'https://registry.modelcontextprotocol.io/v0.1/servers/io.github.outcomeci%2Fmcp-server/versions/latest'

Happy to provide any additional metadata or validation needed for onboarding. Thank you!

[Smokefarmer]

Onboarding request for github.com/mcp: finance.genesispay/mcp

• Registry name: finance.genesispay/mcp (domain-verified namespace, genesispay.finance)
• Version: 1.8.0, status active, isLatest: true (published 2026-10-05)
• Package: npm @genesis-tech/genesispay-mcp 1.8.0, stdio (npx -y @genesis-tech/genesispay-mcp, needs GENESISPAY_AGENT_KEY)
• Remote: streamable-http https://genesispay.finance/mcp (OAuth 2.1)
• Repository: https://github.com/GenesisTechAT/genesispay-js (packages/mcp-server)
• License: MIT
• Description: Lets an AI agent find and pay for x402 APIs and products in USDC on Base, within owner-set limits enforced server-side; payments above the limit wait for the owner's approval. Non-custodial.

Verification:

$ curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=finance.genesispay/mcp"
finance.genesispay/mcp 1.8.0 — status: active, isLatest: true

[niyonx]

Onboarding request for github.com/mcp: PostOnce (io.github.postoncehq/postonce)

• Registry name: io.github.postoncehq/postonce, https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.postoncehq/postonce
• Version: 0.2.0 (active, isLatest: true, published 2026-09-30)
• Remote: Streamable HTTP https://postonce.to/mcp, OAuth 2.1 with Dynamic Client Registration (no API key needed)
• Repository: https://github.com/postoncehq/postonce-skills
• License: MIT
• Description: Publish and schedule social media posts to LinkedIn, Instagram, TikTok, YouTube, X, Threads, Bluesky, Facebook and Pinterest through each platform's official API: drafts, media upload, per-destination delivery status and automatic crossposting workflows.
• Docs: https://postonce.to/integrations/mcp

Verification:

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

Not listed yet on GitHub's side (api.mcp.github.com/v0.1/servers?search=postonce returns 0). Thank you!

[leestucker]

Onboarding request: uk.co.teas/shop

Requesting initial GitHub MCP Registry onboarding for teas.co.uk, following the process in the notes above (official registry first, then manual curation). We build and run this server ourselves.

Field	Value
Registry name	uk.co.teas/shop (domain namespace, verified by HTTP proof on teas.co.uk)
Version	1.0.2, active, isLatest
Registry entry	https://registry.modelcontextprotocol.io/v0.1/servers/uk.co.teas%2Fshop/versions/latest
Transport	Remote, Streamable HTTP at https://teas.co.uk/mcp
Auth	None needed to search, compare, keep a basket and get a checkout link. Account tools (orders, tracking, subscriptions, reward points, returns) use OAuth 2.1 with PKCE S256, dynamic client registration and client ID metadata documents; protected resource metadata at https://teas.co.uk/.well-known/oauth-protected-resource
Tools	18, each with a title and readOnlyHint / destructiveHint annotations (11 read only)
Repository	https://github.com/leestucker/teas-co-uk-mcp (listing, server.json and setup guide; the server itself is a hosted service and its source is not published)
Licence	None: proprietary hosted service
Docs	https://teas.co.uk/ai/
Privacy and terms	https://teas.co.uk/privacy-policy/ and https://teas.co.uk/terms-and-conditions/
Support	hello@teas.co.uk

teas.co.uk is a UK online tea shop. The server lets an assistant search the live catalogue of tea, coffee and hot chocolate, compare products, find recipes, build a basket and hand the customer a checkout link; payment always happens on teas.co.uk. It is in review for the Claude connectors directory and ChatGPT apps, listed on Glama, and a Docker MCP Catalog PR is open (docker/mcp-registry#5464).

Verify:

curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=uk.co.teas/shop&version=latest"

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

Thank you for considering it.

[daniel3303]

Onboarding request: io.github.daniel3303/equibles

Please consider Equibles for the GitHub MCP Registry.

• Official registry name: io.github.daniel3303/equibles
• Published version: 1.0.2 (active and latest when checked on 2026-10-05)
• Transport: remote Streamable HTTP
• Endpoint: https://mcp.equibles.com/mcp
• Authentication: OAuth sign-in or an Equibles API key in the Authorization header
• Repository: https://github.com/daniel3303/stock-market-mcp-server
• Documentation: https://equibles.com/docs/mcp
• Website: https://equibles.com
• Discovery metadata and documentation: MIT. Self-hosted implementation: AGPL-3.0 at https://github.com/daniel3303/Equibles. Hosted terms: https://equibles.com/legal/terms

Financial research for AI assistants: SEC filings and company financials, institutional holdings, insider and congressional trades, earnings-call transcripts, prices, options, and macroeconomic data. Hosted Streamable HTTP with OAuth or an API key. Free account available; paid plans provide higher limits and additional data.

Registry verification: https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.daniel3303/equibles

I maintain Equibles and can address integration or validation questions.

[CMBurnett]

Onboarding request: ai.thedesignagent/mcp

Please consider TheDesignAgent for the GitHub MCP Registry.

• Official registry name: ai.thedesignagent/mcp, with a DNS-verified namespace for thedesignagent.ai
• Published version: 0.5.2, active and latest when checked on 2026-10-06
• Package: npm @thedesignagent/mcp, stdio
• Remote: streamable HTTP at https://www.thedesignagent.ai/mcp
• Authentication: OAuth 2.1 sign-in (RFC 9728 metadata, dynamic client registration), or an optional Authorization: Bearer tda_... API key for CI
• Repository: https://github.com/CMBurnett/the-design-agent-plugin (Agent Plugins package: manifests, skills and install docs)
• License: MIT
• Website: https://www.thedesignagent.ai, with docs at https://www.thedesignagent.ai/llms.txt

What it does: a design agent in the coding agent's loop.

• Discover gives a build brief before a screen is built.
• Ux and Visual score the result for UX and visual quality, judged against the page's job.

Verification:

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

[rogeroliveira84]

Onboarding request: com.kyrodata/kyrodata

• Registry name: com.kyrodata/kyrodata (domain-verified namespace, DNS proof on kyrodata.com)
• Version: 1.0.17, active + isLatest
• Remote endpoint and auth: streamable-http at https://mcp.kyrodata.com/mcp, API key sent as Authorization: Bearer <key> (keys are created at https://kyrodata.com/user/api-keys)
• Repository: https://github.com/kyrodata/mcp
• License: MIT
• What it does: Brazilian foreign-trade data (MDIC/ComexStat exports and imports by HS/NCM code), plus crop production, supply and demand, climate readings and commodity forecasts (soybean, coffee, corn and others). Read-only tools; every comparison uses equal-length windows. Docs: https://kyrodata.com/en-US/developers
• Verification:

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

Note: it is a hosted remote server and needs an API key, so it cannot be tried without an account. Happy to adjust the listing text or add anything the curation needs.

[ykrauq]

Onboarding request for github.com/mcp: UFO CLI (io.github.krauqllc/ufo-cli)

Field	Value
Registry name	io.github.krauqllc/ufo-cli, https://registry.modelcontextprotocol.io/v0.1/servers/io.github.krauqllc%2Fufo-cli/versions/latest
Version	1.6.0-1, active, isLatest: true (published 2026-10-06)
Package and transport	MCPB bundle https://github.com/krauqllc/ufo-cli/releases/download/v1.6.0/ufo-cli-1.6.0-linux-x64.mcpb (fileSha256 bea9a60bb8e5350df6562252874f48568aa4ca97273312f1921307f2156d9d65), stdio. Linux x86_64, glibc 2.35+.
Repository	https://github.com/krauqllc/ufo-cli
License	Repository files Apache-2.0; the runtime is free for individuals and organizations under 10 people and USD 1M revenue, with paid licenses above that
What it does	Local file toolkit for AI agents, 15 tools. Finds hidden or risky content in incoming files, including text written to instruct an AI, reads them, edits Word, Excel, PowerPoint, PDF, JSON, CSV and text without breaking them (always a new copy) and returns clean copies. No network on document paths.

Verification:

$ curl -s "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.krauqllc%2Fufo-cli/versions/latest"
io.github.krauqllc/ufo-cli 1.6.0-1, status active, isLatest true, publishedAt 2026-10-06T05:04:16Z
$ curl -s "https://api.mcp.github.com/v0.1/servers?search=ufo-cli"
{"servers":[],"metadata":{"count":0,...}}

[keys-github]

Onboarding request: I need to add our mcp to the official github.com/mcp. It has already been published on the registry - https://registry.modelcontextprotocol.io/?q=lambdatest

{
  "server": {
    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
    "name": "io.github.LambdaTest/mcp",
    "description": "Agentic testing: HyperExecute jobs, test failure triage, SmartUI visual diffs, a11y audits",
    "title": "TestMu AI MCP Server",
    "repository": {
      "url": "https://github.com/LambdaTest/mcp-server-guide",
      "source": "github"
    },
    "version": "1.0.1",
    "websiteUrl": "https://www.testmuai.com/mcp",
    "remotes": [
      {
        "type": "streamable-http",
        "url": "https://mcp.lambdatest.com/mcp"
      }
    ]
  },
  "_meta": {
    "io.modelcontextprotocol.registry/official": {
      "status": "active",
      "statusChangedAt": "2026-08-03T14:45:31.974075Z",
      "publishedAt": "2026-08-03T14:45:31.974075Z",
      "updatedAt": "2026-08-03T14:45:31.974075Z",
      "isLatest": true
    }
  }
}

Please help it publish here.

[dubadub]

Onboarding request: io.github.cook-md/cook-mcp

• Registry name: io.github.cook-md/cook-mcp
• Version: 0.2.3, active + isLatest (checked 2026-10-06)
• Package and transport: npm @cookmd/mcp, stdio. Optional env COOK_RECIPES_DIR (otherwise uses the client's workspace roots)
• Repository: https://github.com/cook-md/cook-mcp
• License: MIT
• What it does: Gives agents tools over a local folder of plain-text Cooklang recipes: validate, search, scale, write recipes and .menu meal plans, build shopping lists, track a pantry, render reports. Optional cook.md login adds nutrition data and photo import.

Verification:

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

[martinvarelaa]

Requesting onboarding for dev.burnbound/mcp (published in the official MCP registry).

Burnbound lets an agent pay x402 APIs within per-agent spending rules (daily cap, per-payment limit, allowed hosts, human approval). stdio, npx -y @burnbound/mcp, one required secret (BURNBOUND_KEY). Docs: https://burnbound.dev/docs

Disclosure: I'm the author. Closed source, free beta.

[theangrydev]

Registry name: com.trafficparrot/public
Version: 1.0.1 (active, isLatest)
Remote endpoint and auth: Streamable HTTP at https://mcp.trafficparrot.com/, no authentication
Repository: https://github.com/trafficparrot/trafficparrot-mcp-public
License: MIT, for the listing repository only (README, install notes, server.json). The server is a hosted Traffic Parrot service and its code is not published.
What it does: Traffic Parrot simulates APIs and messaging. Request or withdraw a trial, read docs, send feedback.
Verification:

curl -sS "https://registry.modelcontextprotocol.io/v0/servers?search=com.trafficparrot"
{"servers":[{"server":{"$schema":"https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json","name":"com.trafficparrot/public","description":"Traffic Parrot simulates APIs and messaging. Request or withdraw a trial, read docs, send feedback.","title":"Traffic Parrot","version":"1.0.0","websiteUrl":"https://trafficparrot.com/ai/agent-trial.html","icons":[{"src":"https://trafficparrot.com/img/tp/logo4_r_gray.png","mimeType":"image/png","sizes":["500x205"],"theme":"light"},{"src":"https://trafficparrot.com/img/tp/tpfavico.png","mimeType":"image/png","sizes":["64x64"]}],"remotes":[{"type":"streamable-http","url":"https://mcp.trafficparrot.com/"}]},"_meta":{"io.modelcontextprotocol.registry/official":{"status":"active","statusChangedAt":"2026-10-06T16:49:23.466726Z","publishedAt":"2026-10-06T16:49:23.466726Z","updatedAt":"2026-10-06T16:49:23.466726Z","isLatest":false}}},{"server":{"$schema":"https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json","name":"com.trafficparrot/public","description":"Traffic Parrot simulates APIs and messaging. Request or withdraw a trial, read docs, send feedback.","title":"Traffic Parrot","repository":{"url":"https://github.com/trafficparrot/trafficparrot-mcp-public","source":"github","id":"1407660629"},"version":"1.0.1","websiteUrl":"https://trafficparrot.com/ai/agent-trial.html","icons":[{"src":"https://trafficparrot.com/img/tp/logo4_r_gray.png","mimeType":"image/png","sizes":["500x205"],"theme":"light"},{"src":"https://trafficparrot.com/img/tp/tpfavico.png","mimeType":"image/png","sizes":["64x64"]}],"remotes":[{"type":"streamable-http","url":"https://mcp.trafficparrot.com/"}]},"_meta":{"io.modelcontextprotocol.registry/official":{"status":"active","statusChangedAt":"2026-10-06T17:18:42.803986Z","publishedAt":"2026-10-06T17:18:42.803986Z","updatedAt":"2026-10-06T17:18:42.803986Z","isLatest":true}}}],"metadata":{"count":2}}

[krnel-studio]

Onboarding request: io.applyra/mcp-server

• Registry entry: io.applyra/mcp-server, version 1.6.1 (active, isLatest): https://registry.modelcontextprotocol.io/v0/servers?search=io.applyra
• Transports: remote Streamable HTTP at https://www.applyra.io/api/mcp (OAuth 2.1, dynamic client registration, PKCE S256, RFC 9728 metadata), and npm @applyra/mcp-server over stdio (APPLYRA_API_KEY)
• Repository: https://github.com/applyra-io/mcp-server (MIT)
• Description: App Store and Google Play keyword rankings, keyword scores, competitor visibility, ASO Health audits and metadata simulation for AI agents, 25 tools.
• Verification: curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=io.applyra"

[allxsmith]

Onboarding request: io.github.allxsmith/bestax-mcp

• Registry name: io.github.allxsmith/bestax-mcp
• Version: 1.14.0, active and isLatest
• Package: npm bestax-mcp, stdio
• Auth: none
• Repository: https://github.com/allxsmith/bestax/tree/main/bestax-mcp
• License: MIT
• What it does: gives coding agents the props, examples, CSS variables and Agent Skills for bestax-bulma, a React component library for Bulma v1. It answers from an index bundled in the package and makes no network requests.

Verification:

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

Not listed on GitHub's side yet (api.mcp.github.com/v0.1/servers?search=bestax returns 0). Thanks!

[sens663]

Onboarding request: ai.veripoint/mcp

Please consider Veripoint for the GitHub MCP Registry. Its official registry entry was verified as active and isLatest on 7 October 2026.

Field	Value
Registry name	ai.veripoint/mcp
Version	1.1.0, active, isLatest: true
Official entry	https://registry.modelcontextprotocol.io/v0.1/servers/ai.veripoint%2Fmcp/versions/latest
Transport	Remote Streamable HTTP
OAuth endpoint	https://veripoint.sens663.chatgpt.site/mcp
Authentication	A Veripoint workspace, linked active workspace key and client-managed OAuth
Repository	https://github.com/sens663/veripoint-mcp (public connection guide, registry metadata and tool schemas)
License	No open-source implementation or package license is claimed. This repository documents a hosted service and has no license file.
Setup guide	https://veripoint.ai/api-docs/mcp-setup

Veripoint supports private and public company financial research with evidence, saved workspace reports and usage checks. Its four tools are research_company, list_reports, get_report and get_usage. Research creates a saved report and consumes workspace allowance; the other tools read existing workspace information. Coverage varies by company and reporting period.

Verification:

curl -sS "https://registry.modelcontextprotocol.io/v0.1/servers/ai.veripoint%2Fmcp/versions/latest"
curl -sS "https://api.mcp.github.com/v0.1/servers?search=ai.veripoint%2Fmcp"

The first returned version 1.1.0, status active and isLatest true. The second returned an empty servers list with count 0. External OAuth and tool calls have not been certified by this request; the automated test client was rejected by the hosting firewall.