Health · Remote MCP server
Cohearence
Track, curate, and analyze data about your health, habits, and goals.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.TCRichards/cohearence- Version
- 1.0.8
- Status
- Active
- Category
- health
- Transport
- Streamable HTTP
- Published
- 2026-07-05
- Updated
- 2026-07-05
- Publisher
- TCRichards (GitHub)
- Website
- cohearence.app
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.cohearence.app/mcp/ | None |
How to connect Cohearence
Cohearence is a remote MCP server: there is nothing to install. Its endpoint is https://api.cohearence.app/mcp/, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More health servers
| Server | Runs |
|---|---|
| Coach MCPYour endurance training data in your AI assistant: activities, recovery, plan, workout edits. | Remote · HTTP |
| Coach WattsRemote MCP server for training, nutrition, wellness, and performance data with OAuth 2.0. | Remote · HTTP |
| Cochrane Medical ReviewsSystematic medical reviews and evidence-based healthcare research. | Remote · HTTP |
| Codesentinel MCPCodebase health MCP: dead code, cycles, coupling, architectural drift. | Local · stdio |
| Compete Competitive IntelligenceTyped access to monitored competitive changes, evidence, dossiers, research, and collection health. | Local · stdio |
| Constat MCP — FDA Device Evidence LifecycleFDA and CMS evidence for AI medical devices: 510(k), postmarket, reimbursement, and compliance. | Remote · HTTP |
| Context First MCP37-tool MCP server: context health, memory, reasoning, truthfulness & research pipeline. | Local · stdio |
| context-doctorProfile LLM context: token breakdown, wasted-context findings and fixes for chats and agents. | Local · stdio |