SuiteDash MCP by usefulapi
REMOTE · SUITEDASH.USEFULAPI.IO
Read and update SuiteDash contacts, companies and projects; create leads and clients.
Available components
Last scanned (5 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & 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 Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2832 tokens (~177/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.2.0 → 1.2.3 functional
- 24 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 25 Oct 2026 · Probed https://suitedash.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 suitedash.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://suitedash.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://suitedash.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://suitedash.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://suitedash.usefulapi.io/mcp |
| Authorisation server | https://suitedash.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://suitedash.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/suitedash/ |
| http (plaintext) | http://suitedash.usefulapi.io/mcp | Inconclusive | 302 | http://suitedash.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 →
suitedash_create_company Create company ~107
WRITE: create a CRM company (name and role are required) with an optional primary contact. With create_primary_contact_if_not_exists the primary contact is created from the given names/email when no contact has that email. If send_welcome_email is true SuiteDash EMAILS the primary contact a portal invitation: leave it false unless the user asked. POST /company.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Company name. |
| primary_contact | object | – | – |
| role | string | yes | – |
No output schema declared.
No examples provided.
suitedash_create_contact Create contact ~304
WRITE: create a CRM contact in SuiteDash. role and names are required; email is required except for a Lead. Optionally link the contact to a company by name (set create_company_if_not_exists to create it). If send_welcome_email is true SuiteDash EMAILS the contact a portal access invitation: leave it false unless the user asked for that. POST /contact.
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | – | Postal address; only the parts you pass are sent. |
| background_info | string | – | – |
| company_name | string | – | Link the contact to the CRM company with this name. |
| create_company_if_not_exists | boolean | – | With company_name: create the company when none matches (default false). |
| custom_fields | object | – | Custom field values keyed by the custom field UID (from the *_fields tool); text/date as a string, numbers as numbers, multi-select as an array. |
| string | – | Primary email (required unless role is Lead). | |
| first_name | string | yes | First name. |
| last_name | string | yes | Last name. |
| name_prefix | string | – | – |
| phone | string | – | – |
| role | string | yes | – |
| send_welcome_email | boolean | – | Send the portal access invitation email to the contact (default false). |
| tags | array | – | Tags (replaces the record's tag list). |
| title | string | – | Job title. |
| website | string | – | – |
No output schema declared.
No examples provided.
suitedash_get_company Get company ~80
One CRM company by UID or exact name, with primary contact, category, tags, address and custom fields. GET /company/{identifier}.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | The company's UID or name. |
| meta | boolean | – | Also return the field schema (meta object) for each record. Rarely needed: use the *_fields tool instead. |
No output schema declared.
No examples provided.
suitedash_get_company_fields Get company field schema ~52
The company field schema of this account: every default and custom field (public, private and target custom fields under their UIDs) with type, required flag and the actions allowed. GET /company/meta.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
suitedash_get_contact Get contact ~79
One CRM contact by UID or primary email, with companies, tags, address and custom fields. GET /contact/{identifier}.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | The contact's UID or email address. |
| meta | boolean | – | Also return the field schema (meta object) for each record. Rarely needed: use the *_fields tool instead. |
No output schema declared.
No examples provided.
suitedash_get_contact_fields Get contact field schema ~64
The contact field schema of this account: every default and custom field with its type, whether it is required, and which actions (read/create/update) allow it. Custom fields appear under their UID: use these UIDs in custom_fields. GET /contact/meta.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
suitedash_get_project Get project ~157
One project with its description, client and secondary clients, teammates, team, leader, economics (estimated value, currency, sector) and custom fields. Find it by UID (default), exact name, a name fragment, or the most recent one. GET /project/{type}/{identifier}.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | – | The project UID, name or name fragment, per lookup. Not needed for most_recent. |
| lookup | string | – | How identifier is matched: uid (default), exact name, contains_the_following (name contains the text), or most_recent (identifier ignored). |
| meta | boolean | – | Also return the field schema (meta object) for each record. Rarely needed: use the *_fields tool instead. |
No output schema declared.
No examples provided.
suitedash_get_project_fields Get project field schema ~43
The project field schema of this account: default and custom fields (under their UIDs) with type, required flag and allowed actions. GET /project/meta.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
suitedash_list_companies List companies ~164
List CRM companies 10 per page (idle companies are not available): name, role, category, phones, website, address, tags, primary contact and custom fields. Filter by creation time and sort by name or creation date. GET /companies.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only companies created after this date-time (exclusive). |
| created_before | string | – | Only companies created before this date-time (exclusive). |
| meta | boolean | – | Also return the field schema (meta object) for each record. Rarely needed: use the *_fields tool instead. |
| order_by | string | – | – |
| page | integer | – | Page number, from 1 (default 1; 10 items per page). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
suitedash_list_contacts List contacts ~162
List CRM contacts (leads, prospects, clients) 10 per page: name, emails, phones, role, tags, companies, address and custom fields. Filter by creation time and sort by name or creation date. GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only contacts created after this date-time (exclusive). |
| created_before | string | – | Only contacts created before this date-time (exclusive). |
| meta | boolean | – | Also return the field schema (meta object) for each record. Rarely needed: use the *_fields tool instead. |
| order_by | string | – | – |
| page | integer | – | Page number, from 1 (default 1; 10 items per page). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
suitedash_list_projects List projects ~164
List projects 10 per page: name, status, start/end dates, due time. Filter by creation time and sort by name, creation, start or end date. Use suitedash_get_project for the client, team and economics. GET /projects.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only projects created after this date-time (exclusive). |
| created_before | string | – | Only projects created before this date-time (exclusive). |
| meta | boolean | – | Also return the field schema (meta object) for each record. Rarely needed: use the *_fields tool instead. |
| order_by | string | – | – |
| page | integer | – | Page number, from 1 (default 1; 10 items per page). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
suitedash_list_worlds List worlds ~87
List the account's Worlds (client groupings), 10 per page. Only available with the WORLDS Power-Up; otherwise SuiteDash answers 403. GET /worlds.
| Name | Type | Req | Description |
|---|---|---|---|
| order_by | string | – | – |
| page | integer | – | Page number, from 1 (default 1; 10 items per page). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
suitedash_subscribe_to_marketing Subscribe contacts to marketing audiences ~104
WRITE: subscribe people (by email) to one or more marketing audiences (numeric audience ids from SuiteDash > Marketing). Unknown emails may be created as marketing contacts. This enrolls real people in email marketing and can start campaigns or automations tied to those audiences: only do it for people who have consented, and only when the user asked. The reply holds the outcome per person. POST /marketing/subscribe.
| Name | Type | Req | Description |
|---|---|---|---|
| subscribers | array | yes | – |
No output schema declared.
No examples provided.
suitedash_update_company Update company ~274
WRITE: update fields of an existing CRM company (found by UID or name); only the fields you pass change, and null clears a field. Tags and custom fields passed here replace the current values. PUT /company/{identifier}.
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | – | Postal address; only the parts you pass are sent. |
| background_info | – | – | Background info (null clears it). |
| category | string | – | Company category name (must already exist). |
| home_phone | – | – | Home phone (null clears it). |
| identifier | string | yes | The company's UID or current name. |
| name | string | – | New company name. |
| phone | – | – | Phone (null clears it). |
| private_custom_fields | object | – | Custom field values keyed by the custom field UID (from the *_fields tool); text/date as a string, numbers as numbers, multi-select as an array. |
| public_custom_fields | object | – | Custom field values keyed by the custom field UID (from the *_fields tool); text/date as a string, numbers as numbers, multi-select as an array. |
| shop_phone | – | – | Shop phone (null clears it). |
| tags | array | – | Tags (replaces the record's tag list). |
| website | – | – | Website (null clears it). |
| work_phone | – | – | Work phone (null clears it). |
No output schema declared.
No examples provided.
suitedash_update_contact Update contact ~363
WRITE: update fields of an existing CRM contact (found by UID or email); only the fields you pass change, and null clears a field. Tags and custom fields passed here replace the current values. If send_welcome_email is true SuiteDash EMAILS the contact a portal invitation (only if none was sent before): leave it unset unless the user asked. PUT /contact/{identifier}.
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | – | Postal address; only the parts you pass are sent. |
| background_info | – | – | Background info (null clears it). |
| company_name | string | – | Link the contact to the CRM company with this name. |
| create_company_if_not_exists | boolean | – | With company_name: create the company when none matches (default false). |
| custom_fields | object | – | Custom field values keyed by the custom field UID (from the *_fields tool); text/date as a string, numbers as numbers, multi-select as an array. |
| string | – | New primary email. | |
| first_name | string | – | – |
| home_email | – | – | – |
| home_phone | – | – | Home phone (null clears it). |
| identifier | string | yes | The contact's UID or current email address. |
| last_name | string | – | – |
| name_prefix | string | – | – |
| phone | – | – | Primary phone (null clears it). |
| send_welcome_email | boolean | – | Send the portal invitation email if it was never sent. |
| shop_phone | – | – | Shop phone (null clears it). |
| tags | array | – | Tags (replaces the record's tag list). |
| title | – | – | Job title (null clears it). |
| website | – | – | Website (null clears it). |
| work_email | – | – | – |
| work_phone | – | – | Work phone (null clears it). |
No output schema declared.
No examples provided.
suitedash_update_project Update project ~353
WRITE: update fields of an existing project (found by UID, name, name fragment or most recent); only the fields you pass change. The status must be one of the account's project statuses (see suitedash_get_project_fields). The description and client text accept HTML. PUT /project/{type}/{identifier}.
| Name | Type | Req | Description |
|---|---|---|---|
| business_sector | – | – | Business sector name (must exist in Settings > Business Sectors) (null clears it). |
| due_time | – | – | Target time on the end date, HH:00 or HH:30. |
| end_date | – | – | Estimated completion date, yyyy-mm-dd (null clears). |
| estimated_value | – | – | Estimated project value. |
| estimated_value_currency | – | – | Currency name of the estimated value (must exist in the account) (null clears it). |
| identifier | string | – | The project UID, name or name fragment, per lookup. Not needed for most_recent. |
| info_description | – | – | Staff-only project information (HTML) (null clears it). |
| info_description_client | – | – | Client-visible project description (HTML) (null clears it). |
| info_title_client | – | – | Client-visible project title (null clears it). |
| lookup | string | – | How identifier is matched: uid (default), exact name, contains_the_following (name contains the text), or most_recent (identifier ignored). |
| name | string | – | New project name. |
| project_custom_fields | object | – | Custom field values keyed by the custom field UID (from the *_fields tool); text/date as a string, numbers as numbers, multi-select as an array. |
| start_date | – | – | yyyy-mm-dd (null clears). |
| status | string | – | Project status (one of Categories > Project Statuses). |
No output schema declared.
No examples provided.
How do I install the SuiteDash MCP by usefulapi server?
SuiteDash MCP by usefulapi is a hosted endpoint at https://suitedash.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 · suitedash.usefulapi.io
claude mcp add --transport http io-usefulapi-suitedash 'https://suitedash.usefulapi.io/mcp'
What is the SuiteDash MCP by usefulapi server?
SuiteDash MCP by usefulapi is listed in the public MCP registry as io.usefulapi/suitedash. Read and update SuiteDash contacts, companies and projects; create leads and clients. This page covers its hosted endpoint (https://suitedash.usefulapi.io/mcp).
Is the SuiteDash MCP by usefulapi server safe to use?
SuiteDash MCP by usefulapi scores 61 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 SuiteDash MCP by usefulapi server expose?
SuiteDash MCP by usefulapi exposes 16 tools: suitedash_list_contacts, suitedash_get_contact, suitedash_get_contact_fields, suitedash_create_contact, suitedash_update_contact, and 11 more. Their descriptions and schemas cost roughly 2,557 tokens of context every time the server is loaded.
Does the SuiteDash MCP by usefulapi server require authentication?
Yes. SuiteDash MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the SuiteDash MCP by usefulapi server still maintained?
SuiteDash MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.