Tick MCP by usefulapi
REMOTE · TICK.USEFULAPI.IO
Read Tick clients, projects, tasks, users and time entries; log and edit time entries.
Available components
Last scanned (5 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +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.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://tick.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tick.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://tick.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://tick.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://tick.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://tick.usefulapi.io/mcp |
| Authorisation server | https://tick.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tick.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/tick/ |
| http (plaintext) | http://tick.usefulapi.io/mcp | Inconclusive | 302 | http://tick.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
tick_create_client Create client ~58
WRITE: create a new client (POST /clients.json). Tick administrators only (403 otherwise). Creates a new client every call.
| Name | Type | Req | Description |
|---|---|---|---|
| archive | boolean | – | Create the client archived (default false). |
| name | string | yes | Client name. |
No output schema declared.
No examples provided.
tick_create_entry Log time entry ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Day the work was done, yyyy-mm-dd. |
| hours | number | yes | Hours worked, decimal (1.5 = one and a half hours). |
| notes | string | – | What was done. |
| task_id | integer | yes | Task to log the time on. |
| user_id | integer | – | Administrators only: log the time for this user. |
No output schema declared.
No examples provided.
tick_create_project Create project ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | Whether the project is billable. |
| budget | number | – | Project budget (hours, or money for a money-based subscription). |
| client_id | integer | yes | Client the project belongs to (see tick_list_clients). |
| name | string | yes | Project name. |
| notifications | boolean | – | Send budget notifications. |
| owner_id | integer | – | User id of the project owner. |
| recurring | boolean | – | Recurring budget. |
No output schema declared.
No examples provided.
tick_create_task Create task ~82
WRITE: create a new task on a project (POST /tasks.json). Tick administrators only. Creates a new task every call.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | Whether the task is billable. |
| budget | number | – | Task budget (hours). |
| name | string | yes | Task name. |
| project_id | integer | yes | Project the task belongs to. |
No output schema declared.
No examples provided.
tick_get_client Get client ~44
One client by id, with a summary of its projects (count and URL). GET /clients/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | Tick client id. |
No output schema declared.
No examples provided.
tick_get_entry Get time entry ~38
One time entry by id, with its task. GET /entries/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| entry_id | integer | yes | Tick entry id. |
No output schema declared.
No examples provided.
tick_get_project Get project ~52
One project by id, with total_hours entered, a summary of its tasks (count and URL) and its client. GET /projects/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | Tick project id. |
No output schema declared.
No examples provided.
tick_get_task Get task ~52
One task by id, with total_hours entered, a summary of its entries (count and URL) and its project. GET /tasks/{id}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | integer | yes | Tick task id. |
No output schema declared.
No examples provided.
tick_list_clients List clients ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
tick_list_entries List time entries ~252
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
tick_list_projects List projects ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
tick_list_tasks List tasks ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
tick_list_users List users ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
tick_update_entry Update time entry ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| billed | boolean | – | Mark the entry as billed / not billed. |
| date | string | – | New date, yyyy-mm-dd. |
| entry_id | integer | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · tick.usefulapi.io
claude mcp add --transport http io-usefulapi-tick 'https://tick.usefulapi.io/mcp'
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.