mcpbeat Sign in

Nebula MCP Server

answering

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

Per-client memory for any AI. On a clash, the AI gets both values and is told to ask you.

Uptime history 53 days of history · worst day 92%
53 days agonow
98.9%
Uptime 24h
90 of 91 checks
—
Tools
hidden behind auth
252 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nebula does not always answer

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

run in your terminal
claude mcp add nebula --transport http https://nebula.automatoncolony.xyz/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "nebula": {
      "type": "http",
      "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 303 ms 8 min ago

Alternatives to Nebula

same job, measured the same way
Kemory
by sekondbrainailabs

Persistent memory for AI agents: connects MCP clients to your Kemory memory vault

381 installs/wk local only
Memory Bridge
by memorybridgeai

One memory for all your AI tools: Claude, ChatGPT, Cursor and any MCP client share the same notes.

answering
Funes Vault
by funesvault

Personal memory for AI agents from a vault on your Mac, with per-agent scopes and approvals

local only
Mifactory Agent Memory
by mifactory-bot

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

2 tools answering
BrainTube
by lildaddyo

Persistent AI memory over your saved YouTube videos, podcasts, articles and PDFs for any MCP client.

answering
Atlaso Memory
by atlaso

Atlaso, the AI memory layer: one shared, persistent memory for every AI tool you connect.

answering
Mem.Center
by mem

Read-only memory search and task context for AI clients. Requires a Mem.Center Pro account.

answering
Kijito
by kijito

Shared memory and mail for your AI agents. Verified with Claude Code; other MCP clients in testing.

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: 98.9% 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 90 of 91 checks got a reply (98.9%), average response time 252 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 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 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 252 ms on average, which is faster than 56% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.