pape-mcp-server-time

An MCP server that provides the current time (or time-related data) to agents via the Model Context Protocol, likely for prompts that need timestamps or for testing time-dependent workflows.

Evaluated Apr 04, 2026 (27d ago)
Homepage ↗ DevTools mcp time tooling devtools automation
⚙ Agent Friendliness
45
/ 100
Can an agent use this?
🔒 Security
46
/ 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
60
Auth Strength
30
Scope Granularity
20
Dep. Hygiene
45
Secret Handling
80

A time-only tool typically has low intrinsic risk. However, this evaluation lacks concrete repo/manifest evidence for TLS enforcement, auth mechanisms, dependency security, and error/telemetry handling.

⚡ Reliability

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

Best When

You need a lightweight, agent-callable “current time” tool for reasoning, testing, or timestamping.

Avoid When

You require high-assurance/authoritative time sources (e.g., for financial reconciliation) or strict audit-grade time synchronization without external verification.

Use Cases

  • Injecting the current date/time into agent reasoning or outputs
  • Time-stamping generated content for logs, audits, or reports
  • Testing agents/workflows that depend on “now”
  • Scheduling/decision logic that requires the current timestamp

Not For

  • Performing business-critical timekeeping without validation against authoritative time sources
  • Handling sensitive data processing or secure operations

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 package information; MCP tools are commonly unauthenticated or configured at deployment, but this cannot be confirmed here.

Pricing

Free tier: No
Requires CC: No

Pricing not provided; as an MCP server package, it is likely self-hosted.

Agent Metadata

Pagination
none
Idempotent
True
Retry Guidance
Not documented

Known Gotchas

  • Time outputs will differ across retries/calls; agents should not assume identical timestamps.
  • Timezone/format ambiguity (UTC vs local time, ISO8601 vs custom) can cause downstream parsing issues if not clearly documented.

Alternatives

Full Evaluation Report

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

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