_ registry / mcp streamable-http · checked 50m ago

epochcalc

https://epochcalc.com

Registry code: 2a5aa96c93003790

api record

Epoch Calculator tools for time and date math: current time, Unix timestamp conversion, date parsing, time zone conversion with DST, durations, epoch arithmetic, cron schedules, and holiday countdowns. All time zones are IANA names. Prefer these tools over estimating dates or offsets.

endpoint
https://epochcalc.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is epochcalc live?
Yes — it answered the hub's last check (checked 50m ago). It answered 100% of checks over the last 30 days.
Is epochcalc free to use?
Yes — the hub reached it with no key and no payment.
What tools does epochcalc have?
8 tools: convert_timestamp, convert_timezone, date_duration, parse_datetime, cron_next_runs, epoch_math, days_until, time_now.
Is epochcalc safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.7%· all time 99.7%

latency
684ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 310 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
developer tools
used for
  • convert a unix timestamp to a date
  • convert time between time zones
  • list next runs of a cron expression
  • compute duration between dates
  • get the current time
takes → gives
text → data
tools
8 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
3 open 5 never probed 3 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • epoch_math reads open 21h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "add": {
      "type": "object",
      "properties": {
        "days": {
          "type": "number"
        },
        "hours": {
          "type": "number"
        },
        "weeks": {
          "type": "number"
        },
        "years": {
          "type": "number"
        },
        "months": {
          "type": "number"
        },
        "minutes": {
          "type": "number"
        },
        "seconds": {
          "type": "number"
        }
      },
      "description": "Units to add.",
      "additionalProperties": false
    },
    "subtract": {
      "type": "object",
      "properties": {
        "days": {
          "type": "number"
        },
        "hours": {
          "type": "number"
        },
        "weeks": {
          "type": "number"
        },
        "years": {
          "type": "number"
        },
        "months": {
          "type": "number"
        },
        "minutes": {
          "type": "number"
        },
        "seconds": {
          "type": "number"
        }
      },
      "description": "Units to subtract.",
      "additionalProperties": false
    },
    "timezone": {
      "type": "string",
      "description": "Zone in which calendar units (months, days across DST) are applied. Defaults to UTC."
    },
    "timestamp": {
      "type": "number",
      "description": "Base Unix timestamp (seconds or milliseconds, auto-detected). Omit for now."
    }
  },
  "additionalProperties": false
}
    arguments 70 lines
  • days_until reads open 21h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "description": "A target date (YYYY-MM-DD) or date-time (ISO 8601) instead of an event."
    },
    "event": {
      "type": "string",
      "description": "Event slug from the known list, e.g. \"christmas\"."
    },
    "timezone": {
      "type": "string",
      "description": "Zone whose midnight starts the target day. Defaults to UTC."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • time_now reads open 21h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "timezone": {
      "type": "string",
      "description": "IANA time zone, e.g. \"America/New_York\". Defaults to UTC."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • convert_timestamp reads unknown 17h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "timestamp"
  ],
  "properties": {
    "unit": {
      "enum": [
        "auto",
        "seconds",
        "milliseconds"
      ],
      "type": "string",
      "description": "Interpretation of timestamp. Default auto."
    },
    "timezone": {
      "type": "string",
      "description": "IANA time zone, e.g. \"America/New_York\". Defaults to UTC."
    },
    "timestamp": {
      "type": "number",
      "description": "Unix timestamp. Values >= 1e11 are treated as milliseconds unless unit is set."
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • convert_timezone reads unknown 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "datetime",
    "from_timezone",
    "to_timezone"
  ],
  "properties": {
    "datetime": {
      "type": "string",
      "description": "ISO 8601 date/time, e.g. \"2026-09-06T09:30\". If it has no offset it is read as wall time in from_timezone."
    },
    "to_timezone": {
      "type": "string",
      "description": "Target IANA zone, e.g. \"Europe/London\"."
    },
    "from_timezone": {
      "type": "string",
      "description": "Source IANA zone, e.g. \"Asia/Tokyo\"."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • date_duration reads unknown 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "start",
    "end"
  ],
  "properties": {
    "end": {
      "type": "string",
      "description": "End date/time (ISO 8601 or Unix timestamp)."
    },
    "start": {
      "type": "string",
      "description": "Start date/time (ISO 8601 or Unix timestamp)."
    },
    "timezone": {
      "type": "string",
      "description": "IANA time zone, e.g. \"America/New_York\". Defaults to UTC."
    },
    "include_end": {
      "type": "boolean",
      "description": "Count the end date as a full day (adds one day). Default false."
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • parse_datetime reads unknown 9h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "input"
  ],
  "properties": {
    "input": {
      "type": "string",
      "description": "The date/time text to parse."
    },
    "timezone": {
      "type": "string",
      "description": "Zone to assume when the input carries no offset, and to report the result in. Defaults to UTC."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • cron_next_runs reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "expression"
  ],
  "properties": {
    "from": {
      "type": "string",
      "description": "Start evaluating after this date/time (ISO 8601). Defaults to now."
    },
    "count": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "How many upcoming runs to return. Default 5."
    },
    "timezone": {
      "type": "string",
      "description": "Zone the schedule is evaluated in. Defaults to UTC."
    },
    "expression": {
      "type": "string",
      "description": "Cron expression, e.g. \"0 9 * * 1-5\"."
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 2a5aa96c93003790.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2a5aa96c93003790/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2a5aa96c93003790/badge.svg)](https://brick.blue/agent/2a5aa96c93003790?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.