# SuiteDash MCP by usefulapi (remote · suitedash.usefulapi.io)

Read and update SuiteDash contacts, companies and projects; create leads and clients.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `suitedash.usefulapi.io`: 61/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-suitedash/suitedash.md), [page](https://verifymcp.io/servers/io-usefulapi-suitedash/suitedash)

## Channel facts

- Endpoint: `https://suitedash.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.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-10-25.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 81% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-suitedash 'https://suitedash.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-suitedash": {
      "url": "https://suitedash.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-suitedash": {
      "type": "http",
      "url": "https://suitedash.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-suitedash]
url = "https://suitedash.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-suitedash": {
      "type": "remote",
      "url": "https://suitedash.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-suitedash --url 'https://suitedash.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-suitedash:
    url: "https://suitedash.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-suitedash": {
      "Transport": "http",
      "Url": "https://suitedash.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-suitedash -t streamable-http -u 'https://suitedash.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-suitedash": {
      "type": "http",
      "url": "https://suitedash.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-10-25 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.2.0 → 1.2.3

### 2026-10-24 (score 61)

First indexed and scored.

## MCP tools (16)

### `suitedash_list_contacts` (~162 tokens)

List contacts

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.

Input parameters:

- `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.

### `suitedash_get_contact` (~79 tokens)

Get contact

One CRM contact by UID or primary email, with companies, tags, address and custom fields. GET /contact/{identifier}.

Input parameters:

- `identifier` (string, required): 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.

### `suitedash_get_contact_fields` (~64 tokens)

Get contact field schema

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.

### `suitedash_create_contact` (~304 tokens)

Create contact

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.

Input parameters:

- `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.
- `email` (string): Primary email (required unless role is Lead).
- `first_name` (string, required): First name.
- `last_name` (string, required): Last name.
- `name_prefix` (string)
- `phone` (string)
- `role` (string, required)
- `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)

### `suitedash_update_contact` (~363 tokens)

Update contact

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}.

Input parameters:

- `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.
- `email` (string): New primary email.
- `first_name` (string)
- `home_email`
- `home_phone`: Home phone (null clears it).
- `identifier` (string, required): 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).

### `suitedash_list_companies` (~164 tokens)

List companies

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.

Input parameters:

- `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.

### `suitedash_get_company` (~80 tokens)

Get company

One CRM company by UID or exact name, with primary contact, category, tags, address and custom fields. GET /company/{identifier}.

Input parameters:

- `identifier` (string, required): 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.

### `suitedash_get_company_fields` (~52 tokens)

Get company field schema

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.

### `suitedash_create_company` (~107 tokens)

Create company

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.

Input parameters:

- `name` (string, required): Company name.
- `primary_contact` (object)
- `role` (string, required)

### `suitedash_update_company` (~274 tokens)

Update company

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}.

Input parameters:

- `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, required): 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).

### `suitedash_list_projects` (~164 tokens)

List projects

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.

Input parameters:

- `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.

### `suitedash_get_project` (~157 tokens)

Get project

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}.

Input parameters:

- `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.

### `suitedash_get_project_fields` (~43 tokens)

Get project field schema

The project field schema of this account: default and custom fields (under their UIDs) with type, required flag and allowed actions. GET /project/meta.

### `suitedash_update_project` (~353 tokens)

Update project

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}.

Input parameters:

- `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).

### `suitedash_subscribe_to_marketing` (~104 tokens)

Subscribe contacts to marketing audiences

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.

Input parameters:

- `subscribers` (array, required)

### `suitedash_list_worlds` (~87 tokens)

List worlds

List the account's Worlds (client groupings), 10 per page. Only available with the WORLDS Power-Up; otherwise SuiteDash answers 403. GET /worlds.

Input parameters:

- `order_by` (string)
- `page` (integer): Page number, from 1 (default 1; 10 items per page). Pass the previous reply's next_page.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-suitedash/suitedash#diagnostics

## Score history

- 2026-10-25: 61
- 2026-10-24: 61

## Common questions

### 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.

## Links

- Remote endpoint: https://suitedash.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/suitedash/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-suitedash/suitedash.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-suitedash/suitedash.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-suitedash/suitedash