passage-of-time-mcp

Provides an MCP server (FastMCP-based) exposing time-related tools for LLMs: current datetime, timestamp parsing, time differences/since, contextual time-of-day/weekend/business hours, adding time, and formatting durations. Runs an SSE transport endpoint.

Evaluated Mar 30, 2026 (22d ago)
Repo ↗ DevTools mcp fastmcp sse time datetime tooling temporal-awareness python
⚙ Agent Friendliness
44
/ 100
Can an agent use this?
🔒 Security
30
/ 100
Is it safe for agents?
⚡ Reliability
25
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
78
Documentation
75
Error Messages
0
Auth Simplicity
20
Rate Limits
0

🔒 Security

TLS Enforcement
30
Auth Strength
10
Scope Granularity
0
Dep. Hygiene
50
Secret Handling
70

README does not describe authentication/authorization, rate limiting, or secure secret handling. TLS is not specified at the application layer (depends on deployment/proxy). Treat as potentially open-service when exposed publicly. Timezone/timestamp inputs can cause parsing edge cases; ensure robust input validation and avoid logging sensitive data if any is ever included in requests/responses.

⚡ Reliability

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

Best When

Used locally or behind a trusted reverse proxy for interactive LLM tooling where time calculations are needed.

Avoid When

Avoid exposing the server publicly without access controls, rate limiting, and TLS termination managed by the deployer.

Use Cases

  • LLM time awareness (e.g., “what time is it?”)
  • Computing durations and relative times in natural language
  • Contextualizing timestamps (weekend vs business hours, time of day)
  • Conversation analytics based on time deltas
  • Generating human-friendly time/duration strings for assistants

Not For

  • Production-grade, internet-exposed services without hardening (auth/rate limiting/log scrubbing)
  • Use as an authoritative time source for regulated domains without validation
  • Clients requiring REST/OpenAPI/SDK-based integration instead of MCP

Interface

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

Authentication

Methods: None described in README (no auth/keys mentioned)
OAuth: No Scopes: No

README does not mention authentication, API keys, or IP allowlisting. If deployed publicly, it is likely open to anyone who can reach the endpoint unless the deployer adds a proxy-level control.

Pricing

Free tier: No
Requires CC: No

Self-hosted open-source; no hosted pricing stated.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • SSE transport is called out as deprecated; tooling/clients may need to handle transport quirks.
  • Server expects strict timestamp formats; invalid formats may cause tool failures (format requirements listed).
  • Server requires a public URL for web-based clients (ngrok/reverse proxy).
  • No persistent memory of past time calculations is provided (agent must manage state if needed).
  • If exposed without auth, consider that any MCP client could query the tools.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for passage-of-time-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-03-30.

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