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!

[TejThimmaiah]

Onboarding request: Bastion Helix Agent Lens (com.bastionhelix/agent-lens)

Please consider Bastion Helix Agent Lens for github.com/mcp and the VS Code MCP gallery. Values read from the official registry on 2026-10-29 (UTC).

Field	Value
Registry name	com.bastionhelix/agent-lens (HTTP-verified namespace for bastionhelix.com)
Version	1.0.0, active, isLatest: true (published 2026-10-29)
Transport	Remote, Streamable HTTP: https://lens.bastionhelix.com/mcp
Auth	None for the free tools (site, preflight); optional Authorization: Bearer API key for the paid tools
Repository	No public repository: hosted service, closed source
License	Proprietary hosted service. Docs: https://bastionhelix.com/lens/docs, privacy: https://bastionhelix.com/lens/privacy
What it does	Read-only web page tool for AI agents: checks whether a page may be used (robots.txt, Content Signals) and which browser it needs, flags possible prompt injection, and reads pages as Markdown, JSON or screenshots. It never bypasses bot checks and never signs in.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.bastionhelix/agent-lens"
-> com.bastionhelix/agent-lens 1.0.0, status active, isLatest true, publishedAt 2026-10-29T02:25:00Z
curl "https://api.mcp.github.com/v0.1/servers?search=com.bastionhelix"
-> count 0 (not listed yet)

Thank you!

[EminBudak]

Onboarding request: Wiro AI (ai.wiro/mcp)

Please consider Wiro AI for github.com/mcp and the VS Code MCP gallery. Values read from the official registry on 2026-10-29 (UTC).

Field	Value
Registry name	ai.wiro/mcp (DNS-verified namespace for wiro.ai)
Version	1.3.2, active, isLatest: true (published 2026-10-29)
Package and transport	npm @wiro-ai/wiro-mcp@1.3.2, stdio
Remote endpoint	https://mcp.wiro.ai/v1, Streamable HTTP
Auth	Wiro project API key. Remote: Authorization: Bearer <API_KEY> header. Local: WIRO_API_KEY, plus the optional WIRO_API_SECRET
Repository	https://github.com/wiroai/Wiro-MCP
License	MIT
Docs	https://wiro.ai/docs/wiro-mcp-server

What it does: Official MCP server for Wiro AI. Your assistant searches the Wiro catalog, checks a model's inputs and price, runs image, video, audio and LLM models, and follows each task until the output is ready. All 13 tools carry a title and read-only/destructive hints.

Verification:

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

GitHub's registry currently returns no match for wiro.

[EminBudak]

Update for ai.wiro/mcp: version 1.3.4 is now the latest entry in the official registry. The hosted server at https://mcp.wiro.ai/v1 supports OAuth 2.1 sign-in (DCR, CIMD and PKCE), so the Authorization header is optional and VS Code can connect with just the URL. The npm package @wiro-ai/wiro-mcp@1.3.4 still covers stdio. Thanks for considering it.

[no-itsbackpack]

Onboarding request: Faxette (com.faxette/faxette, com.faxette/faxette-eu)

Please consider Faxette for github.com/mcp and the VS Code MCP gallery. It's two servers, one per region. Values read from the official registry on 2026-10-29 (UTC); GitHub Registry search currently returns no match.

Field	Value
Registry names	com.faxette/faxette (US and Canada) and com.faxette/faxette-eu (EU, UK, Switzerland and more). DNS-verified namespace for faxette.com
Version	0.3.0, active, isLatest: true (published 2026-10-29)
Transport	Remote Streamable HTTP: https://mcp.faxette.com/mcp and https://mcp.eu.faxette.com/mcp (no package; nothing to install)
Auth	Optional OAuth 2.1 with PKCE (S256) and protected resource metadata; clients register with a Client ID Metadata Document or dynamic client registration. Guest tools work without signing in; account tools return a 401 challenge
Repository	https://github.com/goosegods/faxette-plugins (server.json, plugins and skills; the server itself is hosted)
License	MIT
Docs	https://www.faxette.com/mcp, privacy: https://www.faxette.com/legal/privacy

What it does: Send a fax from a chat. The assistant finds the official fax number and uploads the files; the person checks the fax and price and pays per fax on Faxette, or from their prepaid credit.

Verification:

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

[Matthew-bk]

Onboarding request: ai.bankrolled/agent-hub

Following the OSS-registry-first / manual-curation process described in this thread (published to the Official MCP Registry first, republished as 1.5.7 with the repository linked, now requesting GitHub MCP Registry onboarding; new versions can sync after).

Field	Value
Official registry name	ai.bankrolled/agent-hub (namespace ai.bankrolled)
Latest version	1.5.7 (active, isLatest; carries the repository field): https://registry.modelcontextprotocol.io/v0.1/servers/ai.bankrolled%2Fagent-hub/versions/latest
Transport	Remote, Streamable HTTP at https://bankrolled.ai/mcp
Auth	None. Free, read-only, no key
Repository	https://github.com/Bankrolled/bankrolled-ai-mcp (README, server.json, licence and registry metadata only; the server itself is hosted and its source is not published)
Manifest	https://github.com/Bankrolled/bankrolled-ai-mcp/blob/main/server.json
License	MIT (repository contents)
Website / docs	https://bankrolled.ai/ · https://bankrolled.ai/llms.txt · https://github.com/Bankrolled/bankrolled-ai-docs
Server card	https://bankrolled.ai/.well-known/mcp/server-card.json
Privacy	https://bankrolled.ai/privacy/
Contact	agents@bankrolled.com

What it does

Free, read-only lookups of official, dated personal-finance limits for the US, UK, Canada, Australia and New Zealand: deposit insurance (FDIC, FSCS, CDIC, AU FCS, NZ DCS) and contribution limits and allowances (for example ISA, 401(k), IRA, TFSA, RRSP, super caps, KiwiSaver). Three data tools: money_fact, scheme_lookup and cross_border_check, plus pricing_list (coverage list) and health_check. Every answer names its official source and an as_of date, and unknown questions return not_in_catalog rather than a guess. All tools carry titles and annotations, nothing is billed, and the server never moves money or touches accounts.

Verification

curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=ai.bankrolled"
curl -s https://bankrolled.ai/mcp/health

The second returns ok: true, billed: false and the live server version (currently 1.5.7, matching the registry entry).

Happy to provide any further verification the curation team needs. Thank you!

[tofijak]

Onboarding request: Serpier (com.serpier/serpier)

Please consider Serpier for github.com/mcp and the VS Code MCP gallery. Values read from the official registry on 2026-10-29 (UTC); GitHub Registry search currently returns no match.

Field	Value
Registry name	com.serpier/serpier (DNS-verified namespace for serpier.com)
Version	1.0.1, active, isLatest: true (published 2026-10-29)
Transport	Remote Streamable HTTP: https://app.serpier.com/api/mcp (no package; nothing to install)
Auth	OAuth 2.1 with PKCE (S256) and protected resource metadata. Clients can register with Dynamic Client Registration or a Client ID Metadata Document.
Repository	https://github.com/Serpier/serpier-mcp (connection details, client configs and registry metadata; the server itself is a hosted service)
License	MIT (repository)

What it does: Serpier is an SEO platform for marketing teams and agencies. The server lets an assistant monitor a brand's AI Visibility (mentions and citations in ChatGPT, Gemini and others), track published articles and backlinks, and search publishers and manage link-building orders in the user's Serpier account.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.serpier/serpier"
curl "https://api.mcp.github.com/v0.1/servers?search=serpier"

[alexhawke]

Onboarding request for Raq.com (com.raq/raq)

Please consider Raq.com for onboarding to github.com/mcp.

Field	Details
Official Registry	com.raq/raq, version 1.0.0 published 16 October 2026
Transport	Remote Streamable HTTP
Endpoint	https://raq.com/mcp/agent/v1
Authentication	OAuth with PKCE, dynamic client registration and client ID metadata documents; workspace permissions apply
Setup documentation	https://raq.com/agent-start
Public connection package	https://github.com/alexhawke/raq-mcp-plugin
Licensing	The connection package is MIT licensed. The hosted Raq.com service is proprietary; the repository contains client configuration and documentation, not the server implementation.
Privacy and terms	https://raq.com/privacy and https://raq.com/terms

Raq.com connects agents to shared tasks, projects, CRM, team messages, forms and e-signatures. The authenticated endpoint exposes discovery tools and a permission-checked tool gateway.

The official Registry API timed out from our network during today's recheck; the existing entry is also visible at https://glama.ai/mcp/connectors/com.raq/raq. Happy to supply any additional onboarding details.

[jmma777-create]

Hi! Please consider adding this remote server to the GitHub MCP Registry.

Official registry name: io.github.jmma777-create/preciosdelcampo (latest version active)
Endpoint: https://preciosdelcampo.es/mcp (Streamable HTTP, no authentication, read-only tools)
What it does: Spanish agricultural prices with their official source and date: weekly farm-gate prices from the Generalitat Valenciana (citrus, fruit and vegetables, since 2017), national averages from Spain's Ministry of Agriculture and daily agricultural diesel prices by province. Free, no key needed.
Docs: https://preciosdelcampo.es/datos/mcp/

Quick test: curl -s https://preciosdelcampo.es/mcp -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Thanks!
José Manuel, preciosdelcampo.es

[saurabhrb]

Onboarding request: Microsoft Dataverse (com.microsoft/dataverse)

Please consider Microsoft Dataverse for initial onboarding to github.com/mcp, using its existing publication in the Official MCP Registry. We are following the registry-first, manual-curation process described in the accepted answer here.

• Registry name: com.microsoft/dataverse
• Version/status: 1.0.88, active, isLatest: true (verified on 2026-10-29).
• Package: @microsoft/dataverse version 1.0.88.
• Transport/runtime: local stdio, launched with npx. The published entry requires the user's Dataverse environment URL as a positional argument.
• Authentication: Microsoft Entra user sign-in. Tenant admin consent and enabling the Dataverse CLI client for the target environment are prerequisites documented in the setup guide below.
• Documentation: Microsoft Learn: connect to Dataverse using the local MCP proxy.
• License: the published npm package metadata declares MIT; this describes the package metadata, not an open-source license for the hosted Dataverse service.
• Repository: the current registry manifest does not include a public GitHub repository. The implementation source is not publicly hosted; Microsoft Learn is the public documentation reference for this request.

What it does: Query, create, and manage Microsoft Dataverse tables, records, and solutions from AI agents. This request is for the existing local npm/stdio publication, not a separate hosted-endpoint listing.

Example invocation of the published version:

npx -y @microsoft/dataverse@1.0.88 mcp https://yourorg.crm.dynamics.com

Repository/metadata clarification: Can this existing publication be onboarded as-is using the Official Registry entry, Microsoft-published npm package, and Microsoft Learn documentation? If a public GitHub README repository and a repository field in the published registry metadata are mandatory for your current intake, please confirm the minimum required so we can follow up. We are not assuming an exception is already supported.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers/com.microsoft%2Fdataverse/versions/latest"
curl "https://api.mcp.github.com/v0.1/servers?search=com.microsoft%2Fdataverse"

The first currently returns 1.0.88, active, and isLatest: true; the second returns no matching server. We would appreciate initial curation review and guidance on any remaining listing requirements. Thank you!

[paddockteam]

Please add Paddock Cards to the GitHub MCP Registry and VS Code MCP gallery.

Send birthday cards, Christmas cards, thank-you cards, sympathy cards, congratulations cards and postcards. Paddock prints and mails them for you. An assistant can choose a card, write its message, preview it, arrange delivery and complete a buyer-approved payment. The service supports postcards, flat cards and folded cards, including mixed-format batch orders.

Official registry: so.paddock/cards, version 0.1.4 (active and latest)
Registry entry: https://registry.modelcontextprotocol.io/v0.1/servers/so.paddock%2Fcards/versions/latest
Transport: remote Streamable HTTP
Public endpoint: https://api.paddock.so/agent-commerce/mcp (no sign-in or API key)
Optional connected endpoint: https://api.paddock.so/agent-commerce/mcp/connected (OAuth for saved Link connection and separately consented order history)
Website: https://paddock.so/agent-commerce/
Guide: https://paddock.so/agent-commerce/guide/
Icon: https://paddock.so/agent-commerce/icon-512.png
Contact: team@paddock.so

The current server exposes 13 tools. Customers can use Stripe-hosted checkout, or approve the exact purchase in Stripe Link and let the agent complete payment. One live Link purchase completed through a native Claude custom connector on October 29. We have verified VS Code server connection and tool discovery; we are not claiming a completed Copilot purchase test.

The server is hosted; no local package is required. Please review the existing official-registry entry for curation and let us know if you need any additional listing information.

Axel Olson
Paddock

[Deniffer001]

Requesting onboarding for Whiteboard Animation, a hosted remote MCP server.

• Registry name: ai.whiteboardanimation/whiteboard-animation (DNS-verified namespace)
• Version: 1.0.1, active + isLatest (now carries the repository)
• Remote endpoint and auth: https://mcp.whiteboardanimation.ai/mcp, streamable HTTP, OAuth 2.1 with dynamic client registration (no API key)
• Repository: https://github.com/celados/whiteboard-animation-mcp (public listing, client configs, Claude Code / Cursor plugin and agent skill; the server itself is hosted). Docs: https://whiteboardanimation.ai/mcp
• License: MIT for the repository; the hosted service is free to try (credits for new accounts)
• What it does: turns any picture (photo, sketch, diagram, or a folder of them) into a hand-drawn whiteboard animation video. The agent can quote the cost, start the drawing, follow it to completion and return a link to watch, edit or export it (MP4, transparent WebM, PNG).
• Verification:

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

Thanks!

[hafizjavaid]

Onboarding request: QuasarUI (com.quasarui/mcp)

Please consider QuasarUI for github.com/mcp and the VS Code MCP gallery. Values read from the official registry on 2026-10-30 (UTC).

Field	Value
Registry name	com.quasarui/mcp (DNS-verified namespace for quasarui.com)
Version	1.0.0, active, isLatest: true (published 2026-10-29)
Remote	Streamable HTTP: https://www.quasarui.com/mcp
Package	npm quasarui-mcp@1.0.0, stdio (npx -y quasarui-mcp)
Auth	None for Free Components. An optional Authorization: Bearer <Access Key> header (or QUASARUI_ACCESS_KEY for the npm package) unlocks Paid Components
Repository	https://github.com/quasarui/quasarui-mcp
License	MIT for the repository; the Components are covered by https://www.quasarui.com/documentation/licensing
Docs	https://www.quasarui.com/documentation/mcp-server, privacy: https://www.quasarui.com/privacy

What it does: lets an assistant search QuasarUI's Quasar Framework (Vue) UI Components, fetch a Component's Vue SFC source and follow the setup guide to paste it into a project. Five tools (list_blocks, list_components, search_components, get_component, get_setup_guide), all read-only with readOnlyHint.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.quasarui"
curl "https://api.mcp.github.com/v0.1/servers?search=quasarui"   # currently returns no match

Posted with help from an AI agent on behalf of the maintainer; values checked against the registry before posting. Thank you!

[mcooper7649]

Onboarding request: FloorFeed (io.floorfeed/floorfeed)

Please consider FloorFeed for github.com/mcp and the VS Code MCP gallery. Values were read from the official registry on 2026-10-30 (UTC).

Field	Value
Registry name	io.floorfeed/floorfeed (DNS-verified namespace for floorfeed.io)
Version	1.0.1, active, isLatest: true
Remote	Streamable HTTP, https://floorfeed.io/api/mcp
Auth	OAuth 2.1 (PKCE S256, dynamic client registration, RFC 9728 / 8414 metadata). Unauthenticated requests get 401 + WWW-Authenticate
Repository	None: hosted, closed-source service. Docs at https://floorfeed.io/mcp
License	Proprietary (hosted service). Terms: https://floorfeed.io/terms

What it does: NFT market data on 12 networks (floors, real sales, traders' profit after fees, live mints), plus the signed-in user's own wallets and holdings if they allow it. Optional prepare-only trade requests the user signs in their own wallet. It's non-custodial: it never holds keys or signs anything.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.floorfeed/floorfeed"
# io.floorfeed/floorfeed 1.0.1 active isLatest=true remotes=[streamable-http https://floorfeed.io/api/mcp]
curl "https://api.mcp.github.com/v0.1/servers?search=io.floorfeed"
# {"servers":[], ... "total":0}   (not listed yet)

Thanks!

[n7studios]

Onboarding request: Social Post Flow (com.socialpostflow/mcp)

Please consider Social Post Flow for github.com/mcp and the VS Code MCP gallery. Values were read from the official registry on 2026-10-30 (UTC).

Field	Value
Registry name	com.socialpostflow/mcp (DNS-verified namespace for socialpostflow.com)
Version	1.0.0, active, isLatest: true
Remote	Streamable HTTP, https://app.socialpostflow.com/mcp
Auth	OAuth 2.1 (PKCE S256, dynamic client registration, RFC 9728 / 8414 metadata). Unauthenticated requests get 401 + WWW-Authenticate
Repository	https://github.com/socialpostflow/socialpostflow-cli (CLI). The MCP server itself is a hosted, closed-source service. Docs at https://www.socialpostflow.com/documentation/mcp/
License	Proprietary (hosted service). Terms: https://www.socialpostflow.com/terms/

What it does: Schedule and publish social media posts to Facebook, X, LinkedIn, Instagram, Threads, Pinterest, TikTok, Bluesky, Mastodon, Telegram and Google Business Profile. Tools list connected profiles and create, schedule, update and delete posts. All tools carry read-only/destructive annotations.

Verification:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.socialpostflow/mcp"
# com.socialpostflow/mcp 1.0.0 active isLatest=true remotes=[streamable-http https://app.socialpostflow.com/mcp]
curl "https://api.mcp.github.com/v0.1/servers?search=com.socialpostflow"
# {"servers":[], ... "total":0}   (not listed yet)

Thanks!

[ericili]

Requesting onboarding for me.pouch/agents (official MCP Registry, version 1.0.1, active, isLatest). Remote streamable HTTP at https://agents.pouch.me/mcp, no authentication, hosted service (no public repo). Custom printed pouches (Pouch.me) and labels (Inkable): specs, bag-type suggestions, confirm-to-send quote requests, label prices. Check: curl "https://registry.modelcontextprotocol.io/v0/servers?search=me.pouch"

[meestierolff]

Please consider TrendsFast for inclusion in the GitHub MCP Registry.

• Registry name: com.trendsfast/trends
• Official entry: https://registry.modelcontextprotocol.io/v0.1/servers?search=com.trendsfast/trends
• Version: 3.0.0; verified active and isLatest: true on 2026-10-30.
• Remote transport: Streamable HTTP at https://trendsfast.com/api/mcp/v3
• Authentication: project API key in the Authorization bearer header (as declared in the registry manifest); the service also exposes OAuth authorization-code/PKCE metadata.
• Public integration repository: https://github.com/meestierolff/trendsfast-open
• License: MIT for the public agent kit and documentation; the hosted service backend is proprietary and credit-based.
• Purpose: sourced niche trend and customer intelligence for agents, with observation dates, measured signals, and explicit coverage limits. Public discovery exposes seven tools.

Verification: curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=com.trendsfast/trends". The equivalent query against https://api.mcp.github.com/v0.1/servers?search=com.trendsfast/trends returned zero entries. No prior TrendsFast request was found in this thread.

Thank you for reviewing.