Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Harvest MCP by usefulapi

REMOTE · HARVEST.USEFULAPI.IO

Read time entries, projects, clients, tasks and invoices; log and update tracked time.

−59 this week 18 Trust /100

Last scanned (33 minutes ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

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.

  • 2 Nov 26 −62
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 31 Oct 26 +3
    • Authorization: partial → pass ▲ security
    • MCP protocol: fail → pass ▲ functional
    • New prompt “find_unpaid_invoices_for_a_client” functional
    • New prompt “fix_or_delete_a_wrong_time_entry” functional
    • New prompt “list_expenses_that_are_not_yet_billed” functional
    • New prompt “log_hours_or_start_stop_and_restart_a_timer” functional
    • New prompt “summarize_hours_logged_by_project_client_or_person” functional
    • MCP protocol version: 2025-06-18 → 2025-11-25 functional
    • Server version: 1.31.0 → 1.33.0 functional
    • Server version: 1.30.0 → 1.31.0 functional
    • Server version: 1.29.2 → 1.30.0 functional
  • 30 Oct 26 0
    • Server version: 1.29.1 → 1.29.2 functional
    • Server version: 1.29.0 → 1.29.1 functional
  • 29 Oct 26 0
    • Server version: 1.28.0 → 1.29.0 functional
    • Server version: 1.27.0 → 1.28.0 functional
  • 28 Oct 26 0
    • Server version: 1.25.0 → 1.27.0 functional
  • 27 Oct 26 0
    • Server version: 1.24.0 → 1.25.0 functional
  • 25 Oct 26 0
    • Server version: 1.23.0 → 1.24.0 functional
    • Server version: 1.22.0 → 1.23.0 functional
    • Server version: 1.21.3 → 1.22.0 functional
    • Server version: 1.21.0 → 1.21.3 functional
  • 24 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 1.20.0 → 1.21.0 functional
    • Server version: 1.19.0 → 1.20.0 functional
    • Server version: 1.17.0 → 1.19.0 functional
Diagnostics

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 5 Nov 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 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 harvest.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

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 Redirected 302 https://usefulapi.io/harvest/
http (plaintext) http://harvest.usefulapi.io/mcp Inconclusive 302 http://harvest.usefulapi.io/mcp
MCP tools · 20 exposed · ~2,204 tokens

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 →

Tool Tokens
harvest_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.

NameTypeReqDescription
ended_timestring–End time for a timestamped entry, e.g. '9:30am'.
hoursnumber–Duration in decimal hours, e.g. 1.5. Omit to start a running timer.
notesstring–Notes for the time entry.
project_idintegeryesThe project id to log time against (required).
spent_datestringyesThe date the time was spent, yyyy-mm-dd (required).
started_timestring–Start time for a timestamped entry, e.g. '8:00am'.
task_idintegeryesThe task id within the project (required).
user_idinteger–Log on behalf of another user (defaults to the authenticated user; requires permission).

No output schema declared.

No examples provided.

harvest_delete_time_entry ~56

Permanently delete a time entry by id. This cannot be undone. Harvest REST: DELETE /time_entries/{id}. WRITE — destroys data.

NameTypeReqDescription
time_entry_idintegeryesThe time entry id to delete (required).

No output schema declared.

No examples provided.

harvest_get_client ~38

Retrieve a single client by id. Harvest REST: GET /clients/{id}.

NameTypeReqDescription
client_idintegeryesThe client id (required).

No output schema declared.

No examples provided.

harvest_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 ~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 ~44

Retrieve a single invoice by id, including its line items. Harvest REST: GET /invoices/{id}.

NameTypeReqDescription
invoice_idintegeryesThe invoice id (required).

No output schema declared.

No examples provided.

harvest_get_project ~38

Retrieve a single project by id. Harvest REST: GET /projects/{id}.

NameTypeReqDescription
project_idintegeryesThe project id (required).

No output schema declared.

No examples provided.

harvest_get_time_entry ~43

Retrieve a single time entry by id. Harvest REST: GET /time_entries/{id}.

NameTypeReqDescription
time_entry_idintegeryesThe time entry id (required).

No output schema declared.

No examples provided.

harvest_list_clients ~106

List clients, optionally filtered by active status or updated-since. Paginated. Harvest REST: GET /clients.

NameTypeReqDescription
is_activeboolean–Only active (true) or archived (false) clients.
pageinteger–Page number (1-based) for pagination.
per_pageinteger–Results per page (1–2000, Harvest default 2000).
updated_sincestring–Only clients updated since this ISO-8601 datetime.

No output schema declared.

No examples provided.

harvest_list_estimates ~165

List estimates, optionally filtered by client, state, date range, or updated-since. Paginated. Harvest REST: GET /estimates.

NameTypeReqDescription
client_idinteger–Filter to a single client id.
fromstring–Only estimates issued on/after this date, yyyy-mm-dd.
pageinteger–Page number (1-based) for pagination.
per_pageinteger–Results per page (1–2000, Harvest default 2000).
statestring–Filter by estimate state: draft, sent, accepted or declined.
tostring–Only estimates issued on/before this date, yyyy-mm-dd.
updated_sincestring–Only estimates updated since this ISO-8601 datetime.

No output schema declared.

No examples provided.

harvest_list_expenses ~198

List expenses, optionally filtered by user, client, project, date range, billed status, or updated-since. Paginated. Harvest REST: GET /expenses.

NameTypeReqDescription
client_idinteger–Filter to a single client id.
fromstring–Only expenses on/after this date, yyyy-mm-dd.
is_billedboolean–Only billed (true) or unbilled (false) expenses.
pageinteger–Page number (1-based) for pagination.
per_pageinteger–Results per page (1–2000, Harvest default 2000).
project_idinteger–Filter to a single project id.
tostring–Only expenses on/before this date, yyyy-mm-dd.
updated_sincestring–Only expenses updated since this ISO-8601 datetime.
user_idinteger–Filter to a single user id.

No output schema declared.

No examples provided.

harvest_list_invoices ~181

List invoices, optionally filtered by client, project, state, date range, or updated-since. Paginated. Harvest REST: GET /invoices.

NameTypeReqDescription
client_idinteger–Filter to a single client id.
fromstring–Only invoices issued on/after this date, yyyy-mm-dd.
pageinteger–Page number (1-based) for pagination.
per_pageinteger–Results per page (1–2000, Harvest default 2000).
project_idinteger–Filter to a single project id.
statestring–Filter by invoice state: draft, open, paid or closed.
tostring–Only invoices issued on/before this date, yyyy-mm-dd.
updated_sincestring–Only invoices updated since this ISO-8601 datetime.

No output schema declared.

No examples provided.

harvest_list_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.

NameTypeReqDescription
pageinteger–Page number (1-based) for pagination.
per_pageinteger–Results per page (1–2000, Harvest default 2000).

No output schema declared.

No examples provided.

harvest_list_projects ~123

List projects, optionally filtered by active status or client, or updated-since. Paginated. Harvest REST: GET /projects.

NameTypeReqDescription
client_idinteger–Filter to a single client id.
is_activeboolean–Only active (true) or archived (false) projects.
pageinteger–Page number (1-based) for pagination.
per_pageinteger–Results per page (1–2000, Harvest default 2000).
updated_sincestring–Only projects updated since this ISO-8601 datetime.

No output schema declared.

No examples provided.

harvest_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.

NameTypeReqDescription
is_activeboolean–Only active (true) or archived (false) tasks.
pageinteger–Page number (1-based) for pagination.
per_pageinteger–Results per page (1–2000, Harvest default 2000).
updated_sincestring–Only tasks updated since this ISO-8601 datetime.

No output schema declared.

No examples provided.

harvest_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.

NameTypeReqDescription
client_idinteger–Filter to a single client id.
fromstring–Only entries on/after this date, yyyy-mm-dd.
is_billedboolean–Only billed (true) or unbilled (false) entries.
is_runningboolean–Only running (true) or only stopped (false) entries.
pageinteger–Page number (1-based) for pagination.
per_pageinteger–Results per page (1–2000, Harvest default 2000).
project_idinteger–Filter to a single project id.
task_idinteger–Filter to a single task id.
tostring–Only entries on/before this date, yyyy-mm-dd.
updated_sincestring–Only entries updated since this ISO-8601 datetime.
user_idinteger–Filter to a single user id.

No output schema declared.

No examples provided.

harvest_list_users ~109

List users in the account, optionally filtered by active status or updated-since. Paginated. Harvest REST: GET /users.

NameTypeReqDescription
is_activeboolean–Only active (true) or archived (false) users.
pageinteger–Page number (1-based) for pagination.
per_pageinteger–Results per page (1–2000, Harvest default 2000).
updated_sincestring–Only users updated since this ISO-8601 datetime.

No output schema declared.

No examples provided.

harvest_restart_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.

NameTypeReqDescription
time_entry_idintegeryesThe stopped time entry id to restart (required).

No output schema declared.

No examples provided.

harvest_stop_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.

NameTypeReqDescription
time_entry_idintegeryesThe running time entry id to stop (required).

No output schema declared.

No examples provided.

harvest_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.

NameTypeReqDescription
ended_timestring–Change the end time, e.g. '9:30am'.
hoursnumber–Change the duration in decimal hours, e.g. 2.25.
notesstring–Change the notes.
project_idinteger–Reassign to a different project id.
spent_datestring–Change the date, yyyy-mm-dd.
started_timestring–Change the start time, e.g. '8:00am'.
task_idinteger–Reassign to a different task id.
time_entry_idintegeryesThe time entry id to update (required).

No output schema declared.

No examples provided.

Install

How do I install the Harvest MCP by usefulapi server?

Harvest MCP by usefulapi 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

# add to Claude Code
claude mcp add --transport http io-usefulapi-harvest 'https://harvest.usefulapi.io/mcp'
Common questions

What is the Harvest MCP by usefulapi server?

Harvest MCP by usefulapi is 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 Harvest MCP by usefulapi server safe to use?

Harvest MCP by usefulapi scores 18 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 Harvest MCP by usefulapi server expose?

Harvest MCP by usefulapi 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 Harvest MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Harvest MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Harvest MCP by usefulapi server still maintained?

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