io.github.theluckystrike/delivery-schedule
mcp-delivery-schedule
io.github.theluckystrike/delivery-schedule costs 2 528 tokens of context per session. It has 12 tool definitions. That is 1.3 % of a 200k window. Measured 2026-10-03.
Dated deliverables against a quote or work order: due dates, sign-off, what is late, milestones.
alive probed 2026-10-03 · HTTP 200
12tools
2.5ktokens for the tool definitions
1.3 %of a 200k context window
71 msto initialize
44 msto list tools
- Endpoint
- https://mcp.zovo.one/mcp/delivery-milestones (streamable-http)
- Host
- mcp.zovo.one
- Protocol
- 2025-11-25
- Reports itself as
- mcp-delivery-schedule 0.22.0
- Capabilities
- prompts, resources, tools
- Instructions
- none
- Repository
- https://github.com/theluckystrike/mcp-servers
- Website
- https://mcp.zovo.one/s/delivery-schedule
- Registry
- active, updated 2026-09-26 · registry entry
- Reachable
- 2 of the last 2 probes
Most expensive tools
| Tool | Tokens | Share of this server |
|---|---|---|
| deliverable_add | 362 | 14 % |
| delivery_schedule_create | 356 | 14 % |
| deliverable_status | 289 | 11 % |
| late_report | 236 | 9 % |
| milestone_payload | 230 | 9 % |
Same tool set as 1 other server
These registry entries have the same tool names and the same schema sizes.
- io.github.theluckystrike/milestone-schedule mcp.zovo.one
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Tokens |
|---|---|---|---|---|
| 2026-10-03 20:40 | alive | 71 ms | 12 | 2.5k |
| 2026-10-03 17:55 | alive | 62 ms | 12 | 2.5k |
Badge
[](https://mcp-pulse.ulehla.dev/s/io.github.theluckystrike/delivery-schedule)