# Epoch Calculator Time and date math that language models get wrong on their own: Unix timestamps, daylight-saving offsets, calendar arithmetic, and cron schedules. Every calculation uses the IANA time zone database, the same engine behind [epochcalc.com](https://epochcalc.com). No API key, no signup, no state. Read-only. ## Tools | Tool | What it does | |---|---| | `time_now` | Current time in any zone, with epoch seconds, ISO 8601, RFC 2822, and DST flag | | `convert_timestamp` | Unix timestamp (seconds or milliseconds, auto-detected) to a full date breakdown | | `parse_datetime` | Natural or ISO date string to timestamp and zone-aware fields | | `convert_timezone` | Same instant in two zones, with the hour difference and DST status of each | | `date_duration` | Days, weekdays, weeks, and calendar breakdown between two dates | | `epoch_math` | Add or subtract years, months, weeks, days, hours, minutes, or seconds | | `cron_next_runs` | Plain-English explanation of a cron expression plus its next N run times | | `days_until` | Countdown to a named holiday or event, or list the supported events | ## Notes - Time zones are IANA names such as `America/New_York` or `Europe/Berlin`. Abbreviations like `EST` are ambiguous and rejected. - Endpoint: `https://epochcalc.com/mcp` (Streamable HTTP, stateless). A plain JSON API for the same tools is at `https://epochcalc.com/api/v1`. - Documentation: [epochcalc.com/api](https://epochcalc.com/api)
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 81.5/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (1256 ms). |
| Protocol revision | 6/10 | Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 8 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 52% of peers
- This listing 81 · peer median 81
- Latency
- Faster than 44% of peers
- This listing 380 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Freshness + modern flags −5
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
- Protocol revision −4
— Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/cmunkres/epochcalc/mcpcurl -X POST https://server.smithery.ai/cmunkres/epochcalc/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'