Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Epoch Calculator is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Unix timestamps, DST-aware time zone conversion, durations, cron schedules, and holiday countdowns
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http epoch-calculator-mcp https://epochcalc.com/mcp
# 2 — ask your agent for something these tools do
# time_now, convert_timestamp, parse_datetime and 5 more
Epoch Calculator costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http epoch-calculator-mcp https://epochcalc.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The current time: Unix epoch in seconds and milliseconds, ISO 8601, and the local wall-clock time in a given IANA time zone with its current UTC offset and DST status. Use this before any relative date reasoning.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| timezone | string | no | IANA time zone, e.g. "America/New_York". Defaults to UTC. |
Convert a Unix timestamp (seconds or milliseconds; auto-detected unless unit is given) to a human-readable date in a time zone, with ISO 8601, RFC 2822, UTC offset, DST flag, weekday, and a relative phrase like "3 days ago".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| timestamp | number | yes | Unix timestamp. Values >= 1e11 are treated as milliseconds unless unit is set. |
| unit | string | no | Interpretation of timestamp. Default auto. |
| timezone | string | no | IANA time zone, e.g. "America/New_York". Defaults to UTC. |
Parse a date/time string (ISO 8601, RFC 2822, HTTP date, SQL "YYYY-MM-DD HH:mm:ss", or a Unix timestamp) into a Unix timestamp and a normalized description. Strings without an offset are interpreted in the given time zone.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| input | string | yes | The date/time text to parse. |
| timezone | string | no | Zone to assume when the input carries no offset, and to report the result in. Defaults to UTC. |
Convert a wall-clock date/time from one IANA time zone to another, correctly across daylight-saving transitions. Returns both sides with offsets, the hour difference at that instant, and whether either zone is on DST.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| datetime | string | yes | ISO 8601 date/time, e.g. "2026-09-06T09:30". If it has no offset it is read as wall time in from_timezone. |
| from_timezone | string | yes | Source IANA zone, e.g. "Asia/Tokyo". |
| to_timezone | string | yes | Target IANA zone, e.g. "Europe/London". |
The exact duration between two dates or date-times: calendar years/months/days, plus total days, hours, minutes and seconds, and the number of weekdays (Mon-Fri). Handles leap years and DST via the IANA database.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | yes | Start date/time (ISO 8601 or Unix timestamp). |
| end | string | yes | End date/time (ISO 8601 or Unix timestamp). |
| timezone | string | no | IANA time zone, e.g. "America/New_York". Defaults to UTC. |
| include_end | boolean | no | Count the end date as a full day (adds one day). Default false. |
Add to or subtract from a Unix timestamp in calendar-aware units (years, months, weeks, days, hours, minutes, seconds) in a time zone, e.g. "now + 30 days" or "1748736543 - 3 months". Returns the resulting timestamp in every format.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| timestamp | number | no | Base Unix timestamp (seconds or milliseconds, auto-detected). Omit for now. |
| add | object | no | Units to add. |
| subtract | object | no | Units to subtract. |
| timezone | string | no | Zone in which calendar units (months, days across DST) are applied. Defaults to UTC. |
Explain a 5- or 6-field cron expression in plain English and list its next run times in a time zone (as ISO 8601 and Unix timestamps). Use to answer "when does this cron job run next?" or to validate an expression.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| expression | string | yes | Cron expression, e.g. "0 9 * * 1-5". |
| timezone | string | no | Zone the schedule is evaluated in. Defaults to UTC. |
| count | integer | no | How many upcoming runs to return. Default 5. |
| from | string | no | Start evaluating after this date/time (ISO 8601). Defaults to now. |
Countdown to a holiday or to a date: days, hours and minutes remaining, and the next occurrence date. Pass an event slug (e.g. "christmas", "thanksgiving", "easter", "super-bowl") or a date (YYYY-MM-DD). Call with no arguments to list the known events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event | string | no | Event slug from the known list, e.g. "christmas". |
| date | string | no | A target date (YYYY-MM-DD) or date-time (ISO 8601) instead of an event. |
| timezone | string | no | Zone whose midnight starts the target day. Defaults to UTC. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Epoch Calculator or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Epoch Calculator can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.