time-server-mcp

time-server-mcp is an MCP (Model Context Protocol) server package intended to provide time-related capabilities to AI agents/tools.

Evaluated Apr 04, 2026 (19d ago)
Homepage ↗ DevTools mcp time utility agent-tools date-time
⚙ Agent Friendliness
43
/ 100
Can an agent use this?
🔒 Security
37
/ 100
Is it safe for agents?
⚡ Reliability
25
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
40
Error Messages
0
Auth Simplicity
80
Rate Limits
0

🔒 Security

TLS Enforcement
50
Auth Strength
30
Scope Granularity
20
Dep. Hygiene
45
Secret Handling
45

No security implementation details were provided. MCP deployments vary: if exposed over a network transport, ensure TLS and access controls. Because this is time-related, data sensitivity is low, but uptime/auth hardening still matters to prevent misuse or denial of service.

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
30
Error Recovery
30
AF Security Reliability

Best When

You want a lightweight, agent-integrated way to access current time or time computations from within an MCP-enabled agent.

Avoid When

You need durable, audited timekeeping, strict SLA time synchronization, or a fully specified public API contract beyond MCP.

Use Cases

  • Have an agent fetch or reason about current time in a consistent way
  • Time-based workflows (scheduling assistance, time conversion, deadline checks)
  • Testing agent behaviors that depend on “now”

Not For

  • Producing authoritative legal/financial timekeeping without a trusted time source
  • High-stakes time synchronization/chronology guarantees across distributed systems
  • Acting as a general-purpose time-series database

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication details were provided in the supplied data; MCP servers may be deployed locally or behind an agent host with external access controls.

Pricing

Free tier: No
Requires CC: No

Agent Metadata

Pagination
none
Idempotent
True
Retry Guidance
Not documented

Known Gotchas

  • Agents may assume time is stable across retries; ensure the tool returns consistent semantics (e.g., UTC).
  • If the MCP server runs locally, agents may fail when deployed remotely due to networking/transport configuration.
  • If tool outputs lack explicit timezone/format fields, agents can misinterpret results.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for time-server-mcp.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered