mcpbeat Sign in

Vilix AI MCP Server

by appfairly Your server? Claim it
answering

Vilix AI is answering right now. Last checked 6 min ago.

Shared memory for connected AI tools. Projects, rules and skills over MCP. OAuth or API key.

Uptime history 9 days of history · worst day 96%
9 days agonow
96.7%
Uptime 24h
89 of 92 checks
Tools
hidden behind auth
579 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Vilix AI does not always answer

Over the last week it answered 98.7% 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 6 min ago.

run in your terminal
claude mcp add vilix --transport http https://api.vilix.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "vilix": {
      "url": "https://api.vilix.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.vilix]
url = "https://api.vilix.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "vilix": {
      "url": "https://api.vilix.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "vilix": {
      "url": "https://api.vilix.ai/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.vilix.ai/mcp streamable-http sign-in 733 ms 6 min ago

Alternatives to Vilix AI

same job, measured the same way
StremAI
by thomasjumper

StremAI MCP: shared memory for AI coding agents. Connected agents can recall. OAuth + local stdio.

96 installs/wk answering
Tilda MCP
by theyahia

MCP server for Tilda API — projects, pages. 3 tools.

63 installs/wk local only
XMemo
by yonro

Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.

274 installs/wk answering
Pathrule
by pathrule

Path-scoped team memories, rules and skills for Claude Code, Cursor, Codex and other MCP clients.

32 tools answering
OpenRevenue
by openrevenue

OpenRevenue analytics MCP: projects, stats, visitors, funnels, and goals via API key or OAuth.

answering
Ambix
by ambix

Your product team's shared strategic memory — an MCP server your AI tools reason over.

answering
Bhived MCP
by artkeyai

Shared knowledge graph, skills, and tool discovery for AI agents through the Model Context Protocol.

97 installs/wk local only
ContextStream MCP Server
by contextstreamio

ContextStream MCP server for code context, memory, search, and AI tools.

1 106 installs/wk local only

Vilix AI — questions

Answers built from our own checks of this server.

Why is there no tool list for Vilix AI?
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: 96.7% of checks in the last 24 hours got a reply.
Is Vilix AI working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 92 checks got a reply (96.7%), average response time 579 ms. The bar chart above shows every period we have measured.
How do I connect Vilix AI?
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 Vilix AI?
No API key is involved. Vilix AI 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 Vilix AI?
It answers our handshake in 579 ms on average, which is faster than 22% 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.