Sellsy MCP by usefulapi
REMOTE · SELLSY.USEFULAPI.IO
Search and read Sellsy companies, contacts, opportunities, invoices and tasks; create records.
Available components
Last scanned (5 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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.
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.
- 2 Nov 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.23 → 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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 “add_a_company_individual_or_contact” functional
- New prompt “create_a_task_or_add_a_note_to_a_record” functional
- New prompt “create_an_opportunity_for_a_customer” functional
- New prompt “find_late_or_unpaid_invoices” functional
- New prompt “look_up_a_company_with_its_contacts_and_quotes” functional
- New prompt “review_open_opportunities_in_the_pipeline” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.8.0 → 1.10.0 functional
- Server version: 1.7.0 → 1.8.0 functional
- Server version: 1.6.2 → 1.7.0 functional
- 30 Oct 26 0
- Server version: 1.6.1 → 1.6.2 functional
- Server version: 1.6.0 → 1.6.1 functional
- 29 Oct 26 +1
- Server version: 1.5.0 → 1.6.0 functional
- Server version: 1.4.0 → 1.5.0 functional
- 28 Oct 26 0
- Server version: 1.2.0 → 1.4.0 functional
- 27 Oct 26 +1
- Server version: 1.1.0 → 1.2.0 functional
- 26 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
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 5 Nov 2026 · Probed https://sellsy.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 sellsy.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | 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://sellsy.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/sellsy/ |
| http (plaintext) | http://sellsy.usefulapi.io/mcp | Inconclusive | 302 | http://sellsy.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 →
sellsy_create_comment Add a comment (note) ~94
WRITE: add a comment (note) to a company, individual, contact, opportunity or document. Visible to the Sellsy staff, not sent to the customer. Needs comments.write.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | The comment text. |
| mentioned_staff_ids | array | – | Staff to notify. |
| related_id | integer | yes | Id of that record. |
| related_type | string | yes | What it is attached to. |
No output schema declared.
No examples provided.
sellsy_create_company Create a company ~135
WRITE: create a company record in Sellsy (a prospect, client or supplier). Needs companies.write. Nothing is sent to the company.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| main_activity_description | string | – | – |
| mobile_number | string | – | – |
| name | string | yes | Company name. |
| note | string | – | – |
| number_of_employees | integer | – | – |
| owner_id | integer | – | Staff id of the owner. |
| phone_number | string | – | – |
| reference | string | – | Your own reference. |
| type | string | yes | Relationship type. |
| website | string | – | – |
No output schema declared.
No examples provided.
sellsy_create_contact Create a contact ~116
WRITE: create a contact (a person) in Sellsy. It is not linked to a company by this call. Needs contacts.write.
| Name | Type | Req | Description |
|---|---|---|---|
| civility | string | – | – |
| string | – | – | |
| first_name | string | – | – |
| last_name | string | yes | Last name. |
| mobile_number | string | – | – |
| note | string | – | – |
| owner_id | integer | – | Staff id of the owner. |
| phone_number | string | – | – |
| position | string | – | Job title. |
No output schema declared.
No examples provided.
sellsy_create_individual Create an individual ~127
WRITE: create an individual (a private person as prospect, client or supplier) in Sellsy. Needs individuals.write.
| Name | Type | Req | Description |
|---|---|---|---|
| civility | string | – | – |
| string | – | – | |
| first_name | string | – | – |
| last_name | string | yes | Last name. |
| mobile_number | string | – | – |
| note | string | – | – |
| owner_id | integer | – | Staff id of the owner. |
| phone_number | string | – | – |
| reference | string | – | – |
| type | string | yes | Relationship type. |
| website | string | – | – |
No output schema declared.
No examples provided.
sellsy_create_opportunity Create an opportunity ~199
WRITE: create a sales opportunity linked to a company, individual or contact. Needs a pipeline id and one of its step ids (see sellsy_list_opportunity_pipelines and sellsy_list_pipeline_steps). Needs opportunities.write.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | Potential amount as a decimal string, e.g. "1500.00" (account currency). |
| assigned_staff_ids | array | – | – |
| contact_ids | array | – | – |
| due_date | string | – | Due date YYYY-MM-DD. |
| name | string | yes | Opportunity name. |
| note | string | – | – |
| owner_id | integer | – | Staff id of the owner (default: the API client's staff). |
| pipeline | integer | yes | Pipeline id. |
| probability | integer | – | – |
| related | array | yes | Who it is for: one company or one individual (required), plus optional contacts. |
| step | integer | yes | Step id inside that pipeline. |
No output schema declared.
No examples provided.
sellsy_create_task Create a task ~188
WRITE: create a task, optionally attached to a record and assigned to staff. Needs a label id (see sellsy_list_task_labels) and a due date-time. Needs tasks.write.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_staff_ids | array | – | – |
| description | string | – | – |
| due_date | string | yes | Due date and time, ISO 8601 with offset, e.g. 2026-11-03T09:00:00+01:00. |
| is_private | boolean | – | – |
| label_id | integer | yes | Task label id. |
| owner_id | integer | – | Staff id of the owner. |
| priority | integer | – | Priority level, 0 or 1. |
| related_id | integer | – | Id of that record. |
| related_type | string | – | Record the task is about (give related_id too). |
| title | string | – | – |
No output schema declared.
No examples provided.
sellsy_get_company Get a company ~99
Get one company by id. Needs companies.read.
| Name | Type | Req | Description |
|---|---|---|---|
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| id | integer | yes | Company id. |
No output schema declared.
No examples provided.
sellsy_get_contact Get a contact ~99
Get one contact by id. Needs contacts.read.
| Name | Type | Req | Description |
|---|---|---|---|
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| id | integer | yes | Contact id. |
No output schema declared.
No examples provided.
sellsy_get_credit_note Get a credit note ~104
Get one credit note by id. Needs credit-notes.read.
| Name | Type | Req | Description |
|---|---|---|---|
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| id | integer | yes | Credit note id. |
No output schema declared.
No examples provided.
sellsy_get_estimate Get an estimate ~106
Get one estimate by id, with its rows and amounts. Needs estimates.read.
| Name | Type | Req | Description |
|---|---|---|---|
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| id | integer | yes | Estimate id. |
No output schema declared.
No examples provided.
sellsy_get_individual Get an individual ~100
Get one individual by id. Needs individuals.read.
| Name | Type | Req | Description |
|---|---|---|---|
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| id | integer | yes | Individual id. |
No output schema declared.
No examples provided.
sellsy_get_invoice Get an invoice ~107
Get one invoice by id, with its rows, amounts and status. Needs invoices.read.
| Name | Type | Req | Description |
|---|---|---|---|
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| id | integer | yes | Invoice id. |
No output schema declared.
No examples provided.
sellsy_get_item Get an item ~100
Get one catalog item by id. Needs items.read.
| Name | Type | Req | Description |
|---|---|---|---|
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| id | integer | yes | Item id. |
No output schema declared.
No examples provided.
sellsy_get_opportunity Get an opportunity ~100
Get one opportunity by id. Needs opportunities.read.
| Name | Type | Req | Description |
|---|---|---|---|
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| id | integer | yes | Opportunity id. |
No output schema declared.
No examples provided.
sellsy_get_order Get an order ~99
Get one order by id. Needs orders.read.
| Name | Type | Req | Description |
|---|---|---|---|
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| id | integer | yes | Order id. |
No output schema declared.
No examples provided.
sellsy_get_task Get a task ~99
Get one task by id. Needs tasks.read.
| Name | Type | Req | Description |
|---|---|---|---|
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| id | integer | yes | Task id. |
No output schema declared.
No examples provided.
sellsy_list_companies List companies ~216
List companies (customers, prospects, suppliers) with paging. Needs companies.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: name, id, created_at, updated_at. |
No output schema declared.
No examples provided.
sellsy_list_company_contacts List a company's contacts ~132
List the contacts linked to one company (GET /companies/{id}/contacts). Needs companies.read and contacts.read.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | yes | Company id. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
No output schema declared.
No examples provided.
sellsy_list_contacts List contacts ~210
List contacts (people at companies) with paging. Needs contacts.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, name, created_at. |
No output schema declared.
No examples provided.
sellsy_list_credit_notes List credit notes ~212
List credit notes with paging. Needs credit-notes.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, number, created, date, amount. |
No output schema declared.
No examples provided.
sellsy_list_estimates List estimates ~217
List estimates (quotes) with paging. Needs estimates.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, numero, created, date, expiry_date, number, amount. |
No output schema declared.
No examples provided.
sellsy_list_individuals List individuals ~218
List individuals (private customers, prospects, suppliers) with paging. Needs individuals.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: name, id, created_at, updated_at. |
No output schema declared.
No examples provided.
sellsy_list_invoice_payments List an invoice's payments ~125
List the payments linked to one invoice. Needs invoices.read and payments.read.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | integer | yes | Invoice id. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
No output schema declared.
No examples provided.
sellsy_list_invoices List invoices ~212
List invoices with paging. Needs invoices.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, number, created, date, amount, due_date. |
No output schema declared.
No examples provided.
sellsy_list_items List items ~213
List catalog items (products, services, shipping, packaging) with paging. Needs items.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, created_at. |
No output schema declared.
No examples provided.
sellsy_list_opportunities List opportunities ~212
List sales opportunities with paging. Needs opportunities.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, created, step_rank, due_date, amount. |
No output schema declared.
No examples provided.
sellsy_list_opportunity_pipelines List opportunity pipelines ~122
List the sales pipelines (needed to create an opportunity: pipeline id and step id). Needs opportunities.read.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
No output schema declared.
No examples provided.
sellsy_list_orders List orders ~214
List orders with paging. Needs orders.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, number, created, date, amount, due_date, order_status. |
No output schema declared.
No examples provided.
sellsy_list_pipeline_steps List the steps of a pipeline ~121
List the steps of one opportunity pipeline. Needs opportunities.read.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| pipeline_id | integer | yes | Pipeline id. |
No output schema declared.
No examples provided.
sellsy_list_staffs List staff members ~220
List the staff members of the account (the list may hold only yourself, depending on the Sellsy plan). Needs staffs.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, name. |
No output schema declared.
No examples provided.
sellsy_list_task_labels List task labels ~118
List the task labels (a label id is required to create a task). Needs tasks.read.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
No output schema declared.
No examples provided.
sellsy_list_tasks List tasks ~203
List tasks with paging. Needs tasks.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, due_date. |
No output schema declared.
No examples provided.
sellsy_search Search across Sellsy ~134
Free-text search over companies, individuals, contacts, opportunities, items, documents and staff in one call (GET /search). Use it to find a record by name, email or number when you do not know its type. Needs the search.read scope.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | true = only archived records. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| q | string | yes | The text to search for. |
| type | array | – | Restrict to these object types or subtypes (e.g. company.client, document.invoice). Omit to search everything. |
No output schema declared.
No examples provided.
sellsy_search_comments Search comments (notes) ~287
Search comments and notes by author, date, parent comment or the company/individual/contact they are attached to. Needs comments.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| filters | object | – | Search filters as an object. Unknown keys are refused by Sellsy. Keys: owners [staff ids], companies [ids], individuals [ids], contacts [ids], parent_id, related_objects [{type,id}], created {start,e… |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, updated, created. |
No output schema declared.
No examples provided.
sellsy_search_companies Search companies ~341
Search companies by name, email, type (prospect/client/supplier), reference, VAT, SIRET, country, postal code, creation or update date. Needs companies.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| filters | object | – | Search filters as an object. Unknown keys are refused by Sellsy. Keys: name (exact), email (exact), type ("prospect"|"client"|"supplier" or an array), is_archived (bool), siret, vat, reference [..],… |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: name, id, created_at, updated_at. |
No output schema declared.
No examples provided.
sellsy_search_contacts Search contacts ~297
Search contacts by last name, email, phone, linked company or individual, creation date. Needs contacts.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| filters | object | – | Search filters as an object. Unknown keys are refused by Sellsy. Keys: last_name, email, phone_number, mobile_number, companies [company ids], individuals [individual ids], id [ids], is_linked (bool)… |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, name, created_at. |
No output schema declared.
No examples provided.
sellsy_search_estimates Search estimates ~356
Search estimates by status, number, date, currency, owner, contact or related company/individual/opportunity. Needs estimates.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| filters | object | – | Search filters as an object. Unknown keys are refused by Sellsy. Keys: status ["draft"|"sent"|"read"|"accepted"|"refused"|"expired"|"advanced"|"partialinvoiced"|"invoiced"|"cancelled"], number (exact… |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, numero, created, date, expiry_date, number, amount. |
No output schema declared.
No examples provided.
sellsy_search_individuals Search individuals ~312
Search individuals by name, email, type, reference, country, postal code, creation or update date. Needs individuals.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| filters | object | – | Search filters as an object. Unknown keys are refused by Sellsy. Keys: name (exact), email (exact), type ("prospect"|"client"|"supplier" or an array), is_archived (bool), reference [..], id [ids], co… |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: name, id, created_at, updated_at. |
No output schema declared.
No examples provided.
sellsy_search_invoices Search invoices ~371
Search invoices by status (draft/due/payinprogress/paid/late/cancelled), number, date, currency, owner, or related company/individual/opportunity. Use it for unpaid or late invoices. Needs invoices.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| filters | object | – | Search filters as an object. Unknown keys are refused by Sellsy. Keys: status ["draft"|"due"|"payinprogress"|"paid"|"late"|"cancelled"], number (exact), currency, date {start,end} dates YYYY-MM-DD, c… |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, number, created, date, amount, due_date. |
No output schema declared.
No examples provided.
sellsy_search_items Search items ~254
Search catalog items by name, reference or type. Needs items.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| filters | object | – | Search filters as an object. Unknown keys are refused by Sellsy. Keys: name, reference, type ["product"|"service"|"shipping"|"packaging"], is_archived (bool). |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, created_at. |
No output schema declared.
No examples provided.
sellsy_search_opportunities Search opportunities ~343
Search opportunities by name, number, pipeline, step, status (open/won/lost/cancelled/closed/late), amount, owner or due date. Needs opportunities.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| filters | object | – | Search filters as an object. Unknown keys are refused by Sellsy. Keys: name, number, pipeline [pipeline ids], step [step ids], statuses ["open"|"won"|"lost"|"cancelled"|"closed"|"late"], amount {min,… |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, created, step_rank, due_date, amount. |
No output schema declared.
No examples provided.
sellsy_search_orders Search orders ~315
Search orders by status or delivery status, or related company/individual/opportunity. Needs orders.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| filters | object | – | Search filters as an object. Unknown keys are refused by Sellsy. Keys: status ["draft"|"sent"|"read"|"accepted"|"expired"|"advanced"|"invoiced"|"partialinvoiced"|"cancelled"], order_status ["none"|"w… |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, number, created, date, amount, due_date, order_status. |
No output schema declared.
No examples provided.
sellsy_search_payments Search payments ~266
Search payments by status (pending/confirmed/rejected/failed/refund) or related company/individual. Needs payments.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| filters | object | – | Search filters as an object. Unknown keys are refused by Sellsy. Keys: status ["pending"|"confirmed"|"rejected"|"failed"|"refund"], related_objects [{type,id}]. |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, paid_date. |
No output schema declared.
No examples provided.
sellsy_search_tasks Search tasks ~313
Search tasks by status (todo/done), owner, assignee, label, due date or related record. Needs tasks.read.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Sort direction (default asc). |
| embed | array | – | Related objects to include (each may need an extra scope and is null without it), e.g. ["invoicing_address","main_contact","cf.1542"]. |
| field | array | – | Only return these fields, e.g. ["id","name"] or ["address.id"], to keep replies small. |
| filters | object | – | Search filters as an object. Unknown keys are refused by Sellsy. Keys: statuses ["todo"|"done"], owners [staff ids], assigned_staffs [staff ids], labels [label ids], priority {min,max} 0-1, companies… |
| limit | integer | – | Records per page, 1-100 (default 25). |
| offset | – | – | Paging cursor. Leave out for the first page. If the previous reply's pagination.offset is a string, pass it back unchanged for the next page. Only a number sets numeric paging: then pass the previous… |
| order | string | – | Sort field: id, due_date. |
No output schema declared.
No examples provided.
How do I install the Sellsy MCP by usefulapi server?
Sellsy MCP by usefulapi is a hosted endpoint at https://sellsy.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 · sellsy.usefulapi.io
claude mcp add --transport http io-usefulapi-sellsy 'https://sellsy.usefulapi.io/mcp'
What is the Sellsy MCP by usefulapi server?
Sellsy MCP by usefulapi is listed in the public MCP registry as io.usefulapi/sellsy. Search and read Sellsy companies, contacts, opportunities, invoices and tasks; create records. This page covers its hosted endpoint (https://sellsy.usefulapi.io/mcp).
Is the Sellsy MCP by usefulapi server safe to use?
Sellsy 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 Sellsy MCP by usefulapi server expose?
Sellsy MCP by usefulapi exposes 44 tools: sellsy_search, sellsy_list_companies, sellsy_search_companies, sellsy_get_company, sellsy_list_company_contacts, and 39 more. Their descriptions and schemas cost roughly 8,426 tokens of context every time the server is loaded.
Does the Sellsy MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Sellsy 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 Sellsy MCP by usefulapi server still maintained?
Sellsy MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.