UNBLOCK MCP Server

by kaeva-labs Your server? Claim it

answering

UNBLOCK is answering right now. Last checked moments ago.

UNBLOCK org-brain — shared memory and comms for human + agent teams. By Kaeva Labs.

Uptime history 17 days of history · worst day 99%

17 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

335 ms

Response time

average over 24h

API key or OAuth

Access

streamable-http

Nothing serious here today

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

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add unblock --transport http https://mcp.kaeva.app/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "unblock": {
      "url": "https://mcp.kaeva.app/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.unblock]
url = "https://mcp.kaeva.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "unblock": {
      "url": "https://mcp.kaeva.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "unblock": {
      "url": "https://mcp.kaeva.app/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.kaeva.app/mcp	streamable-http	needs key	379 ms	0 min ago

Alternatives to UNBLOCK

same job, measured the same way

memsprout

by memsprout

shared AI-context layer for teams — persistent memory your agents search and update over MCP

answering

TeamShared

by xhad

Shared memory for coding agents. Stop re-explaining your codebase every session.

92 tools answering

Agent Memory OS

by yamantaka520

Local-first memory engine for AI-agent teams: team/project ACL, recall, and federated sync.

1 003 installs/wk local only

BrainBrainBrains

by aiaiohhh

Persistent memory + context layer for AI dev teams. 17 tools via MCP.

39 installs/wk local only

Robells

by robells

The shared task board for teams and their AI agents — connect over OAuth, every action signed.

answering

OneLore

by onelore

Shared project context for AI agents and teams: docs, tasks, and messages that stay current.

answering

Hubd

by bzdos

The project tracker for teams of humans and AI agents — in plain files. MCP server + CLI.

117 installs/wk local only

FrameOn

by frameonlab

Shared project memory for teams: read projects and tasks, write updates and wiki decisions.

answering

UNBLOCK — questions

Answers built from our own checks of this server.

Why is there no tool list for UNBLOCK?

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 UNBLOCK 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 335 ms. The bar chart above shows every period we have measured.

How do I connect UNBLOCK?

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 will need your own key or an OAuth login: it refuses anonymous clients.

Does UNBLOCK need an API key?

Yes. Every time we knock, UNBLOCK answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is UNBLOCK?

It answers our handshake in 335 ms on average, which is faster than 53% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.