Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "tick-mcp": {
      "type": "http",
      "url": "https://tick-mcp-production.up.railway.app/mcp"
    }
  }
}

claude mcp add --transport http tick-mcp https://tick-mcp-production.up.railway.app/mcp

[mcp_servers.tick-mcp]
url = "https://tick-mcp-production.up.railway.app/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tick-mcp": {
      "type": "remote",
      "url": "https://tick-mcp-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "tick-mcp": {
      "type": "http",
      "url": "https://tick-mcp-production.up.railway.app/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=tick-mcp&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vdGljay1tY3AtcHJvZHVjdGlvbi51cC5yYWlsd2F5LmFwcC9tY3AifQ%3D%3D"
}

{
  "servers": {
    "tick-mcp": {
      "type": "http",
      "url": "https://tick-mcp-production.up.railway.app/mcp"
    }
  }
}

{
  "mcpServers": {
    "tick-mcp": {
      "httpUrl": "https://tick-mcp-production.up.railway.app/mcp"
    }
  }
}

extensions:
  "tick-mcp":
    enabled: true
    name: "tick-mcp"
    type: streamable_http
    uri: "https://tick-mcp-production.up.railway.app/mcp"
    timeout: 300

Quality 79 / 100good

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-03-26; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene71 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
fail
tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: now (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); since (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
pass
tools.token_costabout 248 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

2 tools, about 248 tokens to load them all · tool set c8bb8632f365 · checked 2026-10-20 12:13 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 57 / 100

unreachable

provenance80

liveness0

freshness65

hygiene100

+repository +namespace-matches-repo -unreachable(7 failures) ~updated-99d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://tick-mcp-production.up.railway.app/mcp` streamable-http	none	no (7 failures)	90%	311 ms	2025-03-26	2026-10-06

Tools (2)

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.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "io.github.Cocabadger/tick-mcp",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://tick-mcp-production.up.railway.app/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.1.0",
  "repository": {
    "url": "https://github.com/Cocabadger/tick-mcp",
    "source": "github"
  },
  "description": "A time server that keeps your AI honest about time. Real clock + drift guard, zero dependencies."
}