mcpbeat

Varosity MCP Server

io.github.jonkludt/varosity
not responding

Varosity is listed as active in the registry but did not answer our last check. 35 installs a week from npm.

One key for AI video, voice, music, and image across 40+ frontier models. BYOK zero markup.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 155 · avg 9 · -20% w/w
a month agotoday
Uptime history 43 hours of history · worst hour 0%
43 hours agonow
68.1%
Uptime 24h
62 of 91 checks
Tools
hidden behind auth
678 ms
Response time
average over 24h
35
Installs / week
npm and PyPI

Connect this server

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

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

Endpoints

URLTransportStateLatencyChecked
https://varosity.ai/api/mcp streamable-http answering 86 ms 7 min ago

Varosity — questions

Answers built from our own checks of this server.

Is Varosity 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 678 ms. The bar chart above shows every period we have measured.
Is Varosity still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Varosity 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 Varosity?
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 Varosity need an API key?
No. Varosity 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.
How fast is Varosity?
It answers our handshake in 678 ms on average, which is faster than 13% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Varosity?
The npm package @varosity/mcp-server was installed 35 times in the last week. Week over week that is -20%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.