MCP server for Eodly: read your team's sourced end-of-day reports and roster fro
MCP server for Eodly: read your team's sourced end-of-day reports and roster from Claude, Cursor, or any MCP client.
active Production-safe Score 94/100 http no auth
At a glance
| Endpoint | https://eodly.io/api/mcp |
|---|---|
| Source | https://github.com/layergen/eodly-mcp |
| Transport | http |
| Tools | 4 |
| Auth | none |
| First seen | 2026-08-22 19:53:18 |
| Last checked | 2026-11-17 21:51:37 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 380 / 640 ms |
| Last successful check | 2026-11-17 21:51:37 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (4)
whoami— Identify the connected Eodly workspace and the scopes this connection holds.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 whoget_report— Get the full structured content of one end-of-day report by id (KPI status, what got done, silent, slipping, blockers). Requires the reportslist_team— List the team roster for the connected workspace (name, role, department, active). Personal contact details are omitted. Requires the team:r
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:51:37 | ✓ | ✓ | 212 ms | 94 | active |
| 2026-11-17 21:36:28 | ✓ | ✓ | 379 ms | 91 | active |
| 2026-11-17 21:21:13 | ✓ | ✓ | 263 ms | 94 | active |
| 2026-11-17 21:06:05 | ✓ | ✓ | 255 ms | 94 | active |
| 2026-11-17 20:50:43 | ✓ | ✓ | 244 ms | 94 | active |
| 2026-11-17 20:35:38 | ✓ | ✓ | 325 ms | 91 | active |
| 2026-11-17 20:20:37 | ✓ | ✓ | 230 ms | 94 | active |
| 2026-11-17 20:05:36 | ✓ | ✓ | 229 ms | 94 | active |
| 2026-11-17 19:49:50 | ✓ | ✓ | 400 ms | 91 | active |
| 2026-11-17 19:34:43 | ✓ | ✓ | 285 ms | 94 | active |
| 2026-11-17 19:19:35 | ✓ | ✓ | 215 ms | 94 | active |
| 2026-11-17 19:04:20 | ✓ | ✓ | 241 ms | 94 | active |
| 2026-11-17 18:49:09 | ✓ | ✓ | 419 ms | 91 | active |
| 2026-11-17 18:33:58 | ✓ | ✓ | 467 ms | 91 | active |
| 2026-11-17 18:18:50 | ✓ | ✓ | 397 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://eodly.io/api/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/eodly-io-api-mcp # JSON