Paymo MCP by usefulapi
REMOTE · PAYMO.USEFULAPI.IO
Browse Paymo projects, tasks, timesheets and invoices, and create tasks, log time or run timers.
Available components
Last scanned (23 hours ago)
Scores higher than 3% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Project Management
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 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.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 2 Nov 26 −61
- 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 “add_up_hours_logged_by_your_team” functional
- New prompt “check_unpaid_invoices_by_client” functional
- New prompt “create_or_update_a_task_and_add_a_comment” functional
- New prompt “find_overdue_tasks_and_who_has_them” functional
- New prompt “log_or_edit_time_or_start_and_stop_a_timer” functional
- New prompt “set_up_a_new_project_for_a_client” 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
- Stability: 0.97 → pass security
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 +1
- 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
- 26 Oct 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.
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 21 Nov 2026 · Probed https://paymo.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 | 11 Nov 2026 | 9 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 93e2fea3bbc31354138c8a47c5e87592 |
| 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 paymo.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | 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://paymo.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/paymo/ |
| http (plaintext) | http://paymo.usefulapi.io/mcp | Inconclusive | 302 | http://paymo.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 →
paymo_add_task_comment Comment on a task ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Comment text. |
| task_id | integer | yes | Task to comment on. |
No output schema declared.
No examples provided.
paymo_create_project Create a project ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Project name. |
| price_per_hour | number | – | Hourly rate for time & materials projects. |
| users | array | – | User ids to assign. |
No output schema declared.
No examples provided.
paymo_create_task Create a task ~174
Create a task in a task list (tasklist_id) or a project (project_id — goes to its 'Default Task List'). Paymo: POST /api/tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
paymo_create_time_entry Log time ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Task the time is for. |
| user_id | integer | – | User to log the time for (default: the API key's user). |
No output schema declared.
No examples provided.
paymo_get_company Get company info ~41
Fetch the company (account) info and settings: name, default currency, timezone, working days, invoice numbering. Paymo: GET /api/company.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
paymo_get_invoice Get an invoice ~73
Fetch one invoice with totals, and (by default) its line items and payments. Paymo: GET /api/invoices/{id}?include=invoiceitems,invoicepayments.
| Name | Type | Req | Description |
|---|---|---|---|
| include_items | boolean | – | Include line items and payments (default true). |
| invoice_id | integer | yes | The invoice id. |
No output schema declared.
No examples provided.
paymo_get_me Get the current user ~61
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
paymo_get_project Get a project ~88
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| include | string | – | Related objects to embed (Paymo `include`), comma-separated, e.g. client or tasklists.tasks. |
| project_id | integer | yes | The project id. |
No output schema declared.
No examples provided.
paymo_get_task Get a task ~89
Fetch one task, optionally with related objects: include=thread.comments for its comments, subtasks, entries (time logged), files, project. Paymo: GET /api/tasks/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| include | string | – | Related objects to embed (Paymo `include`), comma-separated, e.g. client or tasklists.tasks. |
| task_id | integer | yes | The task id. |
No output schema declared.
No examples provided.
paymo_list_clients List clients ~165
List clients (id, name, contact details, active flag). Paymo: GET /api/clients.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
paymo_list_expenses List expenses ~212
List expenses (id, client_id, project_id, user_id, amount, currency, date, notes, invoiced, tags). Paymo: GET /api/expenses.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
paymo_list_invoices List invoices ~155
List invoices (id, number, client_id, status, currency, date, due_date, subtotal, total). Paymo: GET /api/invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
paymo_list_projects List projects ~240
List projects (id, name, code, client_id, active, billable, budget_hours, users, managers), optionally filtered. Paymo: GET /api/projects.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
paymo_list_tasklists List task lists ~122
List task lists (id, name, project_id, milestone_id), e.g. to pick a tasklist_id when creating a task. Paymo: GET /api/tasklists.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
paymo_list_tasks List tasks ~263
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
paymo_list_time_entries List time entries ~324
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
paymo_list_users List users ~157
List users in the company (id, name, email, type, hourly rate, assigned/managed projects). Paymo: GET /api/users.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
paymo_start_timer Start a timer ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | What is being worked on. |
| start_time | string | – | When the timer started (default: now). |
| task_id | integer | yes | Task to time. |
| user_id | integer | – | User to start the timer for (default: the API key's user). |
No output schema declared.
No examples provided.
paymo_stop_timer Stop a timer ~99
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Final description. |
| end_time | string | – | When the timer stopped (default: now). |
| entry_id | integer | yes | The running timer's time-entry id. |
No output schema declared.
No examples provided.
paymo_update_task Update a task ~194
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The task id. |
| tasklist_id | integer | – | Move to this task list. |
| users | array | – | New FULL list of assignee user ids. |
No output schema declared.
No examples provided.
paymo_update_time_entry Update a time entry ~152
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The time entry id. |
| start_time | string | – | New start (start/end entries only). |
| task_id | integer | – | Move the entry to this task. |
No output schema declared.
No examples provided.
How do I install the Paymo MCP by usefulapi server?
Paymo MCP by usefulapi 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.
remote · paymo.usefulapi.io
claude mcp add --transport http io-usefulapi-paymo 'https://paymo.usefulapi.io/mcp'
What is the Paymo MCP by usefulapi server?
Paymo MCP by usefulapi is 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 Paymo MCP by usefulapi server safe to use?
Paymo 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 Paymo MCP by usefulapi server expose?
Paymo MCP by usefulapi 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 Paymo MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Paymo 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 Paymo MCP by usefulapi server still maintained?
Paymo MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Paymo MCP by usefulapi server?
VerifyMCP ran 4 checks on Paymo MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Paymo MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.