MCP.Market

Time MCP server

online · 100% uptime
by mcpcentral-io·io.github.mcpcentral-io/mcp-time·v0.0.3·2 stars

Time MCP server via HTTP

B84/100grade B
What users say
No reviews yet
Be the first
Safety scan
B84/100

full report

Adoption
New

2 stars

Reviews

Write one

Nobody has reviewed Time yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Time tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned25/25
  • Live reliabilityremote reachable in 288ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityauth enforced (unknown)9/15
  • Maintenancelast push 166 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 84/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Time compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
84/100
higher than 68% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
309 ms
faster than 47% of 30,031 servers
GitHub stars
2
more than 75% of 28,688 servers

Install Time in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp-time https://mcp.time.mcpcentral.io
Add to Cursor

What the publisher says

From the Time repository's README, as published. We do not edit it. Read it on GitHub

MCP Time Server

A Model Context Protocol (MCP) server providing time-related tools with dual-mode support:

  • Stdio transport for local MCP clients (via npm)
  • Streamable HTTP transport for remote access (via Cloudflare Workers)

This server allows LLMs to access various date/time functions through multiple connection methods.

MCP Central Server Card: https://guide-gen.mcpcentral.io/servers/io-github-mcpcentral-io-mcp-time

Features

Provides the following MCP tools:

  • current_time: Get the current date and time in specified formats and timezones.
  • relative_time: Get a human-readable relative time string (e.g., "in 5 minutes", "2 hours ago").
  • daysinmonth: Get the number of days in a specific month.
  • get_timestamp: Get the Unix timestamp (milliseconds) for a given time.
  • convert_time: Convert a time between different IANA timezones.
  • getweekyear: Get the week number and ISO week number for a given date.

Project Structure

mcp-time/
├── src/
│   └── index.ts      # Cloudflare Worker entry point & MCP logic
├── package.json      # Project dependencies and scripts
├── tsconfig.json     # TypeScript configuration
└── wrangler.toml     # Cloudflare Worker configuration

Installation

Option 1: Install from npm (Stdio Mode)

Install the package globally or use with npx:

# Global installation
npm install -g @mcpcentral/mcp-time

# Or use directly with npx
npx @mcpcentral/mcp-time

Option 2: Use Remote Server (HTTP Mode)

Connect directly to the deployed Cloudflare Worker:

Example:

https://mcp.time.mcpcentral.io

Usage

Stdio Transport (Local)

Configure your MCP client (e.g., Claude Desktop) to use the stdio transport:

{
  "mcpServers": {
    "time-server": {
      "command": "npx",
      "args": ["@mcpcentral/mcp-time"]
    }
  }
}

Or with global installation:

{
  "mcpServers": {
    "time-server": {
      "command": "/path/to/node/bin/mcp-time"
    }
  }
}

Streamable HTTP Transport (Remote)

Configure your MCP client to use the remote HTTP endpoint:

{
  "mcpServers": {
    "time-server": {
      "url": "https://mcp.time.mcpcentral.io",
      "transport": "streamable-http"
    }
  }
}

Development

  1. Clone the Repository:
git clone https://github.com/mcpcentral-io/mcp-time.git
    cd mcp-time
  1. Install Dependencies:
npm install

Compile the TypeScript code:

  1. Build:
npm run build

(This compiles src/index.ts to dist/index.js)

  1. Test Locally:

Test Stdio Mode:

echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}' | node dist/index.js

Test HTTP Mode (via Wrangler):

npx wrangler dev

This will start the server on http://localhost:8787. You can then test with curl or point your MCP client to this local endpoint.

Deployment

Deploy to Cloudflare Workers (HTTP Mode)

  1. Configure Cloudflare:
cp wrangler.toml.example wrangler.toml

Edit wrangler.toml to configure your domain (optional).

  1. Login and Deploy:
wrangler login
   npx wrangler deploy

Publish to npm (Stdio Mode)

  1. Build the package:
npm run build
  1. Publish:
npm publish --access public

Connectors for Streamable HTTP Servers

NEW: Major providers have adopted the Model Context Protocol and now support Streamable HTTP servers directly. Anthropic, OpenAI, and Microsoft have all adopted this modern transport protocol.

📋 Protocol Note: Streamable HTTP is the modern replacement for the deprecated HTTP+SSE transport.

Anthropic MCP Connector

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Time: common questions

Is Time MCP server safe?
Mostly: it is graded B (84/100). Read the Time safety report
How do I install Time?
It runs remotely at mcp.time.mcpcentral.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Time need an API key?
Yes. The endpoint refuses requests without credentials; the publisher's docs say how to get them.
Is Time maintained?
The last commit was 200 days ago (2026-04-18). The latest release is v0.0.3.
Is Time up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Time compare with other MCP servers?
safety score 84/100 (higher than 68% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 309 ms (faster than 47% of 30,031 servers). Full comparison.