Plutio MCP by usefulapi
REMOTE · PLUTIO.USEFULAPI.IO
Manage Plutio clients, projects, tasks, time entries and invoices.
Available components
Last scanned (1 hour ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 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 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → 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
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “create_a_client_and_a_project” functional
- New prompt “prepare_a_draft_invoice_with_line_items” functional
- New prompt “read_a_proposal_or_contract” functional
- New prompt “record_time_against_a_task” functional
- New prompt “review_outstanding_invoices” functional
- New prompt “review_project_progress_and_overdue_tasks” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.6.0 → 1.8.0 functional
- Server version: 1.5.0 → 1.6.0 functional
- Server version: 1.4.2 → 1.5.0 functional
- 30 Oct 26 0
- Server version: 1.4.1 → 1.4.2 functional
- Server version: 1.4.0 → 1.4.1 functional
- 29 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.3.0 → 1.4.0 functional
- Server version: 1.2.0 → 1.3.0 functional
- 28 Oct 26 61
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 6 Nov 2026 · Probed https://plutio.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 plutio.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://plutio.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/plutio/ |
| http (plaintext) | http://plutio.usefulapi.io/mcp | Inconclusive | 302 | http://plutio.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 →
plutio_add_invoice_items Add invoice line items ~82
WRITE: put line items on an invoice that has none yet (an invoice made with plutio_create_invoice). Refuses an invoice that already has an items block. Plutio works out line totals, subtotal and total. POST /blocks.
| Name | Type | Req | Description |
|---|---|---|---|
| invoiceId | string | yes | The invoice _id. |
| items | array | yes | The invoice lines. |
No output schema declared.
No examples provided.
plutio_create_comment Comment on a task ~82
WRITE: post a comment on a task, file or conversation. Visible to everyone who can see that record. Returns the new record. POST /comments.
| Name | Type | Req | Description |
|---|---|---|---|
| bodyHTML | string | yes | The comment text as HTML. |
| entityId | string | yes | The _id of that record. |
| entityType | string | yes | Kind of record to comment on. |
No output schema declared.
No examples provided.
plutio_create_company Create company ~88
WRITE: add a company, optionally linking existing people to it. Returns the new record. POST /companies.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | Industry as Plutio's lowercase slug, e.g. design (a wrong value is rejected by Plutio). |
| personIds | array | – | _ids of existing people who work there. |
| title | string | yes | The company name. |
No output schema declared.
No examples provided.
plutio_create_event Create event ~83
WRITE: add a calendar event. No invitations are sent. Returns the new record. POST /events.
| Name | Type | Req | Description |
|---|---|---|---|
| descriptionHTML | string | – | – |
| endDate | string | – | End (ISO date-time). |
| isAllDay | boolean | – | – |
| startDate | string | yes | Start (ISO date-time). |
| title | string | yes | Event title. |
No output schema declared.
No examples provided.
plutio_create_invoice Create draft invoice ~130
WRITE: create a DRAFT invoice for a person or company. The client cannot pay it and nothing is emailed. Add line items with plutio_add_invoice_items. Returns the new record. POST /invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| clientId | string | yes | _id of the person or company to bill. |
| clientType | string | yes | Whether clientId is a person or a company. |
| currency | string | yes | Currency code, e.g. USD. |
| dueDate | string | – | Defaults to the due date in your invoice settings. |
| name | string | yes | A name for the invoice. |
No output schema declared.
No examples provided.
plutio_create_person Create person ~86
WRITE: add a person (a client by default) to the workspace. Returns the new record with its _id. POST /people.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email address. | |
| firstName | string | yes | First name. |
| lastName | string | – | Last name. |
| role | string | – | Role: client (default) or one of your team roles. |
No output schema declared.
No examples provided.
plutio_create_project Create project ~198
WRITE: create a project. Plutio gives it a default status and a first task board (find it with plutio_list_task_boards). Returns the new record. POST /projects.
| Name | Type | Req | Description |
|---|---|---|---|
| clientId | string | – | _id of the client (a person or company) the project belongs to. |
| clientType | string | – | Whether clientId is a person (default) or a company. |
| descriptionHTML | string | – | Description as HTML. |
| dueDate | string | – | An ISO 8601 date or date-time, e.g. 2026-12-31 or 2026-12-31T17:00:00Z. |
| name | string | yes | Project name. |
| startDate | string | – | An ISO 8601 date or date-time, e.g. 2026-12-31 or 2026-12-31T17:00:00Z. |
No output schema declared.
No examples provided.
plutio_create_task Create task ~165
WRITE: add a task to a project's task board. Get taskBoardId from plutio_list_task_boards (projectId filter). New tasks start as incomplete. Returns the new record. POST /tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| descriptionHTML | string | – | Description as HTML. |
| dueDate | string | – | An ISO 8601 date or date-time, e.g. 2026-12-31 or 2026-12-31T17:00:00Z. |
| projectId | string | yes | The project the task belongs to. |
| taskBoardId | string | yes | The task board inside that project. |
| taskGroupId | string | – | Optional task group (column) on the board. |
| title | string | yes | What the task is called. |
No output schema declared.
No examples provided.
plutio_get_document_blocks Get document blocks ~89
The content blocks of a contract, proposal or invoice: the written text (textHTML) and, for invoices, the line items. A document record only holds block ids. GET /blocks (entityType and entityId are both required).
| Name | Type | Req | Description |
|---|---|---|---|
| entityId | string | yes | The _id of the contract, proposal or invoice. |
| entityType | string | yes | What kind of document. |
No output schema declared.
No examples provided.
plutio_get_workspace Get workspace ~39
The Plutio workspace this API client is connected to: name, domain, currency, locale, timezone and settings. GET /businesses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plutio_list_categories List categories ~253
Categories used to organize records such as time entries and transactions. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /categories.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_comments List comments ~290
Comments on tasks, files and conversations: bodyHTML, createdBy, entityType, entityId. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /comments.
| Name | Type | Req | Description |
|---|---|---|---|
| entityId | string | – | Only comments on this record id. |
| entityType | string | – | Kind of record the comments belong to. |
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_companies List companies ~258
Companies (clients that group people): title, industry, people, contact details. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /companies.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_contracts List contracts ~265
Contracts: name, client, status, signatures. The text is in blocks: see plutio_get_document_blocks. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /contracts.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_conversations List conversations ~253
Inbox conversations: subject, participants, last message. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_custom_fields List custom fields ~257
Custom field definitions (label, type, which records they apply to). Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /custom-fields.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_events List events ~256
Calendar events: title, startDate, endDate, location, participants. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /events.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_files List files ~258
File records (name, size, folder, sharing). File contents are not downloaded. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /files.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_folders List folders ~247
File folders. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /file-folders.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_form_responses List form responses ~264
Submitted responses to forms. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /form-responses.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| formId | string | – | Only responses to this form id. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_forms List forms ~253
Forms (intake forms, questionnaires): name and status. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /forms.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_invoice_subscriptions List recurring invoices ~256
Recurring invoice subscriptions: client, schedule, amount. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /invoice-subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_invoices List invoices ~292
Invoices: name, client, status (draft, pending, paid and so on), amount, amountPaid, currency, dueDate, issueDate. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
| status | string | – | Invoice status, e.g. draft, pending, paid. |
No output schema declared.
No examples provided.
plutio_list_notes List notes ~260
Notes: title, descriptionHTML, entityType and entityId of the record they belong to. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /notes.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_people List people ~275
People: clients and your own team members (name, role, contactEmails, contactPhones, companies). Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /people.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| role | string | – | Role, e.g. client. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_projects List projects ~299
Projects: name, client, status, dates, budget, billing rate. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /projects.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
| statusId | string | – | Only projects with this status _id (see plutio_list_statuses). |
| statusTitle | string | – | Only projects whose status has this title, e.g. In progress. |
No output schema declared.
No examples provided.
plutio_list_proposals List proposals ~267
Proposals: name, client, status, amount. The text is in blocks: see plutio_get_document_blocks. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /proposals.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_schedulers List schedulers ~252
Scheduling pages (booking links) and their settings. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /scheduler.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_statuses List statuses ~258
Custom statuses (for projects and similar records): title, type, entityType. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /statuses.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_task_boards List task boards ~275
Task boards of projects. A project has one or more boards that hold tasks. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /task-boards.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| projectId | string | – | Only boards of this project id. |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_task_groups List task groups ~271
Task groups (columns/lists on a task board). Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /task-groups.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
| taskBoardId | string | – | Only groups of this task board id. |
No output schema declared.
No examples provided.
plutio_list_tasks List tasks ~322
Tasks: title, status (incomplete, completed, overdue), dueDate, assignedTo, projectId, taskBoardId. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| projectId | string | – | Only tasks of this project id. |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
| status | string | – | Task status. |
| taskBoardId | string | – | Only tasks of this task board id. |
| taskGroupId | string | – | Only tasks of this task group id. |
No output schema declared.
No examples provided.
plutio_list_time_entries List time entries ~313
Time entries: personId, projectId, taskId, startedAt, stoppedAt, time in seconds, billing amount and rate. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /time-tracks.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| personId | string | – | Only entries of this person id. |
| projectId | string | – | Only entries of this project id. |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
| taskId | string | – | Only entries of this task id. |
No output schema declared.
No examples provided.
plutio_list_transactions List transactions ~261
Payments and expenses: amount, currency, client, invoiceId, status, type, issueDate. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_list_wiki_pages List wiki pages ~256
Pages of the Plutio wiki / knowledge base. Returns { count, next_skip, items }; pass next_skip as skip for the next page. Pass id to read one record. Filter with exact-match fields or a MongoDB-style query. GET /wiki-entities.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | Exact-match filters on any record field, e.g. {"role":"client"} or {"projectId":"abc123"}. |
| id | string | – | Read just this record (its _id). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| query | string | – | A MongoDB-style query as a JSON object string, e.g. {"name.first":{"$regex":"^Tay","$options":"i"}} or {"dueDate":{"$lt":"2026-12-01"}}. Supports $regex, $in, $gte and the rest. |
| skip | integer | – | Records to step over, for paging. Pass the previous reply's next_skip. |
| sort | string | – | Sort as <field>_asc or <field>_desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). |
No output schema declared.
No examples provided.
plutio_log_time Log time ~143
WRITE: record a time entry against a task. projectId must be the task's own project (read the task first). time is the length in seconds (5400 = 1.5 hours). POST /time-tracks.
| Name | Type | Req | Description |
|---|---|---|---|
| personId | string | yes | Who did the work (a person _id). |
| projectId | string | yes | The task's own project. |
| startedAt | string | yes | When the work started (ISO date-time). |
| stoppedAt | string | yes | When it stopped (ISO date-time). |
| taskId | string | yes | The task the time was spent on. |
| time | integer | yes | Length in seconds. |
No output schema declared.
No examples provided.
plutio_update_task Update task ~128
WRITE: change a task's title, status (incomplete, completed, overdue), due date or description. Only the fields you pass change. Returns the updated record. PUT /tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| descriptionHTML | string | – | New description as HTML. |
| dueDate | string | – | An ISO 8601 date or date-time, e.g. 2026-12-31 or 2026-12-31T17:00:00Z. |
| id | string | yes | The task _id. |
| status | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
How do I install the Plutio MCP by usefulapi server?
Plutio MCP by usefulapi is a hosted endpoint at https://plutio.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 · plutio.usefulapi.io
claude mcp add --transport http io-usefulapi-plutio 'https://plutio.usefulapi.io/mcp'
What is the Plutio MCP by usefulapi server?
Plutio MCP by usefulapi is listed in the public MCP registry as io.usefulapi/plutio. Manage Plutio clients, projects, tasks, time entries and invoices. This page covers its hosted endpoint (https://plutio.usefulapi.io/mcp).
Is the Plutio MCP by usefulapi server safe to use?
Plutio 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 Plutio MCP by usefulapi server expose?
Plutio MCP by usefulapi exposes 37 tools: plutio_get_workspace, plutio_list_people, plutio_list_companies, plutio_list_projects, plutio_list_task_boards, and 32 more. Their descriptions and schemas cost roughly 8,024 tokens of context every time the server is loaded.
Does the Plutio MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Plutio 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 Plutio MCP by usefulapi server still maintained?
Plutio MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 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 Plutio MCP by usefulapi server?
VerifyMCP ran 4 checks on Plutio 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 Plutio 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.