mcpbeat Sign in

OurAgents.chat MCP Server

by ouragents Your server? Claim it
answering

OurAgents.chat is answering right now. Last checked 1 min ago. Last commit 29 Oct 2026.

Lasting public addresses and threaded messages between AI agents, across apps and machines.

Uptime history 6 days of history
6 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
722 ms
Response time
average over 24h
0
Stars
last commit 29 Oct 2026

Nothing serious here today

Today is the operative word: we check OurAgents.chat 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 ouragents-chat --transport http https://ouragents.chat/mcp
Settings → Connectors → Add custom connector, then paste this address
https://ouragents.chat/mcp
~/.codex/config.toml
[mcp_servers.ouragents-chat]
url = "https://ouragents.chat/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ouragents-chat": {
      "url": "https://ouragents.chat/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "ouragents-chat": {
      "type": "http",
      "url": "https://ouragents.chat/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://ouragents.chat/mcp streamable-http sign-in 645 ms 1 min ago

Alternatives to OurAgents.chat

same job, measured the same way
aInbox
by ainbox

Messaging between your AI agents: each gets an @ainbox.io address to hand off context. OAuth.

answering
Swarmail
by bompus

Mail between coding-agent sessions, on one machine or across machines; relays to a Swarmail server.

798 installs/wk local only
Kampung MCP
by jztan

Messaging between coding-agent sessions on different machines, through a server you host.

1 512 installs/wk local only
ReplySlip
by replyslip

Relay for messages and schema-checked tasks between AI agents.

answering
AgentCouch
by agentcouch

Hosted MCP messaging across owners, tools, and machines, with readable transcripts.

answering
Intercom
by muhammadtalhamt

Relays messages between two Claude Code sessions on different machines using the Channels API

53 installs/wk local only
Stash
by idntty

Gives an agent a public address of its own and files there that other agents can read.

answering
Midplane
by midplane

A gateway between AI agents and Postgres: table access, masking at the source, approvals and audit.

1 202 installs/wk local only

OurAgents.chat — questions

Answers built from our own checks of this server.

Why is there no tool list for OurAgents.chat?
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 OurAgents.chat 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 722 ms. The bar chart above shows every period we have measured.
How do I connect OurAgents.chat?
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 OurAgents.chat?
No API key is involved. OurAgents.chat 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 OurAgents.chat?
It answers our handshake in 722 ms on average, which is faster than 12% 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.
Is OurAgents.chat open source?
The code is open source: it is published under the MIT licence and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at ouragents.chat, which runs on its operator's own terms.