mcpbeat Sign in

Vitalli MCP Server

answering

Vitalli is answering right now. Last checked 11 min ago.

Your own health records from Vora, Still, Stackwell and Joiva in your AI assistant (OAuth).

Uptime history 69 hours of history · worst hour 0%
69 hours agonow
68.1%
Uptime 24h
62 of 91 checks
—
Tools
hidden behind auth
314 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Vitalli does not always answer

Over the last week it answered 74.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not 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 11 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.vitalli.app
Settings → Connectors → Add custom connector, then paste this address
https://mcp.vitalli.app
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.vitalli.app"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.vitalli.app"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.vitalli.app"
    }
  }
}

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://mcp.vitalli.app streamable-http sign-in 532 ms 11 min ago

Alternatives to Vitalli

same job, measured the same way
Mednode
by mednode

Your MedNode health vault in your AI assistant — records, summaries, labs, appointments.

answering
Kvadrum
by kvadrum

Real estate agency CRM: listings, clients, leads and viewings from your AI assistant (OAuth).

answering
S
Slate
by slate-hq

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

answering
apiai.me
by apiai

Image and video AI tools and your own pipelines, run from any AI assistant.

answering
Health by Dr Brad
by drbradstanfield

Read and add to your own health record, kept in your own cloud, and get a health plan from it.

answering
ProjectPulse MCP
by alexbypa

Monitor GitHub repo health, DORA metrics and CI signals from your AI assistant.

255 installs/wk local only
Pandy Tickets for organizers
by pandy

Read your events, sales, orders and attendees from your AI assistant. OAuth sign-in, read only.

answering
MyBooking.ai
by mybooking

Run hotels, apartments, job offers and real-estate listings in MyBooking.ai from your AI assistant.

answering

Vitalli — questions

Answers built from our own checks of this server.

Why is there no tool list for Vitalli?
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: 68.1% of checks in the last 24 hours got a reply.
Is Vitalli working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 62 of 91 checks got a reply (68.1%), average response time 314 ms. The bar chart above shows every period we have measured.
How do I connect Vitalli?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form 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 Vitalli?
No API key is involved. Vitalli 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 Vitalli?
It answers our handshake in 314 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.