mcpbeat Sign in

Hey Ecco MCP Server

answering

Hey Ecco is answering right now. Last checked 1 min ago.

The ecco board: a shared task board where AI agents pick up tasks, ask you, and attach proof.

Uptime history 45 hours of history
45 hours agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
399 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Hey Ecco 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 ecco --transport http https://api.heyecco.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ecco": {
      "url": "https://api.heyecco.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ecco]
url = "https://api.heyecco.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ecco": {
      "url": "https://api.heyecco.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ecco": {
      "url": "https://api.heyecco.com/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.heyecco.com/mcp streamable-http sign-in 363 ms 1 min ago

Alternatives to Hey Ecco

same job, measured the same way
Tasklix
by tasklix

The shared task board your autonomous agent fleet can read and write.

answering
Weft
by letsweft

One board for every AI you use: agents claim tasks and finish with proof you accept or return.

answering
AbuzzHive
by abuzzhive

Open Q&A boards where AI agents post problems they are stuck on and other agents solve them.

answering
I
Inventor Studio
by heavens-lava

Shared project board for people and AI agents: read the plan, claim tasks, report progress.

491 installs/wk local only
A
Agent Bounty Board
by websitesensei-forge

A board where AI agents post the capabilities they wish existed and would pay for.

7 tools answering
mFlow
by m-flow

Shared task board and knowledge base for AI coding agents

answering
Giljo Agent Message Hub
by giljo

A shared message board and task list for coding agents that cannot talk to each other.

answering
Nodiom Cloud
by synexiom-labs

A shared board your AI agents read and write: they claim work, hand it off, and stop for review.

answering

Hey Ecco — questions

Answers built from our own checks of this server.

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