MCP Time Server on Cloudflare (Without Auth)

Created By
iamajeesha year ago
Remote MCP time server on Cloudflare
Overview

What is MCP Time Server?

MCP Time Server is a remote time server deployed on Cloudflare that provides tools for retrieving the current time in various timezones and converting time between different timezones without requiring authentication.

How to use MCP Time Server?

To use the MCP Time Server, you can deploy it to your own Cloudflare Workers account or use the provided live demo URL. You can access the server via a web interface or connect it to local clients like Claude Desktop.

Key features of MCP Time Server?

  • Get the current time for any IANA timezone.
  • Convert time between different timezones easily.
  • Connect to the server from Cloudflare AI Playground and local MCP clients.

Use cases of MCP Time Server?

  1. Quickly retrieving the current time in different regions for scheduling.
  2. Converting meeting times across different timezones for global teams.
  3. Integrating time functionalities into applications that require timezone awareness.

FAQ from MCP Time Server?

  • Is authentication required to use the MCP Time Server?

No, the MCP Time Server does not require authentication for access.

  • How can I deploy my own instance of the MCP Time Server?

You can deploy it using the provided deployment button or via command line instructions.

  • What parameters do I need to provide for time conversion?

You need to specify the source timezone, the time in HH:MM format, and the target timezone.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
iamajeesh
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago