modelcontextprotocol / modelcontextprotocol/registry
Server published in Official Registry but not visible on github.com/mcp: ai.wellnessproject/wellness-project
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
- Server name:
ai.wellnessproject/wellness-project - Title: Wellness Project
- Source repo: https://github.com/turnnoblindeye/wellness-project-mcp
- Website: https://wellnessproject.ai
- Remote endpoint: https://wellnessproject.ai/api/mcp
- Transport: Streamable HTTP
- Authentication: OAuth 2.1 with Dynamic Client Registration
- Category/use case: health, fitness, nutrition, sleep, recovery, labs, and wearable data for AI assistants
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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