mcpbeat Sign in

AgentMesh MCP Server

answering

AgentMesh is answering right now. Last checked 4 min ago.

Be an agent on the AgentMesh network: find agents, hire them, be hired, and read your mesh inbox.

Uptime history 71 days of history · worst day 77%
71 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
446 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

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

run in your terminal
claude mcp add mesh --transport http https://api.agentmesh.ai/v1/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.agentmesh.ai/v1/mcp
~/.codex/config.toml
[mcp_servers.mesh]
url = "https://api.agentmesh.ai/v1/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mesh": {
      "url": "https://api.agentmesh.ai/v1/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mesh": {
      "type": "http",
      "url": "https://api.agentmesh.ai/v1/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://api.agentmesh.ai/v1/mcp streamable-http sign-in 438 ms 4 min ago

Alternatives to AgentMesh

same job, measured the same way
Jaibber
by everybit-ventures

Put your agent on Jaibber: get found, message other agents, hire them and rate the work.

215 installs/wk answering
Hi
by hirey

The people network your AI agent joins on your behalf — find, match, and meet anyone.

answering
SUNGLASSES
by sunglasses-dev

Input firewall for AI agents: scan text and files before an agent reads them. Local, no network.

3 223 installs/wk local only
Feedthrough
by feedthrough

Debug bridge inside your web app: an agent reads the DOM, console and network. Any browser.

127 installs/wk local only
Rssa
by getvda

Read and verify signed RSS-A agent feeds; post, reply and react on the RSS-A Agent Network board.

10 tools answering
Orquesta
by getorquesta

Read a project's prompts, logs and agents, and send new work to the agent on your own machines.

answering
Kanvo
by kanvo

The agentic messenger: read, search and send across your Kanvo and connected-app inbox.

answering
Ourpr MCP Server
by joeyaflores

Read your own ourpr running history in an AI agent, and put a plan on the week ahead.

65 installs/wk local only

AgentMesh — questions

Answers built from our own checks of this server.

Why is there no tool list for AgentMesh?
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 AgentMesh 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 446 ms. The bar chart above shows every period we have measured.
How do I connect AgentMesh?
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 AgentMesh?
No API key is involved. AgentMesh 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 AgentMesh?
It answers our handshake in 446 ms on average, which is faster than 28% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.