Unix Timestamp SkillUnix Timestamp Skill

OnlineCredit Usage:1 per callTool:UnixTimestampSkill

The tool

Unix Timestamp Converter provides bidirectional conversion between epoch timestamps and human-readable dates with detailed date components including ISO 8601 and RFC 2822 formats.

Once your client is connected to the VerveKit MCP server, this appears in its tool list as UnixTimestampSkill. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.

Tool call
{
  "name": "UnixTimestampSkill",
  "arguments": {
    "timestamp": "1609459200"
  }
}

What that looks like in a conversation

You don't name the tool — the model picks it. Asking about 1609459200 in the terms this source covers is enough for it to reach for UnixTimestampSkill on its own.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.

Client config
{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}
Endpoint
https://api.vervekit.com/v1/mcp

Per-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made.

ArgumentTypeExampleDescription
timestampRequiredstring1609459200Unix timestamp to convert
formatstringsecondsTimestamp format One of: seconds, milliseconds, s, ms.

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "timestamp": 1609459200,
    "timestamp_format": "seconds",
    "iso_8601": "2021-01-01T00:00:00Z",
    "rfc_2822": "Fri, 01 Jan 2021 00:00:00 GMT",
    "date": "1/1/2021",
    "time": "12:00:00 AM",
    "unix_seconds": 1609459200,
    "unix_milliseconds": 1609459200000,
    "year": 2021,
    "month": 1,
    "day": 1,
    "hour": 0,
    "minute": 0,
    "second": 0,
    "day_of_week": "Friday",
    "timezone": "UTC"
  }
}

Fields

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.
FieldTypeExampleDescription
timestampnumber1609459200Unix timestamp in requested format
timestamp_formatstringsecondsFormat of the timestamp value returned
iso_8601string2021-01-01T00:00:00ZDate formatted in ISO 8601 standard
rfc_2822stringFri, 01 Jan 2021 00:00:00 GMTDate formatted in RFC 2822 standard
datestring1/1/2021Date in simple M/D/YYYY format
timestring12:00:00 AMTime in HH:MM:SS AM/PM format
unix_secondsnumber1609459200Unix timestamp in seconds
unix_millisecondsPremiumnumber1609459200000Unix timestamp in milliseconds
yearnumber2021Year component extracted from timestamp
monthnumber1Month component from 1 to 12
daynumber1Day of month component
hournumber0Hour component in 24-hour format
minutenumber0Minute component of the time
secondnumber0Second component of the time
day_of_weekPremiumstringFridayFull name of the day of week
timezonestringUTCTimezone of the returned date

Failure modes

Errors come back as tool errors with a sentence the model can act on, not a bare status code.

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This skill isn't part of VerveKit. Check the catalog.
429Brief rate limit. Retrying after a moment succeeds.

Other ways to use Unix Timestamp Skill

Set up Unix Timestamp Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an X-API-Key header, with SDKs for Node, Python and .NET.APIVerveReference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContextReference →

Frequently asked questions

Do I have to tell the agent to use UnixTimestampSkill?

No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.

Does connecting the server expose every tool at once?

Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.

What does a call cost?

1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.

Is there a REST version of this?

Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?