Skip to content

Harvest MCP by usefulapi

io.usefulapi/harvestusefulapi.iostreamable-httpv1.40.4Scanned

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

20 tools: 5 can delete or cancel things and 15 only read.

Tools: 5 delete, 0 irreversible, 0 write, 15 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Harvest MCP by usefulapi can do

The Harvest MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 20 tools. It can delete or cancel things (5 tools: harvest_create_time_entry, harvest_update_time_entry, harvest_stop_time_entry, harvest_restart_time_entry and 1 more). 15 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

20 tools

Deletes or cancels 5Claude Code: deny
  • harvest_create_time_entryCreate a time entry.No findings

    Why it is in this group

    • The name "harvest_create_time_entry" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create time entry
    • destructiveHint: true
  • harvest_delete_time_entryPermanently delete a time entry by id.No findings

    Why it is in this group

    • The name "harvest_delete_time_entry" says "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Permanently delete a time entry by id. This cannot be undone. Harvest REST: DELETE /time_entries/{id}. WRITE — destroys data.

    Annotations the server declares

    • title: Delete time entry
    • destructiveHint: true
  • harvest_restart_time_entryRestart a previously stopped time entry, resuming its timer (error if it is already running).No findings

    Why it is in this group

    • The name "harvest_restart_time_entry" says "restart": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Restart stopped time entry
    • destructiveHint: true
  • harvest_stop_time_entryStop a currently running time entry (no-op error if it is already stopped).No findings

    Why it is in this group

    • The name "harvest_stop_time_entry" says "stop": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Stop a currently running time entry (no-op error if it is already stopped). Harvest REST: PATCH /time_entries/{id}/stop. WRITE — modifies data.

    Annotations the server declares

    • title: Stop running time entry
    • destructiveHint: true
  • harvest_update_time_entryUpdate an existing time entry's hours, notes, spent date, or project/task.No findings

    Why it is in this group

    • The name "harvest_update_time_entry" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update time entry
    • destructiveHint: true
Only reads 15Show 15 read-only tools
  • harvest_get_clientRetrieve a single client by id.No findings

    Why it is in this group

    • The name "harvest_get_client" says "get": a word for reading.
    Description, as the server wrote it
    Retrieve a single client by id. Harvest REST: GET /clients/{id}.

    Annotations the server declares

    • title: Get client
    • readOnlyHint: true
  • harvest_get_companyRetrieve the company/account settings for the authenticated account (name, currency, time/date formats, week start, feature flags).No findings

    Why it is in this group

    • The name "harvest_get_company" says "get": a word for reading.
    Description, as the server wrote it
    Retrieve the company/account settings for the authenticated account (name, currency, time/date formats, week start, feature flags). Harvest REST: GET /company.

    Annotations the server declares

    • title: Get company
    • readOnlyHint: true
  • harvest_get_current_userRetrieve the currently authenticated user (whom the access token belongs to).No findings

    Why it is in this group

    • The name "harvest_get_current_user" says "get": a word for reading.
    Description, as the server wrote it
    Retrieve the currently authenticated user (whom the access token belongs to). Harvest REST: GET /users/me.

    Annotations the server declares

    • title: Get current user
    • readOnlyHint: true
  • harvest_get_invoiceRetrieve a single invoice by id, including its line items.No findings

    Why it is in this group

    • The name "harvest_get_invoice" says "get": a word for reading.
    Description, as the server wrote it
    Retrieve a single invoice by id, including its line items. Harvest REST: GET /invoices/{id}.

    Annotations the server declares

    • title: Get invoice
    • readOnlyHint: true
  • harvest_get_projectRetrieve a single project by id.No findings

    Why it is in this group

    • The name "harvest_get_project" says "get": a word for reading.
    Description, as the server wrote it
    Retrieve a single project by id. Harvest REST: GET /projects/{id}.

    Annotations the server declares

    • title: Get project
    • readOnlyHint: true
  • harvest_get_time_entryRetrieve a single time entry by id.No findings

    Why it is in this group

    • The name "harvest_get_time_entry" says "get": a word for reading.
    Description, as the server wrote it
    Retrieve a single time entry by id. Harvest REST: GET /time_entries/{id}.

    Annotations the server declares

    • title: Get time entry
    • readOnlyHint: true
  • harvest_list_clientsList clients, optionally filtered by active status or updated-since.No findings

    Why it is in this group

    • The name "harvest_list_clients" says "list": a word for reading.
    Description, as the server wrote it
    List clients, optionally filtered by active status or updated-since. Paginated. Harvest REST: GET /clients.

    Annotations the server declares

    • title: List clients
    • readOnlyHint: true
  • harvest_list_estimatesList estimates, optionally filtered by client, state, date range, or updated-since.No findings

    Why it is in this group

    • The name "harvest_list_estimates" says "list": a word for reading.
    Description, as the server wrote it
    List estimates, optionally filtered by client, state, date range, or updated-since. Paginated. Harvest REST: GET /estimates.

    Annotations the server declares

    • title: List estimates
    • readOnlyHint: true
  • harvest_list_expensesList expenses, optionally filtered by user, client, project, date range, billed status, or updated-since.No findings

    Why it is in this group

    • The name "harvest_list_expenses" says "list": a word for reading.
    Description, as the server wrote it
    List expenses, optionally filtered by user, client, project, date range, billed status, or updated-since. Paginated. Harvest REST: GET /expenses.

    Annotations the server declares

    • title: List expenses
    • readOnlyHint: true
  • harvest_list_invoicesList invoices, optionally filtered by client, project, state, date range, or updated-since.No findings

    Why it is in this group

    • The name "harvest_list_invoices" says "list": a word for reading.
    Description, as the server wrote it
    List invoices, optionally filtered by client, project, state, date range, or updated-since. Paginated. Harvest REST: GET /invoices.

    Annotations the server declares

    • title: List invoices
    • readOnlyHint: true
  • harvest_list_project_assignmentsList 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 …No findings

    Why it is in this group

    • The name "harvest_list_project_assignments" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List my project assignments
    • readOnlyHint: true
  • harvest_list_projectsList projects, optionally filtered by active status or client, or updated-since.No findings

    Why it is in this group

    • The name "harvest_list_projects" says "list": a word for reading.
    Description, as the server wrote it
    List projects, optionally filtered by active status or client, or updated-since. Paginated. Harvest REST: GET /projects.

    Annotations the server declares

    • title: List projects
    • readOnlyHint: true
  • harvest_list_tasksList tasks (the billable/non-billable work categories that can be assigned to projects), optionally filtered by active status or updated-since.No findings

    Why it is in this group

    • The name "harvest_list_tasks" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List tasks
    • readOnlyHint: true
  • harvest_list_time_entriesList time entries, optionally filtered by user, project, client, task, date range, running/billed status, or updated-since.No findings

    Why it is in this group

    • The name "harvest_list_time_entries" says "list": a word for reading.
    Description, as the server wrote it
    List time entries, optionally filtered by user, project, client, task, date range, running/billed status, or updated-since. Paginated. Harvest REST: GET /time_entries.

    Annotations the server declares

    • title: List time entries
    • readOnlyHint: true
  • harvest_list_usersList users in the account, optionally filtered by active status or updated-since.No findings

    Why it is in this group

    • The name "harvest_list_users" says "list": a word for reading.
    Description, as the server wrote it
    List users in the account, optionally filtered by active status or updated-since. Paginated. Harvest REST: GET /users.

    Annotations the server declares

    • title: List users
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://harvest.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://harvest.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://harvest.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://harvest.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http harvest https://harvest.usefulapi.io/mcp
claude mcp add --transport http harvest https://harvest.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__harvest__harvest_list_time_entries",
      "mcp__harvest__harvest_get_time_entry",
      "mcp__harvest__harvest_list_projects",
      "mcp__harvest__harvest_get_project",
      "mcp__harvest__harvest_list_clients",
      "mcp__harvest__harvest_get_client",
      "mcp__harvest__harvest_list_tasks",
      "mcp__harvest__harvest_list_users",
      "mcp__harvest__harvest_get_current_user",
      "mcp__harvest__harvest_list_project_assignments",
      "mcp__harvest__harvest_list_invoices",
      "mcp__harvest__harvest_get_invoice",
      "mcp__harvest__harvest_list_estimates",
      "mcp__harvest__harvest_list_expenses",
      "mcp__harvest__harvest_get_company"
    ],
    "ask": [],
    "deny": [
      "mcp__harvest__harvest_create_time_entry",
      "mcp__harvest__harvest_update_time_entry",
      "mcp__harvest__harvest_stop_time_entry",
      "mcp__harvest__harvest_restart_time_entry",
      "mcp__harvest__harvest_delete_time_entry"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as harvest. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/harvest/verify?hash=04c1992f04fd48e6a41da48da3a6b07ff8be95cc4f1f00440e70238fdbfe15fd" | jq -e '.changed == false'

Pinned hash 04c1992f04fd, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/harvest/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/harvest
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/harvest.svg)](https://radar.anlyon.com/servers/io.usefulapi/harvest)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Harvest MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Harvest MCP by usefulapi safe?

No scan can promise that. What its definitions show: 20 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Harvest MCP by usefulapi delete data?

Yes. 5 tools can delete, cancel or revoke something: harvest_create_time_entry, harvest_update_time_entry, harvest_stop_time_entry, harvest_restart_time_entry and harvest_delete_time_entry.

Can the Harvest MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Harvest MCP by usefulapi have?

20 tools: 5 destructive, 15 read. harvest_create_time_entry, harvest_update_time_entry, harvest_stop_time_entry, harvest_restart_time_entry, harvest_delete_time_entry, harvest_list_time_entries, harvest_get_time_entry, harvest_list_projects and 12 more.

Does the Harvest MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Harvest MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Harvest MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.