Chrono Mcp

io.github.nexus-api-labPublished by GitHub account nexus-api-labv0.1.1Updated Oct 25, 2026

Deterministic time tools for AI agents: timezone conversion, business-day math, cron interpretation.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP server giving assistants deterministic time tools: timezone conversion, business-day math and cron interpretation.

What you can do
Convert times between timezones so an assistant can state correct local times and offsets. Do business-day arithmetic, such as counting or shifting working days. Interpret cron expressions so schedules can be explained or checked. The manifest lists no individual tools, so exact inputs and outputs are not documented here.
When to use it
Useful when an assistant must reason about timezones, working-day deadlines or cron schedules and you want deterministic results rather than model guesswork. It is a small, single-purpose addition rather than a general utility server.
Requirements
A remote streamable HTTP endpoint; the assistant connects to the hosted address. No packages, environment variables, headers or authentication are declared, so no account or key appears to be needed. Network access to the endpoint is required.
Before you install
The service is hosted by a third party, so any times, dates, schedules or cron expressions you send are processed outside your machine. No authentication is declared, so do not send sensitive scheduling details. Tool behavior and availability are not documented beyond the short description.

Installation

In SourceWeft

  1. Open Chrono Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.nexus-api-lab%2Fchrono-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "chrono": {
      "type": "http",
      "url": "https://chrono-mcp.dokasukadon.workers.dev/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.