mcp-fast-time-server-go

Minimal Go service that returns/streams the current UTC time via multiple transports: stdio, HTTP JSON-RPC, and an HTTP SSE endpoint (optionally bearer-token protected for SSE).

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ DevTools go mcp? time stdio json-rpc sse http minimal-service
⚙ Agent Friendliness
36
/ 100
Can an agent use this?
🔒 Security
37
/ 100
Is it safe for agents?
⚡ Reliability
19
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
55
Error Messages
0
Auth Simplicity
75
Rate Limits
0

🔒 Security

TLS Enforcement
30
Auth Strength
40
Scope Granularity
10
Dep. Hygiene
60
Secret Handling
50

TLS enforcement is not described (unknown whether HTTP is plain or HTTPS-enabled). SSE supports a bearer token via -auth-token, but there is no evidence of fine-grained scopes or authentication coverage across transports. No information is provided about logging/secret handling, dependency vulnerabilities, or secure headers; only basic token gating for SSE is documented.

⚡ Reliability

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

Best When

You need a tiny, local, transport-flexible service for experimentation, testing, or demonstrations of HTTP JSON-RPC/SSE/stdio flows.

Avoid When

You need strong auth for all endpoints, clear rate-limit policies, or production operational guarantees; documentation does not cover these details.

Use Cases

  • Developer tooling and demos needing a simple time source
  • Load testing or benchmarking of transport paths (HTTP/JSON-RPC, SSE, stdio)
  • Integration testing for systems expecting a time endpoint
  • Building blocks for demos of agent↔service communication over stdio or HTTP

Not For

  • Production-grade time services that need robust security, auditing, or strict reliability guarantees
  • Environments requiring documented OpenAPI contracts, client SDKs, or strong operational/SLA commitments
  • Use cases needing paginated/complex APIs, retries/idempotency semantics, or rich error taxonomy

Interface

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

Authentication

Methods: Bearer token for SSE via -auth-token (optional)
OAuth: No Scopes: No

Authentication is only described for SSE (Authorization: Bearer <token>). No auth details are provided for the HTTP JSON-RPC or stdio transports in the README.

Pricing

Free tier: No
Requires CC: No

Self-hosted open-source project (Apache-2.0); no usage pricing described.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • No MCP server is indicated; agents must use stdio/HTTP/SSE transports instead.
  • SSE is described with optional bearer auth only; HTTP JSON-RPC auth behavior is not documented.
  • Rate limiting and error-code contracts are not documented in the README.

Alternatives

Full Evaluation Report

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

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