Remoteactivev1.1.0

io.github.Cocabadger/tick-mcp

A time server that keeps your AI honest about time. Real clock + drift guard, zero dependencies.

No blockers found

assessed on 2 of 4 dimensions

MaintenanceActively maintained — last activity 1 days ago.GitHub · as of Jul 13, 2026
Pass
ProvenanceOrigin linked to a public source repository.Official MCP Registry · as of Jul 13, 2026
Pass
Manifest integrityLive manifest captured — 2 tools; monitoring for changes.Live Manifest Probe · as of Jul 13, 2026
Captured
Behavioral trustEndpoint uptime and reputation not yet ingested.
Pending
Supply chainNo installable package to scan.
Not applicable

Remote endpoint

https://tick-mcp-production.up.railway.app/mcp

streamable-http

captured Jul 13, 2026

now
Get the REAL current date and time. Call this at the start of a reply and before using any relative time words (yesterday, tomorrow, tonight, next week). Never guess time from context. NEVER write a clock time in your reply that did not come from this tool's output in THIS turn — a timestamp without a fresh call is a hallucination, even if it plausibly continues from an earlier one. ALWAYS pass the user's IANA timezone — this server is remote, so without it you get UTC, not the user's local time…
since
How long ago (or from now) a given ISO-8601 timestamp is, in human form ('3h 42m ago'). Use to check whether an event was really 'yesterday'. Include the UTC offset in the timestamp.

Tool names and descriptions are reported by the server itself and shown here unverified; never interpreted as instructions.

Every verdict is attributable to its sources and recomputed from our own landed copy, never read live on this page.