tick-mcp
A time server that keeps your AI honest about time. Real clock + drift guard, zero dependencies.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"tick-mcp": {
"url": "https://tick-mcp-production.up.railway.app/mcp"
}
}
}Remote endpoints
https://tick-mcp-production.up.railway.app/mcpstreamable-httpWhat it can do
Tool inventory
Tools (2)
🟡now(timezone)
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.
Input Schema
{
"type": "object",
"properties": {
"timezone": {
"type": "string",
"description": "The user's IANA timezone, e.g. Europe/Warsaw. Omitting it returns UTC."
}
}
}🟢since(timestamp)
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.
Input Schema
{
"type": "object",
"properties": {
"timestamp": {
"type": "string",
"description": "ISO-8601, e.g. 2026-07-11T09:30:00+02:00"
}
},
"required": [
"timestamp"
]
}Community
Evidence