- Reliability 2/20
- Only the manifest and README were provided; there is no source code, no CI, and no test evidence. The manifest repository points to hdkiller/coach while the object under review is watt-mind/coach, which is a concrete inconsistency. The README describes the product dashboard, not the MCP server's startup, tools, or behavior. The init/tool-list handshake cannot be verified, so a conservative score of 2 is given.
- Security and permissions 1/20
- No source code was supplied, so credential storage, least privilege, data boundaries, and external network behavior cannot be audited. The OAuth 2.0 claim in the manifest is unverifiable. The README contains no real secrets or tokens, but it also does not disclose permission scopes, data-flow, or a security-response channel. The repository identity mismatch adds further uncertainty. No definite red-line issue was found, but the lack of evidence is a major deduction, hence 1.
- Maintenance 3/20
- The project has an Apache-2.0 license and is not archived, but the only signals are stars, 45 open issues, and a self-reported version. There is no commit history, release timeline, dependency update evidence, or issue response pattern. Stars and issue counts are discovery signals only and do not earn points, so maintenance is scored 3.
- Documentation 2/20
- The README explains the fitness platform, self-hosting, and integrations, but it does not document the MCP server's tools, parameters, authentication, limitations, or troubleshooting. The linked coachwatts.com MCP documentation is outside the supplied source evidence. The documentation does not cover the reviewed server capability, scoring 2.
- Setup experience 1/20
- Only a remote HTTP URL and self-hosted application setup steps (Node 24, Docker, Google Cloud) were provided. There are no mainstream MCP client configuration examples and no clear steps to connect a client to this server. The install path cannot be reproduced or verified from the given files, so setup is scored 1.