{"id":"pape-mcp-server-time","name":"pape-mcp-server-time","homepage":"https://pypi.org/project/pape-mcp-server-time/","repo_url":null,"category":"devtools","subcategories":[],"tags":["mcp","time","tooling","devtools","automation"],"what_it_does":"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.","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"],"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.","alternatives":["Use an agent runtime’s system clock directly","Call a public time API (e.g., NTP-backed services) and validate responses","Implement a small custom MCP tool that returns server time with clear contract/tests"],"af_score":45.0,"security_score":46.2,"reliability_score":25.0,"package_type":"mcp_server","discovery_source":["pypi"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:49:17.015647+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"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":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Pricing not provided; as an MCP server package, it is likely self-hosted."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":45.0,"security_score":46.2,"reliability_score":25.0,"mcp_server_quality":55.0,"documentation_accuracy":40.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":80.0,"rate_limit_clarity":0.0,"tls_enforcement":60.0,"auth_strength":30.0,"scope_granularity":20.0,"dependency_hygiene":45.0,"secret_handling":80.0,"security_notes":"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.","uptime_documented":0.0,"version_stability":40.0,"breaking_changes_history":30.0,"error_recovery":30.0,"idempotency_support":"true","idempotency_notes":"A “get current time” call is naturally idempotent in the sense that repeated calls return different timestamps but the operation itself is side-effect-free; true idempotency for identical outputs is not applicable.","pagination_style":"none","retry_guidance_documented":false,"known_agent_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."]}}