Skip to content

Paymo MCP by usefulapi

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

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

21 tools: 8 can delete or cancel things and 13 only read.

Tools: 8 delete, 0 irreversible, 0 write, 13 read.
  • Reads private data · 4
  • Reads text others write · 2
  • Can send data out · 1
  • No findings

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

Anlyon alternative

8 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 Paymo MCP by usefulapi can do

The Paymo MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 21 tools. It can delete or cancel things (8 tools: paymo_create_project, paymo_create_task, paymo_update_task, paymo_create_time_entry and 4 more). 13 tools only read.

4 tools read private data (paymo_list_users, paymo_list_clients, paymo_get_task and 1 more); 2 tools bring in text other people can write (paymo_list_users and paymo_get_task); 1 tool can send data out of your system (paymo_add_task_comment). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way 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.

21 tools

Deletes or cancels 8Claude Code: deny
  • paymo_add_task_commentAdd a comment to a task's discussion thread (content may contain basic HTML).Can send data outNo findings

    Why it is in this group

    • The name "paymo_add_task_comment" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "paymo_add_task_comment" says "add" and "comment": it writes something other people read.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Comment on a task
    • destructiveHint: true
  • paymo_create_projectCreate a project.No findings

    Why it is in this group

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

    Annotations the server declares

    • title: Create a project
    • destructiveHint: true
  • paymo_create_taskCreate a task in a task list (tasklist_id) or a project (project_id — goes to its 'Default Task List').No findings

    Why it is in this group

    • The name "paymo_create_task" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create a task in a task list (tasklist_id) or a project (project_id — goes to its 'Default Task List'). Paymo: POST /api/tasks.

    Annotations the server declares

    • title: Create a task
    • destructiveHint: true
  • paymo_create_time_entryLog a completed time entry on a task, EITHER as date + duration_seconds OR as start_time + end_time (min 1 minute).No findings

    Why it is in this group

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

    Annotations the server declares

    • title: Log time
    • destructiveHint: true
  • paymo_start_timerStart a running timer on a task (a time entry with a start_time and no end_time).No findings

    Why it is in this group

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

    Annotations the server declares

    • title: Start a timer
    • destructiveHint: true
  • paymo_stop_timerStop a running timer by setting its end_time (default: now).No findings

    Why it is in this group

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

    Annotations the server declares

    • title: Stop a timer
    • destructiveHint: true
  • paymo_update_taskUpdate 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.No findings

    Why it is in this group

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

    Annotations the server declares

    • title: Update a task
    • destructiveHint: true
  • paymo_update_time_entryEdit a time entry: description, task, or its length.No findings

    Why it is in this group

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

    Annotations the server declares

    • title: Update a time entry
    • destructiveHint: true
Only reads 13Show 13 read-only tools
  • paymo_get_companyFetch the company (account) info and settings: name, default currency, timezone, working days, invoice numbering.No findings

    Why it is in this group

    • The name "paymo_get_company" says "get": a word for reading.
    Description, as the server wrote it
    Fetch the company (account) info and settings: name, default currency, timezone, working days, invoice numbering. Paymo: GET /api/company.

    Annotations the server declares

    • title: Get company info
    • readOnlyHint: true
  • paymo_get_invoiceFetch one invoice with totals, and (by default) its line items and payments.No findings

    Why it is in this group

    • The name "paymo_get_invoice" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one invoice with totals, and (by default) its line items and payments. Paymo: GET /api/invoices/{id}?include=invoiceitems,invoicepayments.

    Annotations the server declares

    • title: Get an invoice
    • readOnlyHint: true
  • paymo_get_meFetch the Paymo user the API key belongs to (id, name, type, timezone).No findings

    Why it is in this group

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

    Annotations the server declares

    • title: Get the current user
    • readOnlyHint: true
  • paymo_get_projectFetch one project, optionally with related objects inline, e.g.No findings

    Why it is in this group

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

    Annotations the server declares

    • title: Get a project
    • readOnlyHint: true
  • paymo_get_taskFetch one task, optionally with related objects: include=thread.comments for its comments, subtasks, entries (time logged), files, project.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "paymo_get_task" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "thread": it reads messages.
    • untrusted-inputThe description's first sentence says "fetch" and "thread": it reads messages, which other people can write.
    Description, as the server wrote it
    Fetch one task, optionally with related objects: include=thread.comments for its comments, subtasks, entries (time logged), files, project. Paymo: GET /api/tasks/{id}.

    Annotations the server declares

    • title: Get a task
    • readOnlyHint: true
  • paymo_list_clientsList clients (id, name, contact details, active flag).Reads private dataNo findings

    Why it is in this group

    • The name "paymo_list_clients" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    List clients (id, name, contact details, active flag). Paymo: GET /api/clients.

    Annotations the server declares

    • title: List clients
    • readOnlyHint: true
  • paymo_list_expensesList expenses (id, client_id, project_id, user_id, amount, currency, date, notes, invoiced, tags).Reads private dataNo findings

    Why it is in this group

    • The name "paymo_list_expenses" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "note": it reads notes.
    Description, as the server wrote it
    List expenses (id, client_id, project_id, user_id, amount, currency, date, notes, invoiced, tags). Paymo: GET /api/expenses.

    Annotations the server declares

    • title: List expenses
    • readOnlyHint: true
  • paymo_list_invoicesList invoices (id, number, client_id, status, currency, date, due_date, subtotal, total).No findings

    Why it is in this group

    • The name "paymo_list_invoices" says "list": a word for reading.
    Description, as the server wrote it
    List invoices (id, number, client_id, status, currency, date, due_date, subtotal, total). Paymo: GET /api/invoices.

    Annotations the server declares

    • title: List invoices
    • readOnlyHint: true
  • paymo_list_projectsList projects (id, name, code, client_id, active, billable, budget_hours, users, managers), optionally filtered.No findings

    Why it is in this group

    • The name "paymo_list_projects" says "list": a word for reading.
    Description, as the server wrote it
    List projects (id, name, code, client_id, active, billable, budget_hours, users, managers), optionally filtered. Paymo: GET /api/projects.

    Annotations the server declares

    • title: List projects
    • readOnlyHint: true
  • paymo_list_tasklistsList task lists (id, name, project_id, milestone_id), e.g.No findings

    Why it is in this group

    • The name "paymo_list_tasklists" says "list": a word for reading.
    Description, as the server wrote it
    List task lists (id, name, project_id, milestone_id), e.g. to pick a tasklist_id when creating a task. Paymo: GET /api/tasklists.

    Annotations the server declares

    • title: List task lists
    • readOnlyHint: true
  • paymo_list_tasksList tasks (id, name, code, project_id, tasklist_id, complete, due_date, users, priority), filtered by project, task list, assignee or completion.No findings

    Why it is in this group

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

    Annotations the server declares

    • title: List tasks
    • readOnlyHint: true
  • paymo_list_time_entriesList time entries (id, task_id, user_id, project_id, start_time/end_time or date, duration in seconds, description, billed).No findings

    Why it is in this group

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

    Annotations the server declares

    • title: List time entries
    • readOnlyHint: true
  • paymo_list_usersList users in the company (id, name, email, type, hourly rate, assigned/managed projects).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "paymo_list_users" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    List users in the company (id, name, email, type, hourly rate, assigned/managed projects). Paymo: GET /api/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.

8 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__paymo__paymo_add_task_comment"
    ]
  }
}

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:37 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: 8 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://paymo.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://paymo.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: 8 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://paymo.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://paymo.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 paymo https://paymo.usefulapi.io/mcp
claude mcp add --transport http paymo https://paymo.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__paymo__paymo_get_me",
      "mcp__paymo__paymo_get_company",
      "mcp__paymo__paymo_list_users",
      "mcp__paymo__paymo_list_clients",
      "mcp__paymo__paymo_list_projects",
      "mcp__paymo__paymo_get_project",
      "mcp__paymo__paymo_list_tasklists",
      "mcp__paymo__paymo_list_tasks",
      "mcp__paymo__paymo_get_task",
      "mcp__paymo__paymo_list_time_entries",
      "mcp__paymo__paymo_list_invoices",
      "mcp__paymo__paymo_get_invoice",
      "mcp__paymo__paymo_list_expenses"
    ],
    "ask": [],
    "deny": [
      "mcp__paymo__paymo_create_project",
      "mcp__paymo__paymo_create_task",
      "mcp__paymo__paymo_update_task",
      "mcp__paymo__paymo_create_time_entry",
      "mcp__paymo__paymo_update_time_entry",
      "mcp__paymo__paymo_start_timer",
      "mcp__paymo__paymo_stop_timer",
      "mcp__paymo__paymo_add_task_comment"
    ]
  }
}

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 paymo. Review it before you use it.

Capability tags behind 5 rules
  • mcp__paymo__paymo_list_users private-data, untrusted-input
  • mcp__paymo__paymo_list_clients private-data
  • mcp__paymo__paymo_get_task private-data, untrusted-input
  • mcp__paymo__paymo_list_expenses private-data
  • mcp__paymo__paymo_add_task_comment outbound

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/paymo/verify?hash=6b9f47182a7da187d09150aa3497e9f8852992364e8ca92f2658c2477d6cf797" | jq -e '.changed == false'

Pinned hash 6b9f47182a7d, 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/paymo/changes.xml

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

Badge

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

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

Paymo MCP by usefulapi: questions and answers

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

Is the Paymo MCP by usefulapi safe?

No scan can promise that. What its definitions show: 21 tools, 8 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 Paymo MCP by usefulapi delete data?

Yes. 8 tools can delete, cancel or revoke something: paymo_create_project, paymo_create_task, paymo_update_task, paymo_create_time_entry, paymo_update_time_entry, paymo_start_timer and 2 more.

Can the Paymo 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 Paymo MCP by usefulapi have?

21 tools: 8 destructive, 13 read. paymo_create_project, paymo_create_task, paymo_update_task, paymo_create_time_entry, paymo_update_time_entry, paymo_start_timer, paymo_stop_timer, paymo_add_task_comment and 13 more.

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

Its remote endpoint did not answer the last anonymous look.

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

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): paymo_add_task_comment.

Has the Paymo MCP by usefulapi changed its tools?

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