modelcontextprotocol / modelcontextprotocol/registry

Server published in Official Registry but not visible on github.com/mcp: ai.wellnessproject/wellness-project

Open
#1,627 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
7.3k
Forks
994
Avg merge
4d 12h
Merged PRs (30d)
19

Description

Description

Wellness Project is successfully published and active in the Official MCP Registry as ai.wellnessproject/wellness-project (current version 1.2.1), but it does not appear to be discoverable in the GitHub MCP Registry at github.com/mcp.

Server details
Request

Could Wellness Project be onboarded/synced into the GitHub MCP Registry at github.com/mcp? If first-time additions are still manually curated, please consider this a request for onboarding.

The public repository is intentionally a docs/catalog repository for the hosted server and contains the generated public tool catalog, schemas, connection instructions, and canonical server metadata.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No registry files, tests, or implementation entry points are identified. Start by reviewing the registry's onboarding or curation process and the Wellness Project's canonical server metadata, generated tool catalog, schemas, and connection instructions. Done means the server is discoverable at github.com/mcp.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.