# Epoch Calculator (remote · epochcalc.com)

Unix timestamps, DST-aware time zone conversion, durations, cron schedules, and holiday countdowns

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `epochcalc.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-epochcalc-epochcalc/epochcalc.md), [page](https://verifymcp.io/servers/com-epochcalc-epochcalc/epochcalc)

## Channel facts

- Endpoint: `https://epochcalc.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1052 tokens (~131/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Epoch Calculator MCP server?

Epoch Calculator is a hosted endpoint at https://epochcalc.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-epochcalc-epochcalc 'https://epochcalc.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-epochcalc-epochcalc": {
      "url": "https://epochcalc.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-epochcalc-epochcalc": {
      "type": "http",
      "url": "https://epochcalc.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-epochcalc-epochcalc]
url = "https://epochcalc.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-epochcalc-epochcalc": {
      "type": "remote",
      "url": "https://epochcalc.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-epochcalc-epochcalc --url 'https://epochcalc.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-epochcalc-epochcalc:
    url: "https://epochcalc.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-epochcalc-epochcalc": {
      "Transport": "http",
      "Url": "https://epochcalc.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-epochcalc-epochcalc -t streamable-http -u 'https://epochcalc.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-epochcalc-epochcalc": {
      "type": "http",
      "url": "https://epochcalc.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-23 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (8)

### `time_now` (~78 tokens)

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.

Input parameters:

- `timezone` (string): IANA time zone, e.g. "America/New_York". Defaults to UTC.

Output parameters:

- `abbreviation` (string): Zone abbreviation at that instant, e.g. "BST".
- `epoch_millis` (integer): Unix time in milliseconds.
- `epoch_seconds` (integer): Unix time in seconds.
- `human` (string): Readable sentence with weekday, date, time and zone.
- `is_dst` (boolean): Whether daylight-saving time is in effect.
- `iso` (string): ISO 8601 with the zone offset.
- `offset` (string): UTC offset, e.g. "+09:00".
- `offset_minutes` (integer): UTC offset in minutes.
- `rfc2822` (string): RFC 2822 date string.
- `timezone` (string): IANA zone name.
- `utc_iso` (string): ISO 8601 in UTC (Z).
- `weekday` (string): Full weekday name in English.

### `convert_timestamp` (~125 tokens)

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".

Input parameters:

- `timestamp` (number, required): Unix timestamp. Values >= 1e11 are treated as milliseconds unless unit is set.
- `timezone` (string): IANA time zone, e.g. "America/New_York". Defaults to UTC.
- `unit` (string): Interpretation of timestamp. Default auto.

Output parameters:

- `abbreviation` (string): Zone abbreviation at that instant, e.g. "BST".
- `epoch_millis` (integer): Unix time in milliseconds.
- `epoch_seconds` (integer): Unix time in seconds.
- `human` (string): Readable sentence with weekday, date, time and zone.
- `is_dst` (boolean): Whether daylight-saving time is in effect.
- `iso` (string): ISO 8601 with the zone offset.
- `offset` (string): UTC offset, e.g. "+09:00".
- `offset_minutes` (integer): UTC offset in minutes.
- `relative` (string): Relative phrase such as "3 days ago".
- `rfc2822` (string): RFC 2822 date string.
- `timezone` (string): IANA zone name.
- `utc_iso` (string): ISO 8601 in UTC (Z).
- `weekday` (string): Full weekday name in English.

### `parse_datetime` (~102 tokens)

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.

Input parameters:

- `input` (string, required): The date/time text to parse.
- `timezone` (string): Zone to assume when the input carries no offset, and to report the result in. Defaults to UTC.

Output parameters:

- `abbreviation` (string): Zone abbreviation at that instant, e.g. "BST".
- `epoch_millis` (integer): Unix time in milliseconds.
- `epoch_seconds` (integer): Unix time in seconds.
- `human` (string): Readable sentence with weekday, date, time and zone.
- `input` (string): The text that was parsed.
- `is_dst` (boolean): Whether daylight-saving time is in effect.
- `iso` (string): ISO 8601 with the zone offset.
- `offset` (string): UTC offset, e.g. "+09:00".
- `offset_minutes` (integer): UTC offset in minutes.
- `rfc2822` (string): RFC 2822 date string.
- `timezone` (string): IANA zone name.
- `utc_iso` (string): ISO 8601 in UTC (Z).
- `weekday` (string): Full weekday name in English.

### `convert_timezone` (~134 tokens)

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.

Input parameters:

- `datetime` (string, required): 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, required): Source IANA zone, e.g. "Asia/Tokyo".
- `to_timezone` (string, required): Target IANA zone, e.g. "Europe/London".

Output parameters:

- `difference_hours` (number): target offset minus source offset, in hours.
- `same_instant_utc` (string): The shared instant as ISO 8601 UTC.
- `source` (object): One instant described in one IANA time zone.
- `target` (object): One instant described in one IANA time zone.

### `date_duration` (~139 tokens)

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.

Input parameters:

- `end` (string, required): End date/time (ISO 8601 or Unix timestamp).
- `include_end` (boolean): Count the end date as a full day (adds one day). Default false.
- `start` (string, required): Start date/time (ISO 8601 or Unix timestamp).
- `timezone` (string): IANA time zone, e.g. "America/New_York". Defaults to UTC.

Output parameters:

- `days` (integer)
- `direction` (string)
- `end` (object): One instant described in one IANA time zone.
- `hours` (integer)
- `human` (string): Calendar duration in words, e.g. "1 year, 2 months, 3 days".
- `minutes` (integer)
- `months` (integer)
- `seconds` (integer)
- `start` (object): One instant described in one IANA time zone.
- `total_days` (integer)
- `total_hours` (integer)
- `total_minutes` (integer)
- `total_seconds` (integer)
- `weekdays` (integer): Monday to Friday days in the span.
- `weekend_days` (integer)
- `years` (integer)

### `epoch_math` (~137 tokens)

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.

Input parameters:

- `add` (object): Units to add.
- `subtract` (object): Units to subtract.
- `timestamp` (number): Base Unix timestamp (seconds or milliseconds, auto-detected). Omit for now.
- `timezone` (string): Zone in which calendar units (months, days across DST) are applied. Defaults to UTC.

Output parameters:

- `base` (object): One instant described in one IANA time zone.
- `delta_seconds` (integer): result minus base, in seconds.
- `result` (object): One instant described in one IANA time zone.

### `cron_next_runs` (~140 tokens)

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.

Input parameters:

- `count` (integer): How many upcoming runs to return. Default 5.
- `expression` (string, required): Cron expression, e.g. "0 9 * * 1-5".
- `from` (string): Start evaluating after this date/time (ISO 8601). Defaults to now.
- `timezone` (string): Zone the schedule is evaluated in. Defaults to UTC.

Output parameters:

- `description` (string): Plain-English reading of the expression.
- `expression` (string)
- `next_runs` (array)
- `timezone` (string)

### `days_until` (~139 tokens)

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.

Input parameters:

- `date` (string): A target date (YYYY-MM-DD) or date-time (ISO 8601) instead of an event.
- `event` (string): Event slug from the known list, e.g. "christmas".
- `timezone` (string): Zone whose midnight starts the target day. Defaults to UTC.

Output parameters:

- `days` (integer)
- `events` (array): Known events (only when called with no arguments).
- `hours` (integer)
- `human` (string): e.g. "in 12 days, 5 hours".
- `is_past` (boolean)
- `minutes` (integer)
- `name` (string)
- `target` (object): One instant described in one IANA time zone.
- `total_seconds` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-epochcalc-epochcalc/epochcalc#diagnostics

## Score history

- 2026-09-24: 78
- 2026-09-23: 78
- 2026-09-22: 77
- 2026-09-21: 77
- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 74
- 2026-09-15: 74
- 2026-09-14: 74
- 2026-09-13: 73
- 2026-09-12: 73
- 2026-09-11: 72
- 2026-09-10: 72
- 2026-09-09: 71
- 2026-09-08: 71
- 2026-09-07: 70
- 2026-09-06: 70

## Common questions

### What is the Epoch Calculator MCP server?

Epoch Calculator is an MCP server listed in the public MCP registry as com.epochcalc/epochcalc. Unix timestamps, DST-aware time zone conversion, durations, cron schedules, and holiday countdowns. This page covers its hosted endpoint (https://epochcalc.com/mcp).

### Is the Epoch Calculator MCP server safe to use?

Epoch Calculator scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Epoch Calculator MCP server expose?

Epoch Calculator exposes 8 tools: time_now, convert_timestamp, parse_datetime, convert_timezone, date_duration, and 3 more. Their descriptions and schemas cost roughly 994 tokens of context every time the server is loaded.

### Does the Epoch Calculator MCP server require authentication?

No. We connected to Epoch Calculator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Epoch Calculator MCP server still maintained?

Epoch Calculator is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://epochcalc.com/mcp
- Website: https://epochcalc.com/api
- Changelog RSS feed: https://verifymcp.io/servers/com-epochcalc-epochcalc/epochcalc.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-epochcalc-epochcalc/epochcalc.json
- HTML version of this page: https://verifymcp.io/servers/com-epochcalc-epochcalc/epochcalc