# Plutio MCP by usefulapi (remote · plutio.usefulapi.io) Manage Plutio clients, projects, tasks, time entries and invoices. - Trust score: 18/100 (low) - Change this week: −44 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-06 ## Components - remote · `plutio.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-plutio/plutio.md), [page](https://verifymcp.io/servers/io-usefulapi-plutio/plutio) ## Channel facts - Endpoint: `https://plutio.usefulapi.io/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.10.3` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-06. - **Endpoint Security**: 46/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 0/100 - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. - **Schema Quality & AI Usability**: 0/100 - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. - **Stability & Change Management**: 0/100 - Stability not yet verified: not enough scan history yet (needs a 30-day window). - **Tool Coverage**: 0/100 - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. - **Tool Safety**: 0/100 - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. - **Capabilities**: 0/100 - Capabilities not yet verified: we couldn't read the endpoint's capabilities. **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. ## Install ### 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. ### Claude ```bash claude mcp add --transport http io-usefulapi-plutio 'https://plutio.usefulapi.io/mcp' ``` ### Cursor ```json { "mcpServers": { "io-usefulapi-plutio": { "url": "https://plutio.usefulapi.io/mcp" } } } ``` ### VS Code ```json { "servers": { "io-usefulapi-plutio": { "type": "http", "url": "https://plutio.usefulapi.io/mcp" } } } ``` ### Codex ```toml [mcp_servers.io-usefulapi-plutio] url = "https://plutio.usefulapi.io/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "io-usefulapi-plutio": { "type": "remote", "url": "https://plutio.usefulapi.io/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add io-usefulapi-plutio --url 'https://plutio.usefulapi.io/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: io-usefulapi-plutio: url: "https://plutio.usefulapi.io/mcp" ``` ### Netclaw ```json { "McpServers": { "io-usefulapi-plutio": { "Transport": "http", "Url": "https://plutio.usefulapi.io/mcp" } } } ``` ### Vellum ```bash assistant mcp add io-usefulapi-plutio -t streamable-http -u 'https://plutio.usefulapi.io/mcp' ``` ### Other ```json { "mcpServers": { "io-usefulapi-plutio": { "type": "http", "url": "https://plutio.usefulapi.io/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-06 (score 18, 0) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-11-02 (score 18, −48) - [security regression] Endpoint reachability: reachable → not serving MCP - [security regression] Stability: 0.13 → unverified - [security regression] Tool safety: pass → unverified - [security regression] Authorization: pass → unverified - [functional regression] Schema quality: 100 → unverified - [functional regression] Capabilities: pass → unverified - [functional regression] Tool coverage: 100 → unverified ### 2026-11-01 (score 66, +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. ### 2026-10-31 (score 65, +3) - [security improvement] Authorization: partial → pass - [functional improvement] 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 ### 2026-10-30 (score 62, 0) - [functional] Server version: 1.4.1 → 1.4.2 - [functional] Server version: 1.4.0 → 1.4.1 ### 2026-10-29 (score 62, +1) - [functional improvement] Stability: unverified → 0.03 - [functional] Server version: 1.3.0 → 1.4.0 - [functional] Server version: 1.2.0 → 1.3.0 ### 2026-10-28 (score 61) First indexed and scored. ## MCP tools (37) ### `plutio_get_workspace` (~39 tokens) Get workspace The Plutio workspace this API client is connected to: name, domain, currency, locale, timezone and settings. GET /businesses. ### `plutio_list_people` (~275 tokens) List people 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_companies` (~258 tokens) List companies 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_projects` (~299 tokens) List projects 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. Input parameters: - `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 _asc or _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. ### `plutio_list_task_boards` (~275 tokens) List task boards 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_task_groups` (~271 tokens) List task groups 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). - `taskBoardId` (string): Only groups of this task board id. ### `plutio_list_tasks` (~322 tokens) List tasks 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. Input parameters: - `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 _asc or _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. ### `plutio_list_statuses` (~258 tokens) List statuses 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_time_entries` (~313 tokens) List time entries 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). - `taskId` (string): Only entries of this task id. ### `plutio_list_categories` (~253 tokens) List categories 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_events` (~256 tokens) List events 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_schedulers` (~252 tokens) List schedulers 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_invoices` (~292 tokens) List invoices 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). - `status` (string): Invoice status, e.g. draft, pending, paid. ### `plutio_list_invoice_subscriptions` (~256 tokens) List recurring invoices 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_transactions` (~261 tokens) List transactions 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_proposals` (~267 tokens) List proposals 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_contracts` (~265 tokens) List contracts 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_forms` (~253 tokens) List forms 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_form_responses` (~264 tokens) List form responses 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_notes` (~260 tokens) List notes 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_comments` (~290 tokens) List comments 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_conversations` (~253 tokens) List conversations 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_wiki_pages` (~256 tokens) List wiki pages 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_files` (~258 tokens) List files 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_folders` (~247 tokens) List folders 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_list_custom_fields` (~257 tokens) List custom fields 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. Input parameters: - `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 _asc or _desc, e.g. createdAt_desc (most resources sort on createdAt and updatedAt). ### `plutio_get_document_blocks` (~89 tokens) Get document blocks 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). Input parameters: - `entityId` (string, required): The _id of the contract, proposal or invoice. - `entityType` (string, required): What kind of document. ### `plutio_create_person` (~86 tokens) Create person WRITE: add a person (a client by default) to the workspace. Returns the new record with its _id. POST /people. Input parameters: - `email` (string): Email address. - `firstName` (string, required): First name. - `lastName` (string): Last name. - `role` (string): Role: client (default) or one of your team roles. ### `plutio_create_company` (~88 tokens) Create company WRITE: add a company, optionally linking existing people to it. Returns the new record. POST /companies. Input parameters: - `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, required): The company name. ### `plutio_create_project` (~198 tokens) Create project 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. Input parameters: - `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, required): Project name. - `startDate` (string): An ISO 8601 date or date-time, e.g. 2026-12-31 or 2026-12-31T17:00:00Z. ### `plutio_create_task` (~165 tokens) Create task 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. Input parameters: - `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, required): The project the task belongs to. - `taskBoardId` (string, required): The task board inside that project. - `taskGroupId` (string): Optional task group (column) on the board. - `title` (string, required): What the task is called. ### `plutio_update_task` (~128 tokens) Update task 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. Input parameters: - `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, required): The task _id. - `status` (string) - `title` (string) ### `plutio_log_time` (~143 tokens) Log time 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. Input parameters: - `personId` (string, required): Who did the work (a person _id). - `projectId` (string, required): The task's own project. - `startedAt` (string, required): When the work started (ISO date-time). - `stoppedAt` (string, required): When it stopped (ISO date-time). - `taskId` (string, required): The task the time was spent on. - `time` (integer, required): Length in seconds. ### `plutio_create_comment` (~82 tokens) Comment on a task WRITE: post a comment on a task, file or conversation. Visible to everyone who can see that record. Returns the new record. POST /comments. Input parameters: - `bodyHTML` (string, required): The comment text as HTML. - `entityId` (string, required): The _id of that record. - `entityType` (string, required): Kind of record to comment on. ### `plutio_create_event` (~83 tokens) Create event WRITE: add a calendar event. No invitations are sent. Returns the new record. POST /events. Input parameters: - `descriptionHTML` (string) - `endDate` (string): End (ISO date-time). - `isAllDay` (boolean) - `startDate` (string, required): Start (ISO date-time). - `title` (string, required): Event title. ### `plutio_create_invoice` (~130 tokens) Create draft invoice 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. Input parameters: - `clientId` (string, required): _id of the person or company to bill. - `clientType` (string, required): Whether clientId is a person or a company. - `currency` (string, required): Currency code, e.g. USD. - `dueDate` (string): Defaults to the due date in your invoice settings. - `name` (string, required): A name for the invoice. ### `plutio_add_invoice_items` (~82 tokens) Add invoice line items 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. Input parameters: - `invoiceId` (string, required): The invoice _id. - `items` (array, required): The invoice lines. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-plutio/plutio#diagnostics ## Score history - 2026-11-06: 18 - 2026-11-05: 18 - 2026-11-04: 18 - 2026-11-03: 18 - 2026-11-02: 18 - 2026-11-01: 66 - 2026-10-31: 65 - 2026-10-30: 62 - 2026-10-29: 62 - 2026-10-28: 61 ## Common questions ### 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. ## Links - Remote endpoint: https://plutio.usefulapi.io/mcp - Repository: https://github.com/m190/usefulapi-mcp - Website: https://usefulapi.io/plutio/ - Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-plutio/plutio.xml - Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-plutio/plutio/changelog.json - Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-plutio/plutio.json - HTML version of this page: https://verifymcp.io/servers/io-usefulapi-plutio/plutio