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 51 days of history · worst day 0%
51 days agonow
8.8%
Uptime 24h
8 of 91 checks
4
Tools
read from the server
362 ms
Response time
average over 24h
open, no key
Access
streamable-http

Eodly does not always answer

Over the last week it answered 2.5% 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 6 min ago.

run in your terminal
claude mcp add eodly --transport http https://eodly.io/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "eodly": {
      "url": "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
{
  "mcpServers": {
    "eodly": {
      "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, shipped, silent, slipping, blockers). Requires the reports:read scope.
reports
list_reports
List recent end-of-day reports for the key's organization, most recent first. Each report summarizes who shipped, who is silent, and who is slipping. Requires the reports:read scope.
team
list_team
List the team roster for the key's organization (name, role, department, active). Personal contact details are omitted. Requires the team:read scope.
whoami
whoami
Identify the calling Eodly API key: the organization it belongs to and the scopes it holds.

Endpoints

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

Alternatives to Eodly

same job, measured the same way
AI Usage
by mohitbansal321

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

268 installs/wk local only
Session Replay
by session-replay

Read and triage bug reports captured by Session Replay for your verified domains.

answering
Dmarc Examiner
by dmarc-examiner

Read your own DMARC aggregate and forensic reports: sources, alignment, alerts, CSV export.

29 installs/wk 21 tools answering
Wisegrid MCP
by ryankramer

Read and write WiseGrid sheets, rows, columns and reports from any AI agent.

56 installs/wk local only
WitWiki
by witwiki

A shared team wiki your coding agents read and write — across every repo and every MCP client.

answering
Servd Merchant
by getservd

Run your restaurant from an AI client: orders, menu, reports, refunds, payouts and staff.

answering
Vortex Iq
by vortexiq

Read-only access to your VortexIQ store data: audits, KPIs, alerts, Brand DNA, reports, Ask VIQ.

answering
Github Gist
by ofershap

MCP server to create, read, update, list, and search GitHub Gists from your IDE

35 installs/wk local only

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 8 of 91 checks got a reply (8.8%), average response time 362 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 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.
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 362 ms on average, which is faster than 45% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.