io.usefulapi/harvest
REMOTE · HARVEST.USEFULAPI.IO · SCANNED SEP 20
Read time entries, projects, clients, tasks and invoices; log and update tracked time.
Available components
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 answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2204 tokens (~110/item across 20 items; 20 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 20 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
How do I install the io.usefulapi/harvest MCP server?
io.usefulapi/harvest is a hosted endpoint at https://harvest.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 · harvest.usefulapi.io
claude mcp add --transport http io-usefulapi-harvest 'https://harvest.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-harvest": {
"url": "https://harvest.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-harvest": {
"type": "http",
"url": "https://harvest.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-harvest] url = "https://harvest.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-harvest": {
"type": "remote",
"url": "https://harvest.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-harvest --url 'https://harvest.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-harvest:
url: "https://harvest.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-harvest": {
"Transport": "http",
"Url": "https://harvest.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-harvest -t streamable-http -u 'https://harvest.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-harvest": {
"type": "http",
"url": "https://harvest.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 1 Sept 26 +1
- Stability: 0.97 → pass security
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
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 20 Sept 2026 · Probed https://harvest.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 | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | aea215b633fe902513d8a20341057234 |
| SANs: usefulapi.io, harvest.usefulapi.io, *.harvest.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 harvest.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 | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://harvest.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://harvest.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://harvest.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://harvest.usefulapi.io/mcp |
| Authorisation server | https://harvest.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://harvest.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://harvest.usefulapi.io/mcp | Inconclusive | 401 |
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 →
harvest_create_time_entry Create time entry ~260
Create a time entry. Requires project_id, task_id and spent_date. Provide `hours` to log a specific duration; OR provide `started_time` (+ optional `ended_time`) for a timestamped entry; OR omit both to start a running timer (on a timestamp-tracking account). Use harvest_list_project_assignments to find valid project_id + task_id. Harvest REST: POST /time_entries. WRITE — creates data.
| Name | Type | Req | Description |
|---|---|---|---|
| ended_time | string | – | End time for a timestamped entry, e.g. '9:30am'. |
| hours | number | – | Duration in decimal hours, e.g. 1.5. Omit to start a running timer. |
| notes | string | – | Notes for the time entry. |
| project_id | integer | yes | The project id to log time against (required). |
| spent_date | string | yes | The date the time was spent, yyyy-mm-dd (required). |
| started_time | string | – | Start time for a timestamped entry, e.g. '8:00am'. |
| task_id | integer | yes | The task id within the project (required). |
| user_id | integer | – | Log on behalf of another user (defaults to the authenticated user; requires permission). |
No output schema declared.
No examples provided.
harvest_delete_time_entry Delete time entry ~56
Permanently delete a time entry by id. This cannot be undone. Harvest REST: DELETE /time_entries/{id}. WRITE — destroys data.
| Name | Type | Req | Description |
|---|---|---|---|
| time_entry_id | integer | yes | The time entry id to delete (required). |
No output schema declared.
No examples provided.
harvest_get_client Get client ~38
Retrieve a single client by id. Harvest REST: GET /clients/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | The client id (required). |
No output schema declared.
No examples provided.
harvest_get_company Get company ~40
Retrieve the company/account settings for the authenticated account (name, currency, time/date formats, week start, feature flags). Harvest REST: GET /company.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
harvest_get_current_user Get current user ~32
Retrieve the currently authenticated user (whom the access token belongs to). Harvest REST: GET /users/me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
harvest_get_invoice Get invoice ~44
Retrieve a single invoice by id, including its line items. Harvest REST: GET /invoices/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | integer | yes | The invoice id (required). |
No output schema declared.
No examples provided.
harvest_get_project Get project ~38
Retrieve a single project by id. Harvest REST: GET /projects/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | The project id (required). |
No output schema declared.
No examples provided.
harvest_get_time_entry Get time entry ~43
Retrieve a single time entry by id. Harvest REST: GET /time_entries/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| time_entry_id | integer | yes | The time entry id (required). |
No output schema declared.
No examples provided.
harvest_list_clients List clients ~106
List clients, optionally filtered by active status or updated-since. Paginated. Harvest REST: GET /clients.
| Name | Type | Req | Description |
|---|---|---|---|
| is_active | boolean | – | Only active (true) or archived (false) clients. |
| page | integer | – | Page number (1-based) for pagination. |
| per_page | integer | – | Results per page (1–2000, Harvest default 2000). |
| updated_since | string | – | Only clients updated since this ISO-8601 datetime. |
No output schema declared.
No examples provided.
harvest_list_estimates List estimates ~165
List estimates, optionally filtered by client, state, date range, or updated-since. Paginated. Harvest REST: GET /estimates.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | – | Filter to a single client id. |
| from | string | – | Only estimates issued on/after this date, yyyy-mm-dd. |
| page | integer | – | Page number (1-based) for pagination. |
| per_page | integer | – | Results per page (1–2000, Harvest default 2000). |
| state | string | – | Filter by estimate state: draft, sent, accepted or declined. |
| to | string | – | Only estimates issued on/before this date, yyyy-mm-dd. |
| updated_since | string | – | Only estimates updated since this ISO-8601 datetime. |
No output schema declared.
No examples provided.
harvest_list_expenses List expenses ~198
List expenses, optionally filtered by user, client, project, date range, billed status, or updated-since. Paginated. Harvest REST: GET /expenses.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | – | Filter to a single client id. |
| from | string | – | Only expenses on/after this date, yyyy-mm-dd. |
| is_billed | boolean | – | Only billed (true) or unbilled (false) expenses. |
| page | integer | – | Page number (1-based) for pagination. |
| per_page | integer | – | Results per page (1–2000, Harvest default 2000). |
| project_id | integer | – | Filter to a single project id. |
| to | string | – | Only expenses on/before this date, yyyy-mm-dd. |
| updated_since | string | – | Only expenses updated since this ISO-8601 datetime. |
| user_id | integer | – | Filter to a single user id. |
No output schema declared.
No examples provided.
harvest_list_invoices List invoices ~181
List invoices, optionally filtered by client, project, state, date range, or updated-since. Paginated. Harvest REST: GET /invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | – | Filter to a single client id. |
| from | string | – | Only invoices issued on/after this date, yyyy-mm-dd. |
| page | integer | – | Page number (1-based) for pagination. |
| per_page | integer | – | Results per page (1–2000, Harvest default 2000). |
| project_id | integer | – | Filter to a single project id. |
| state | string | – | Filter by invoice state: draft, open, paid or closed. |
| to | string | – | Only invoices issued on/before this date, yyyy-mm-dd. |
| updated_since | string | – | Only invoices updated since this ISO-8601 datetime. |
No output schema declared.
No examples provided.
harvest_list_project_assignments List my project assignments ~101
List the authenticated user's active project assignments — the projects and their assignable tasks the current user can log time against (use this to find the project_id + task_id for harvest_create_time_entry). Paginated. Harvest REST: GET /users/me/project_assignments.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based) for pagination. |
| per_page | integer | – | Results per page (1–2000, Harvest default 2000). |
No output schema declared.
No examples provided.
harvest_list_projects List projects ~123
List projects, optionally filtered by active status or client, or updated-since. Paginated. Harvest REST: GET /projects.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | – | Filter to a single client id. |
| is_active | boolean | – | Only active (true) or archived (false) projects. |
| page | integer | – | Page number (1-based) for pagination. |
| per_page | integer | – | Results per page (1–2000, Harvest default 2000). |
| updated_since | string | – | Only projects updated since this ISO-8601 datetime. |
No output schema declared.
No examples provided.
harvest_list_tasks List tasks ~122
List tasks (the billable/non-billable work categories that can be assigned to projects), optionally filtered by active status or updated-since. Paginated. Harvest REST: GET /tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| is_active | boolean | – | Only active (true) or archived (false) tasks. |
| page | integer | – | Page number (1-based) for pagination. |
| per_page | integer | – | Results per page (1–2000, Harvest default 2000). |
| updated_since | string | – | Only tasks updated since this ISO-8601 datetime. |
No output schema declared.
No examples provided.
harvest_list_time_entries List time entries ~238
List time entries, optionally filtered by user, project, client, task, date range, running/billed status, or updated-since. Paginated. Harvest REST: GET /time_entries.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | – | Filter to a single client id. |
| from | string | – | Only entries on/after this date, yyyy-mm-dd. |
| is_billed | boolean | – | Only billed (true) or unbilled (false) entries. |
| is_running | boolean | – | Only running (true) or only stopped (false) entries. |
| page | integer | – | Page number (1-based) for pagination. |
| per_page | integer | – | Results per page (1–2000, Harvest default 2000). |
| project_id | integer | – | Filter to a single project id. |
| task_id | integer | – | Filter to a single task id. |
| to | string | – | Only entries on/before this date, yyyy-mm-dd. |
| updated_since | string | – | Only entries updated since this ISO-8601 datetime. |
| user_id | integer | – | Filter to a single user id. |
No output schema declared.
No examples provided.
harvest_list_users List users ~109
List users in the account, optionally filtered by active status or updated-since. Paginated. Harvest REST: GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| is_active | boolean | – | Only active (true) or archived (false) users. |
| page | integer | – | Page number (1-based) for pagination. |
| per_page | integer | – | Results per page (1–2000, Harvest default 2000). |
| updated_since | string | – | Only users updated since this ISO-8601 datetime. |
No output schema declared.
No examples provided.
harvest_restart_time_entry Restart stopped time entry ~64
Restart a previously stopped time entry, resuming its timer (error if it is already running). Harvest REST: PATCH /time_entries/{id}/restart. WRITE — modifies data.
| Name | Type | Req | Description |
|---|---|---|---|
| time_entry_id | integer | yes | The stopped time entry id to restart (required). |
No output schema declared.
No examples provided.
harvest_stop_time_entry Stop running time entry ~61
Stop a currently running time entry (no-op error if it is already stopped). Harvest REST: PATCH /time_entries/{id}/stop. WRITE — modifies data.
| Name | Type | Req | Description |
|---|---|---|---|
| time_entry_id | integer | yes | The running time entry id to stop (required). |
No output schema declared.
No examples provided.
harvest_update_time_entry Update time entry ~185
Update an existing time entry's hours, notes, spent date, or project/task. Only the fields you provide are changed. Harvest REST: PATCH /time_entries/{id}. WRITE — modifies data.
| Name | Type | Req | Description |
|---|---|---|---|
| ended_time | string | – | Change the end time, e.g. '9:30am'. |
| hours | number | – | Change the duration in decimal hours, e.g. 2.25. |
| notes | string | – | Change the notes. |
| project_id | integer | – | Reassign to a different project id. |
| spent_date | string | – | Change the date, yyyy-mm-dd. |
| started_time | string | – | Change the start time, e.g. '8:00am'. |
| task_id | integer | – | Reassign to a different task id. |
| time_entry_id | integer | yes | The time entry id to update (required). |
No output schema declared.
No examples provided.
What is the io.usefulapi/harvest MCP server?
io.usefulapi/harvest is an MCP server listed in the public MCP registry as io.usefulapi/harvest. Read time entries, projects, clients, tasks and invoices; log and update tracked time. This page covers its hosted endpoint (https://harvest.usefulapi.io/mcp).
Is the io.usefulapi/harvest MCP server safe to use?
io.usefulapi/harvest scores 87 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 io.usefulapi/harvest MCP server expose?
io.usefulapi/harvest exposes 20 tools: harvest_list_time_entries, harvest_get_time_entry, harvest_list_projects, harvest_get_project, harvest_list_clients, and 15 more. Their descriptions and schemas cost roughly 2,204 tokens of context every time the server is loaded.
Does the io.usefulapi/harvest MCP server require authentication?
Yes. io.usefulapi/harvest 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 io.usefulapi/harvest MCP server still maintained?
io.usefulapi/harvest is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.