mcpbeat Sign in

Nebula MCP Server

answering

Nebula is answering right now. Last checked 1 min ago.

Per-client memory for any AI. When two facts clash, the AI uses neither until you decide.

Uptime history 8 days of history
8 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
298 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Nebula 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 1 min ago.

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

Alternatives to Nebula

same job, measured the same way
AI Memory
by alphaonedev

Persistent memory for any AI — zero token cost until recall

local only
Knowl
by dat999zx

Persistent memory for Claude Code, Cursor and Codex. Facts retire when they change.

509 installs/wk answering
YourMemory
by sachitrafa

Persistent memory for AI agents. Memories decay with time and strengthen on recall.

439 installs/wk local only
Mifactory Agent Memory
by mifactory-bot

Persistent memory for AI agents across Claude, ChatGPT and any MCP client.

2 tools answering
Memory
by cortex-mem

Shared, persistent memory for AI agents — works with Claude, Kiro, Cursor, or any MCP client.

67 installs/wk local only
UseMyContext.ai
by usemycontext

Personal context for AI, written by you and never scraped: your profile and files, any MCP client.

13 tools answering
aide-memory
by aide-memory

Persistent memory layer for AI coding agents — your agent remembers what you taught it.

40 installs/wk local only
Taproot
by taproothq

Persistent memory layer for AI tools. Save and recall notes across Claude and other MCP clients.

answering

Nebula — questions

Answers built from our own checks of this server.

Why is there no tool list for Nebula?
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 Nebula working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 298 ms. The bar chart above shows every period we have measured.
How do I connect Nebula?
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 Nebula?
No API key is involved. Nebula 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 Nebula?
It answers our handshake in 298 ms on average, which is faster than 51% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.