io.usefulapi/paymo
REMOTE · PAYMO.USEFULAPI.IO · SCANNED OCT 4
Browse Paymo projects, tasks, timesheets and invoices, and create tasks, log time or run timers.
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 Security89
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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/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.
remote · paymo.usefulapi.io
claude mcp add --transport http io-usefulapi-paymo 'https://paymo.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-paymo": {
"url": "https://paymo.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-paymo": {
"type": "http",
"url": "https://paymo.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-paymo] url = "https://paymo.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-paymo": {
"type": "remote",
"url": "https://paymo.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-paymo --url 'https://paymo.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-paymo:
url: "https://paymo.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-paymo": {
"Transport": "http",
"Url": "https://paymo.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-paymo -t streamable-http -u 'https://paymo.usefulapi.io/mcp'
{
"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.
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.
- 3 Oct 26 +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.
- 2 Oct 26 0
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +53
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 29 Sept 26 18
First indexed and scored.
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 4 Oct 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 | 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 paymo.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://paymo.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://paymo.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://paymo.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://paymo.usefulapi.io/mcp |
| Authorisation server | https://paymo.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://paymo.usefulapi.io/mcp | HTTPS enforced | 301 | https://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.
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.