mcpbeat Sign in

Cohearence MCP Server

by tcrichards Your server? Claim it
answering

Cohearence is answering right now. Last checked 4 min ago.

Track, curate, and analyze data about your health, habits, and goals.

Uptime history 48 days of history · worst day 99%
48 days agonow
98.9%
Uptime 24h
91 of 92 checks
Tools
hidden behind auth
498 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Cohearence missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add cohearence --transport http https://api.cohearence.app/mcp/
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "cohearence": {
      "url": "https://api.cohearence.app/mcp/"
    }
  }
}
~/.codex/config.toml
[mcp_servers.cohearence]
url = "https://api.cohearence.app/mcp/"
.cursor/mcp.json
{
  "mcpServers": {
    "cohearence": {
      "url": "https://api.cohearence.app/mcp/"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "cohearence": {
      "url": "https://api.cohearence.app/mcp/"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://api.cohearence.app/mcp/ streamable-http sign-in 452 ms 4 min ago

Alternatives to Cohearence

same job, measured the same way
freddy
by freddy

Connect your wearables, rings and training apps, then ask your AI about your own health data.

answering
Keypup Engineering Analytics
by keypup

Generate answers & visualizations from your engineering data to track software development health.

answering
C
MakeMeBetter AI
by rohithmariyala

Manage your MakeMeBetter AI tasks, habits, and goals from your AI assistant.

answering
YOUB
by youb

Manage your endurance training data and race preparation

answering
U
Slate
by slate-hq

Your own SLATE health data in your AI assistant: read, trend, plan and log. Never suggests a dose.

answering
Scispot
by scispot

Turn any LLM into your lab assistant: search samples, track experiments, analyze data with AI.

answering
Eutexa CRM
by eutexa

Search contacts, track deals, create tasks and log notes in your Eutexa CRM workspace.

answering
Pkgdiet
by om-tajne

Put your node_modules on a diet - find unused dependencies, analyze health, and reduce size

79 installs/wk local only

Cohearence — questions

Answers built from our own checks of this server.

Why is there no tool list for Cohearence?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 98.9% of checks in the last 24 hours got a reply.
Is Cohearence working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 92 checks got a reply (98.9%), average response time 498 ms. The bar chart above shows every period we have measured.
How do I connect Cohearence?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Cohearence?
No API key is involved. Cohearence answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Cohearence?
It answers our handshake in 498 ms on average, which is faster than 29% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.