# io.usefulapi/paymo (remote · paymo.usefulapi.io)

Browse Paymo projects, tasks, timesheets and invoices, and create tasks, log time or run timers.

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

## Components

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

## Channel facts

- Endpoint: `https://paymo.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-04.

- **Endpoint Security**: 89/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 is enforced; there's no plaintext access path.
  - 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**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3117 tokens (~148/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 21 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 io.usefulapi/paymo MCP server?

io.usefulapi/paymo is a hosted endpoint at https://paymo.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-paymo 'https://paymo.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-paymo": {
      "type": "http",
      "url": "https://paymo.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-03 (score 77, +1)

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

### 2026-10-02 (score 76, 0)

- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 76, +5)

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-30 (score 71, +53)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (21)

### `paymo_get_me` (~61 tokens)

Get the current user

Fetch the Paymo user the API key belongs to (id, name, type, timezone). Use the id as user_id for 'my' time entries and timers. A cheap way to confirm the key works. Paymo: GET /api/me.

### `paymo_get_company` (~41 tokens)

Get company info

Fetch the company (account) info and settings: name, default currency, timezone, working days, invoice numbering. Paymo: GET /api/company.

### `paymo_list_users` (~157 tokens)

List users

List users in the company (id, name, email, type, hourly rate, assigned/managed projects). Paymo: GET /api/users.

Input parameters:

- `active` (boolean): true = active users only, false = retired users only.
- `limit` (integer): Max items to return (default 100, max 500). Paymo has no pagination; results beyond this are truncated.
- `type` (string): Only users of this type.
- `where` (string): Extra raw Paymo filter ANDed onto the typed ones, e.g. `billable=true` or `name like Website`. Operators: = > >= < <= != like, not like, in (a,b), not in (a,b).

### `paymo_list_clients` (~165 tokens)

List clients

List clients (id, name, contact details, active flag). Paymo: GET /api/clients.

Input parameters:

- `active` (boolean): true = active clients only, false = archived only.
- `include` (string): Related objects to embed (Paymo `include`), comma-separated, e.g. client or tasklists.tasks.
- `limit` (integer): Max items to return (default 100, max 500). Paymo has no pagination; results beyond this are truncated.
- `where` (string): Extra raw Paymo filter ANDed onto the typed ones, e.g. `billable=true` or `name like Website`. Operators: = > >= < <= != like, not like, in (a,b), not in (a,b).

### `paymo_list_projects` (~240 tokens)

List projects

List projects (id, name, code, client_id, active, billable, budget_hours, users, managers), optionally filtered. Paymo: GET /api/projects.

Input parameters:

- `active` (boolean): true = active projects, false = archived.
- `billable` (boolean): Only billable (true) or non-billable (false) projects.
- `client_id` (integer): Only projects for this client.
- `include` (string): Related objects to embed (Paymo `include`), comma-separated, e.g. client or tasklists.tasks.
- `limit` (integer): Max items to return (default 100, max 500). Paymo has no pagination; results beyond this are truncated.
- `manager_id` (integer): Only projects this user manages.
- `user_id` (integer): Only projects this user is assigned to.
- `where` (string): Extra raw Paymo filter ANDed onto the typed ones, e.g. `billable=true` or `name like Website`. Operators: = > >= < <= != like, not like, in (a,b), not in (a,b).

### `paymo_get_project` (~88 tokens)

Get a project

Fetch one project, optionally with related objects inline, e.g. include=tasklists.tasks for the whole task tree or include=client. Paymo: GET /api/projects/{id}.

Input parameters:

- `include` (string): Related objects to embed (Paymo `include`), comma-separated, e.g. client or tasklists.tasks.
- `project_id` (integer, required): The project id.

### `paymo_list_tasklists` (~122 tokens)

List task lists

List task lists (id, name, project_id, milestone_id), e.g. to pick a tasklist_id when creating a task. Paymo: GET /api/tasklists.

Input parameters:

- `include` (string): Related objects to embed (Paymo `include`), comma-separated, e.g. client or tasklists.tasks.
- `limit` (integer): Max items to return (default 100, max 500). Paymo has no pagination; results beyond this are truncated.
- `project_id` (integer): Only task lists from this project.

### `paymo_list_tasks` (~263 tokens)

List tasks

List tasks (id, name, code, project_id, tasklist_id, complete, due_date, users, priority), filtered by project, task list, assignee or completion. my_tasks=true returns the caller's 'My Tasks'. Paymo: GET /api/tasks.

Input parameters:

- `complete` (boolean): true = completed tasks, false = open tasks.
- `include` (string): Related objects to embed (Paymo `include`), comma-separated, e.g. client or tasklists.tasks.
- `limit` (integer): Max items to return (default 100, max 500). Paymo has no pagination; results beyond this are truncated.
- `my_tasks` (boolean): true = tasks assigned to the calling user or to nobody, in their projects.
- `project_id` (integer): Only tasks from this project.
- `tasklist_id` (integer): Only tasks from this task list.
- `user_id` (integer): Only tasks assigned to this user.
- `where` (string): Extra raw Paymo filter ANDed onto the typed ones, e.g. `billable=true` or `name like Website`. Operators: = > >= < <= != like, not like, in (a,b), not in (a,b).

### `paymo_get_task` (~89 tokens)

Get a task

Fetch one task, optionally with related objects: include=thread.comments for its comments, subtasks, entries (time logged), files, project. Paymo: GET /api/tasks/{id}.

Input parameters:

- `include` (string): Related objects to embed (Paymo `include`), comma-separated, e.g. client or tasklists.tasks.
- `task_id` (integer, required): The task id.

### `paymo_list_time_entries` (~324 tokens)

List time entries

List time entries (id, task_id, user_id, project_id, start_time/end_time or date, duration in seconds, description, billed). At least one filter is required. from/to filter by the entry's time interval; running_only=true returns running timers. Paymo: GET /api/entries.

Input parameters:

- `billed` (boolean): true = already invoiced, false = unbilled.
- `client_id` (integer): Only entries for this client.
- `from` (string): Interval start (YYYY-MM-DD = start of that day UTC). Requires `to`.
- `include` (string): Related objects to embed (Paymo `include`), comma-separated, e.g. client or tasklists.tasks.
- `limit` (integer): Max items to return (default 100, max 500). Paymo has no pagination; results beyond this are truncated.
- `project_id` (integer): Only entries from this project.
- `running_only` (boolean): true = only running timers (no end_time yet).
- `task_id` (integer): Only entries for this task.
- `to` (string): Interval end (YYYY-MM-DD = end of that day UTC). Requires `from`.
- `user_id` (integer): Only entries for this user.
- `where` (string): Extra raw Paymo filter ANDed onto the typed ones, e.g. `billable=true` or `name like Website`. Operators: = > >= < <= != like, not like, in (a,b), not in (a,b).

### `paymo_list_invoices` (~155 tokens)

List invoices

List invoices (id, number, client_id, status, currency, date, due_date, subtotal, total). Paymo: GET /api/invoices.

Input parameters:

- `client_id` (integer): Only invoices for this client.
- `limit` (integer): Max items to return (default 100, max 500). Paymo has no pagination; results beyond this are truncated.
- `status` (string): Only invoices with this status.
- `where` (string): Extra raw Paymo filter ANDed onto the typed ones, e.g. `billable=true` or `name like Website`. Operators: = > >= < <= != like, not like, in (a,b), not in (a,b).

### `paymo_get_invoice` (~73 tokens)

Get an invoice

Fetch one invoice with totals, and (by default) its line items and payments. Paymo: GET /api/invoices/{id}?include=invoiceitems,invoicepayments.

Input parameters:

- `include_items` (boolean): Include line items and payments (default true).
- `invoice_id` (integer, required): The invoice id.

### `paymo_list_expenses` (~212 tokens)

List expenses

List expenses (id, client_id, project_id, user_id, amount, currency, date, notes, invoiced, tags). Paymo: GET /api/expenses.

Input parameters:

- `client_id` (integer): Only expenses for this client.
- `date_from` (string): Only expenses dated on/after this day.
- `date_to` (string): Only expenses dated on/before this day.
- `invoiced` (boolean): true = already invoiced, false = not yet invoiced.
- `limit` (integer): Max items to return (default 100, max 500). Paymo has no pagination; results beyond this are truncated.
- `project_id` (integer): Only expenses for this project.
- `where` (string): Extra raw Paymo filter ANDed onto the typed ones, e.g. `billable=true` or `name like Website`. Operators: = > >= < <= != like, not like, in (a,b), not in (a,b).

### `paymo_create_project` (~149 tokens)

Create a project

Create a project. Note: if client_id is omitted Paymo auto-creates a 'Sample Client'. Free plans have an active-projects limit (403). Paymo: POST /api/projects.

Input parameters:

- `billable` (boolean): Whether the project is billable.
- `budget_hours` (number): Budget in hours.
- `client_id` (integer): Client the project is for.
- `description` (string): Project description.
- `managers` (array): User ids of managers (subset of users).
- `name` (string, required): Project name.
- `price_per_hour` (number): Hourly rate for time & materials projects.
- `users` (array): User ids to assign.

### `paymo_create_task` (~174 tokens)

Create a task

Create a task in a task list (tasklist_id) or a project (project_id — goes to its 'Default Task List'). Paymo: POST /api/tasks.

Input parameters:

- `billable` (boolean): Whether the task is billable.
- `budget_hours` (number): Budget hours for the task.
- `description` (string): Task description / notes.
- `due_date` (string): Due date.
- `name` (string, required): Task name.
- `priority`: Priority: 25 low, 50 normal, 75 high, 100 critical.
- `project_id` (integer): Project to add the task to (used when tasklist_id is not given).
- `tasklist_id` (integer): Task list to add the task to.
- `users` (array): Assignee user ids.

### `paymo_update_task` (~194 tokens)

Update a task

Update a task — rename, re-describe, reassign (users replaces the whole list), set due date or priority, mark complete/incomplete, move to another task list or workflow status. Only the fields given are changed. Paymo: PUT /api/tasks/{id}.

Input parameters:

- `budget_hours` (number): New budget hours.
- `complete` (boolean): true = mark complete, false = reopen.
- `description` (string): New description.
- `due_date` (string): New due date.
- `name` (string): New name.
- `priority`: Priority: 25 low, 50 normal, 75 high, 100 critical.
- `status_id` (integer): Workflow status id.
- `task_id` (integer, required): The task id.
- `tasklist_id` (integer): Move to this task list.
- `users` (array): New FULL list of assignee user ids.

### `paymo_create_time_entry` (~171 tokens)

Log time

Log a completed time entry on a task, EITHER as date + duration_seconds OR as start_time + end_time (min 1 minute). To start a live timer use paymo_start_timer. Paymo: POST /api/entries.

Input parameters:

- `date` (string): Day of the entry (with duration_seconds).
- `description` (string): What was done.
- `duration_seconds` (integer): Length in seconds (with date), e.g. 3600 = 1h.
- `end_time` (string): End (with start_time).
- `start_time` (string): Start (with end_time).
- `task_id` (integer, required): Task the time is for.
- `user_id` (integer): User to log the time for (default: the API key's user).

### `paymo_update_time_entry` (~152 tokens)

Update a time entry

Edit a time entry: description, task, or its length. duration_seconds only applies to date+duration entries; for start/end entries change end_time instead. Paymo: PUT /api/entries/{id}.

Input parameters:

- `date` (string): New day (date+duration entries only).
- `description` (string): New description.
- `duration_seconds` (integer): New length in seconds (date+duration entries only).
- `end_time` (string): New end (start/end entries only).
- `entry_id` (integer, required): The time entry id.
- `start_time` (string): New start (start/end entries only).
- `task_id` (integer): Move the entry to this task.

### `paymo_start_timer` (~119 tokens)

Start a timer

Start a running timer on a task (a time entry with a start_time and no end_time). A user can have only one running timer; if one is running Paymo returns 409. Paymo: POST /api/entries.

Input parameters:

- `description` (string): What is being worked on.
- `start_time` (string): When the timer started (default: now).
- `task_id` (integer, required): Task to time.
- `user_id` (integer): User to start the timer for (default: the API key's user).

### `paymo_stop_timer` (~99 tokens)

Stop a timer

Stop a running timer by setting its end_time (default: now). The final duration must be at least 1 minute. Find running timers with paymo_list_time_entries running_only=true. Paymo: PUT /api/entries/{id}.

Input parameters:

- `description` (string): Final description.
- `end_time` (string): When the timer stopped (default: now).
- `entry_id` (integer, required): The running timer's time-entry id.

### `paymo_add_task_comment` (~69 tokens)

Comment on a task

Add a comment to a task's discussion thread (content may contain basic HTML). Read existing comments with paymo_get_task include=thread.comments. Paymo: POST /api/comments.

Input parameters:

- `content` (string, required): Comment text.
- `task_id` (integer, required): Task to comment on.

## Diagnostics

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

## Score history

- 2026-10-04: 77
- 2026-10-03: 77
- 2026-10-02: 76
- 2026-10-01: 76
- 2026-09-30: 71
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/paymo MCP server?

io.usefulapi/paymo is an MCP server listed in the public MCP registry as io.usefulapi/paymo. Browse Paymo projects, tasks, timesheets and invoices, and create tasks, log time or run timers. This page covers its hosted endpoint (https://paymo.usefulapi.io/mcp).

### Is the io.usefulapi/paymo MCP server safe to use?

io.usefulapi/paymo scores 77 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/paymo MCP server expose?

io.usefulapi/paymo exposes 21 tools: paymo_get_me, paymo_get_company, paymo_list_users, paymo_list_clients, paymo_list_projects, and 16 more. Their descriptions and schemas cost roughly 3,117 tokens of context every time the server is loaded.

### Does the io.usefulapi/paymo MCP server require authentication?

Yes. io.usefulapi/paymo 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/paymo MCP server still maintained?

io.usefulapi/paymo is still listed as active in the MCP registry. We last reached this channel on 4 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://paymo.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-paymo/paymo.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-paymo/paymo.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-paymo/paymo