Helisoma MCP Server

by dalyaka Your server? Claim it

answering

Helisoma is answering right now. Last checked 13 min ago.

Your DNA wellness report for AI: caffeine, sleep, training, nutrients. Hand-checked, no diagnoses.

Uptime history 34 days of history

34 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

178 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Helisoma every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add helisoma --transport http https://api.helisoma.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "helisoma": {
      "url": "https://api.helisoma.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.helisoma]
url = "https://api.helisoma.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "helisoma": {
      "url": "https://api.helisoma.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "helisoma": {
      "url": "https://api.helisoma.com/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

URL	Transport	State	Latency	Checked
https://api.helisoma.com/mcp	streamable-http	sign-in	150 ms	13 min ago

Alternatives to Helisoma

same job, measured the same way

Vynix

by vynix

Give AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis.

41 installs/wk 17 tools answering

Session Replay

by session-replay

Read and triage bug reports captured by Session Replay for your verified domains.

answering

DevDome Analytics

by devdome

Website traffic, bot reports, realtime visitors and site health for your DevDome sites

10 tools answering

BugCatcher

by fdiosc

Bug reports, AI diagnosis, and status management for Cursor, Claude, Windsurf.

24 installs/wk local only

Codeweb

by ghostlygawd

See what your AI edits affect. Structural checks for AI code changes. 28 MCP tools, no LLM.

219 installs/wk local only

Pure Report — Neutral News

by pure

Neutral, bias-scored news for AI agents: compare left/right media-bias framing, fact-check receipts.

8 tools answering

Bring Your AI

by bringyour

No-data MCP handoff for local Claude Code to Codex harness moves. $49 lifetime.

7 tools answering

Time Tracker Timesheet Billable Hours

by theluckystrike

Track billable time from your AI chat: timers, entries, reports, CSV export. All data stays local.

14 tools answering

Helisoma — questions

Answers built from our own checks of this server.

Why is there no tool list for Helisoma?

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: 100.0% of checks in the last 24 hours got a reply.

Is Helisoma working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 178 ms. The bar chart above shows every period we have measured.

How do I connect Helisoma?

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 Helisoma?

No API key is involved. Helisoma 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 Helisoma?

It answers our handshake in 178 ms on average, which is faster than 75% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.