mcpbeat Sign in
not responding

Eodly is listed as active in the registry but did not answer our last check. It exposes 4 tools.

Read your team's end-of-day reports and roster from Eodly.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 91 days of history · worst day 0%
91 days agonow
18.5%
Uptime 24h
17 of 92 checks
4
Tools
read from the server
229 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 7 October 2026. No other catalogue keeps this.

18 Oct 2 tool descriptions were rewritten get_report, list_reports
7 Oct 3 tool descriptions were rewritten list_reports, list_team, whoami

Eodly does not always answer

Over the last week it answered 23.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

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 0 min ago.

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

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

report
get_report
Get the full structured content of one end-of-day report by id (KPI status, what got done, silent, slipping, blockers). Requires the reports:read scope.
reports
list_reports
List recent end-of-day reports for the connected workspace, most recent first. Each report summarizes what got done, who is silent, and who is slipping. Requires the reports:read scope.
team
list_team
List the team roster for the connected workspace (name, role, department, active). Personal contact details are omitted. Requires the team:read scope.
whoami
whoami
Identify the connected Eodly workspace and the scopes this connection holds.

Endpoints

URLTransportStateLatencyChecked
https://eodly.io/api/mcp streamable-http answering 83 ms 0 min ago

Alternatives to Eodly

same job, measured the same way
Eodly MCP
by layergen

Read your team's end-of-day reports and roster from Eodly. Sign in with OAuth or use an API key.

83 installs/wk 4 tools answering
Rollstack
by rollstack

Build, refresh and send Rollstack reports and slide decks from your company's data.

59 tools answering
Ybug
by ybug

Read, filter and triage Ybug website feedback and bug reports from your AI assistant

answering
Shipday
by shipday

Manage Shipday orders, drivers, driver earnings, reports from your AI assistants.

answering
Fastero
by fastero

Query your databases and build dashboards, Streamlit apps and reports your team logs in to.

answering
Reviewflowz
by reviewflowz

Read, tag, assign and report on your customer reviews from 200+ platforms in Reviewflowz.

answering
AI Usage
by mohitbansal321

Reports real token usage and cost from Claude Code and OpenCode data. Nothing leaves your machine.

229 installs/wk local only
Replyhand
by replyhand

Run your Replyhand inbox, contacts, AI agent and reports from your own AI assistant.

answering

Eodly — questions

Answers built from our own checks of this server.

What can Eodly do?
It exposes 4 tools, read directly from the server on our last check. Among them: get_report, list_reports, list_team, whoami. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Eodly working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 17 of 92 checks got a reply (18.5%), average response time 229 ms. The bar chart above shows every period we have measured.
Is Eodly still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Eodly as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Eodly?
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.
Does Eodly need an API key?
No. Eodly completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Eodly?
It answers our handshake in 229 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.