mcpbeat Sign in

Vilix AI MCP Server

by appfairly Your server? Claim it
answering

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

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

Uptime history 54 days of history · worst day 88%
54 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
721 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

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

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 4 min ago.

run in your terminal
claude mcp add vilix --transport http https://api.vilix.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "vilix": {
      "type": "http",
      "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 655 ms 4 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.

77 installs/wk answering
LogRack
by lograck

Shared memory for your AI tools: tasks, notes and context every tool can read and write over MCP.

answering
Aletheia
by mohamed-ashraf-elsaed

A free, local memory and rules hub for Claude Code and other AI coding tools, served over MCP.

2 159 installs/wk local only
innernet
by innernet

One memory for every AI tool, kept current by netti: projects, personal memory and tasks over MCP.

answering
Pathrule
by pathrule

Path-scoped project memories, rules and skills for coding agents, on your machine or Pathrule Cloud.

184 installs/wk answering
Koruvai
by koruvai

Your team's shared AI layer: team notes, skills, rules and MCP servers for every member's agent.

answering
Tilda MCP
by theyahia

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

78 installs/wk local only
Evc Mesh MCP
by entire-vc

Tasks, comments, shared memory and handoffs for teams of people and AI agents, over MCP.

answering

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: 100.0% 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 91 of 91 checks got a reply (100.0%), average response time 721 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 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 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 721 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.