go-passage-of-time-mcp-server

Provides an MCP server (Go) that lets an LLM do basic “passage of time”/time-related operations, inspired by a similar Python MCP server. Can run as an stdio MCP server by default, or as an HTTP streamable server when given a port.

Evaluated Apr 04, 2026 (17d ago)
Repo ↗ Ai Ml mcp time temporal-utilities go stdio http agent-tools
⚙ Agent Friendliness
36
/ 100
Can an agent use this?
🔒 Security
25
/ 100
Is it safe for agents?
⚡ Reliability
21
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
35
Error Messages
0
Auth Simplicity
100
Rate Limits
0

🔒 Security

TLS Enforcement
30
Auth Strength
20
Scope Granularity
0
Dep. Hygiene
40
Secret Handling
40

Security posture is hard to assess from the provided materials. No auth described; HTTP mode could be sensitive without TLS/auth guidance. README does not mention logging/secret handling, scopes, or transport security.

⚡ Reliability

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

Best When

You want a simple, local/agent-integrated MCP time utility that runs in stdio mode or a basic HTTP mode for tooling.

Avoid When

You need well-documented APIs, robust operational guarantees (SLA, retry semantics), or strong authentication/authorization controls.

Use Cases

  • LLM tools that need current time, time arithmetic, or reasoning about elapsed/passage-of-time concepts
  • Building lightweight temporal utilities in an MCP-enabled agent workflow
  • Integrating time-related actions into agents without implementing time logic in every client

Not For

  • High-security, authenticated multi-tenant deployments (auth behavior is not described)
  • Production systems requiring strict rate limiting guarantees or published SLAs
  • Use cases requiring complex scheduling, time zones, or persistent storage semantics beyond “basic time operations”

Interface

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

Authentication

OAuth: No Scopes: No

README does not describe any authentication/authorization mechanism for either stdio MCP or HTTP mode.

Pricing

Free tier: No
Requires CC: No

No pricing information in provided README/repo metadata.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Time-related tools often need clarity about time zones/clock source; this README does not document such behavior.
  • If running over HTTP, agent integrations may need to know the expected streaming/protocol details; README only mentions `-port` at a high level.
  • No documented error codes, retry guidance, or idempotency guarantees were found in the provided materials.

Alternatives

Full Evaluation Report

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

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