# tick-mcp MCP server

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

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-cocabadger-tick-mcp
- Repository: https://github.com/Cocabadger/tick-mcp

## Install
- Endpoint: https://tick-mcp-production.up.railway.app/mcp
- Auth: Not captured

## Setup notes
- Remote endpoint: https://tick-mcp-production.up.railway.app/mcp

## Tools
- 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. Endpoint: https://tick-mcp-production.up.railway.app/mcp
- 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. Endpoint: https://tick-mcp-production.up.railway.app/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.Cocabadger
- Version: 1.1.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jul 13, 2026
- Source: https://registry.modelcontextprotocol.io