mcpbeat Sign in

AgentBrink MCP Server

by agentbrink-www Your server? Claim it
answering

AgentBrink is answering right now. Last checked 12 min ago.

Give your AI agent an identity: its own email, webhook, repo, secrets vault, memory and skills.

Uptime history 83 days of history · worst day 98%
83 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
181 ms
Response time
average over 24h
authentication required
Access
streamable-http

Nothing serious here today

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

run in your terminal
claude mcp add mcp --transport http https://api.agentbrink.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.agentbrink.com/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://api.agentbrink.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://api.agentbrink.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://api.agentbrink.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://api.agentbrink.com/mcp streamable-http needs auth 133 ms 12 min ago

Alternatives to AgentBrink

same job, measured the same way
Agentline NZ: email inboxes for AI assistants
by agentline

Give your AI assistant its own email inbox: send, read and catch sign-in codes. Texting coming soon.

answering
Abnormal Security MCP
by servosity

Abnormal Security email threats, cases, and reporting in your terminal and your AI agents.

local only
Dead Simple Email
by deadsimple

Give an agent its own inbox: send, receive, and pull signup codes from real email.

191 installs/wk 14 tools answering
Kira
by aibenyclaude-coder

Skills and Scars for AI agents - your agent records its failures and never repeats them.

81 installs/wk local only
Alwen
by alwen

One memory for every AI you work with: your rules, notes and decisions in your own Git repo.

answering
hush
by omarei-omoto

Team secrets your AI agent can use but never read: encrypted in the repo, value-blind tools.

130 installs/wk local only
Infernoflow
by ronmiz

Git-native memory for coding agents: gotchas, decisions and bookmarks as plain text in your repo.

567 installs/wk local only
Project Memory MCP
by kaaustubh

Persistent memory for AI coding agents — past bugs, decisions, and your corrections, in your repo.

68 installs/wk local only

AgentBrink — questions

Answers built from our own checks of this server.

Why is there no tool list for AgentBrink?
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 AgentBrink 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 181 ms. The bar chart above shows every period we have measured.
How do I connect AgentBrink?
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 will need your own credentials: it refuses anonymous clients.
Does AgentBrink need an API key?
Yes. Every time we knock, AgentBrink 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 AgentBrink?
It answers our handshake in 181 ms on average, which is faster than 75% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.