# Tick MCP by usefulapi (remote · tick.usefulapi.io)

Read Tick clients, projects, tasks, users and time entries; log and edit time entries.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `tick.usefulapi.io`: 65/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-tick/tick.md), [page](https://verifymcp.io/servers/io-usefulapi-tick/tick)

## Channel facts

- Endpoint: `https://tick.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1673 tokens (~119/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Tick MCP by usefulapi server?

Tick MCP by usefulapi is a hosted endpoint at https://tick.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-usefulapi-tick 'https://tick.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-tick": {
      "url": "https://tick.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-tick": {
      "type": "http",
      "url": "https://tick.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-tick]
url = "https://tick.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-tick": {
      "type": "remote",
      "url": "https://tick.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-tick --url 'https://tick.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-tick:
    url: "https://tick.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-tick": {
      "Transport": "http",
      "Url": "https://tick.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-tick -t streamable-http -u 'https://tick.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-tick": {
      "type": "http",
      "url": "https://tick.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 64, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 61)

First indexed and scored.

## MCP tools (14)

### `tick_list_clients` (~105 tokens)

List clients

List Tick clients. By default only clients that have open projects; set include_all=true for every client (also archived or without projects). 100 per page. GET /clients.json or /clients/all.json.

Input parameters:

- `include_all` (boolean): true = all clients, false/omitted = only clients with open projects.
- `page` (integer): Page number, from 1 (default 1; 100 records per page). Pass the previous reply's next_page.

### `tick_get_client` (~44 tokens)

Get client

One client by id, with a summary of its projects (count and URL). GET /clients/{id}.json.

Input parameters:

- `client_id` (integer, required): Tick client id.

### `tick_list_projects` (~101 tokens)

List projects

List Tick projects with budget (hours or money), billable flag, client_id and owner_id. Open projects by default; status=closed for closed ones. 100 per page. GET /projects.json or /projects/closed.json.

Input parameters:

- `page` (integer): Page number, from 1 (default 1; 100 records per page). Pass the previous reply's next_page.
- `status` (string): open (default) or closed.

### `tick_get_project` (~52 tokens)

Get project

One project by id, with total_hours entered, a summary of its tasks (count and URL) and its client. GET /projects/{id}.json.

Input parameters:

- `project_id` (integer, required): Tick project id.

### `tick_list_tasks` (~150 tokens)

List tasks

List Tick tasks (the budget lines that time entries are logged against). Across all projects, or for one project when project_id is given. Open tasks by default; status=closed for closed ones. You need a task id to log time. 100 per page. GET /tasks.json, /tasks/closed.json, /projects/{id}/tasks.json or /projects/{id}/tasks/closed.json.

Input parameters:

- `page` (integer): Page number, from 1 (default 1; 100 records per page). Pass the previous reply's next_page.
- `project_id` (integer): Only the tasks of this project.
- `status` (string): open (default) or closed.

### `tick_get_task` (~52 tokens)

Get task

One task by id, with total_hours entered, a summary of its entries (count and URL) and its project. GET /tasks/{id}.json.

Input parameters:

- `task_id` (integer, required): Tick task id.

### `tick_list_users` (~108 tokens)

List users

List the users of the Tick subscription (id, name, e-mail, timezone). A non-administrator sees only themself. Use deleted=true for removed users who still have time entries (administrators only). GET /users.json or /users/deleted.json.

Input parameters:

- `deleted` (boolean): true = deleted users that have time entries.
- `page` (integer): Page number, from 1 (default 1; 100 records per page). Pass the previous reply's next_page.

### `tick_list_entries` (~252 tokens)

List time entries

List time entries. Tick requires EITHER start_date AND end_date (entries dated in that range) OR updated_at (entries created or changed after that time). Optional filters: project_id, task_id, user_id, billable, billed. Each entry has date, hours, notes, task_id, user_id. 100 per page. GET /entries.json.

Input parameters:

- `billable` (boolean): Only billable (true) or non-billable (false) entries.
- `billed` (boolean): Only billed (true) or not yet billed (false) entries.
- `end_date` (string): Last day of the range (with start_date).
- `page` (integer): Page number, from 1 (default 1; 100 records per page). Pass the previous reply's next_page.
- `project_id` (integer): Only entries of this project.
- `start_date` (string): First day of the range (with end_date).
- `task_id` (integer): Only entries of this task.
- `updated_at` (string): Only entries created or modified after this time (instead of a date range).
- `user_id` (integer): Only entries of this user.

### `tick_get_entry` (~38 tokens)

Get time entry

One time entry by id, with its task. GET /entries/{id}.json.

Input parameters:

- `entry_id` (integer, required): Tick entry id.

### `tick_create_entry` (~156 tokens)

Log time entry

WRITE: log a new time entry on a task (POST /entries.json). Needs the task id (see tick_list_tasks). hours is a decimal (1.5 = 1h30m). user_id is only honored for administrators (otherwise the entry is yours). Creates a new entry every call; nothing is sent to anyone.

Input parameters:

- `date` (string, required): Day the work was done, yyyy-mm-dd.
- `hours` (number, required): Hours worked, decimal (1.5 = one and a half hours).
- `notes` (string): What was done.
- `task_id` (integer, required): Task to log the time on.
- `user_id` (integer): Administrators only: log the time for this user.

### `tick_update_entry` (~130 tokens)

Update time entry

WRITE: change an existing time entry (PUT /entries/{id}.json): hours, notes, date, task, or mark it billed. Only the fields you pass change; the previous values are overwritten.

Input parameters:

- `billed` (boolean): Mark the entry as billed / not billed.
- `date` (string): New date, yyyy-mm-dd.
- `entry_id` (integer, required): Entry to change.
- `hours` (number): New hours (decimal).
- `notes` (string): New notes (replaces the old notes).
- `task_id` (integer): Move the entry to this task.

### `tick_create_client` (~58 tokens)

Create client

WRITE: create a new client (POST /clients.json). Tick administrators only (403 otherwise). Creates a new client every call.

Input parameters:

- `archive` (boolean): Create the client archived (default false).
- `name` (string, required): Client name.

### `tick_create_project` (~146 tokens)

Create project

WRITE: create a new project (POST /projects.json). Tick administrators only. The project has no tasks: create at least one with tick_create_task before time can be logged. Creates a new project every call.

Input parameters:

- `billable` (boolean): Whether the project is billable.
- `budget` (number): Project budget (hours, or money for a money-based subscription).
- `client_id` (integer, required): Client the project belongs to (see tick_list_clients).
- `name` (string, required): Project name.
- `notifications` (boolean): Send budget notifications.
- `owner_id` (integer): User id of the project owner.
- `recurring` (boolean): Recurring budget.

### `tick_create_task` (~82 tokens)

Create task

WRITE: create a new task on a project (POST /tasks.json). Tick administrators only. Creates a new task every call.

Input parameters:

- `billable` (boolean): Whether the task is billable.
- `budget` (number): Task budget (hours).
- `name` (string, required): Task name.
- `project_id` (integer, required): Project the task belongs to.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-tick/tick#diagnostics

## Score history

- 2026-10-17: 65
- 2026-10-16: 65
- 2026-10-15: 64
- 2026-10-14: 64
- 2026-10-13: 62
- 2026-10-12: 61

## Common questions

### What is the Tick MCP by usefulapi server?

Tick MCP by usefulapi is listed in the public MCP registry as io.usefulapi/tick. Read Tick clients, projects, tasks, users and time entries; log and edit time entries. This page covers its hosted endpoint (https://tick.usefulapi.io/mcp).

### Is the Tick MCP by usefulapi server safe to use?

Tick MCP by usefulapi scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Tick MCP by usefulapi server expose?

Tick MCP by usefulapi exposes 14 tools: tick_list_clients, tick_get_client, tick_list_projects, tick_get_project, tick_list_tasks, and 9 more. Their descriptions and schemas cost roughly 1,474 tokens of context every time the server is loaded.

### Does the Tick MCP by usefulapi server require authentication?

Yes. Tick MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Tick MCP by usefulapi server still maintained?

Tick MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://tick.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/tick/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-tick/tick.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-tick/tick.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-tick/tick