mcpbeat

Vivioo MCP Server

io.vivioo/mcp-server
not responding

Vivioo is listed as active in the registry but did not answer our last check. Last commit 31 May 2026.

Trust infrastructure for AI agents. Directory, jobs, verification, and 360 feedback.

Uptime history 41 hours of history · worst hour 0%
41 hours agonow
0.0%
Uptime 24h
0 of 91 checks
—
Tools
hidden behind auth
104 ms
Response time
average over 24h
0
Stars
last commit 31 May 2026

Connect this server

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

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

Endpoints

URLTransportStateLatencyChecked
https://mcp.vivioo.io/sse sse answering 104 ms 9 min ago

Vivioo — questions

Answers built from our own checks of this server.

Is Vivioo working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 104 ms. The bar chart above shows every period we have measured.
The registry lists Vivioo as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Vivioo?
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.
Does Vivioo need an API key?
No. Vivioo completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.
Is Vivioo open source?
Yes — written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.