# DirectIQ (remote · mcp.directiq.com)

Manage DirectIQ contacts, lists and tags, see campaign results, and send transactional email.

- Trust score: 82/100 (high trust)
- Change this week: +16
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.directiq.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-directiq-mcp-directiq/mcp.md), [page](https://verifymcp.io/servers/com-directiq-mcp-directiq/mcp)

## Channel facts

- Endpoint: `https://mcp.directiq.com/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `0.2.0`

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

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 2699 tokens (~89/item across 30 items; 30 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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.
  - All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the DirectIQ MCP server?

DirectIQ is a hosted endpoint at https://mcp.directiq.com/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 com-directiq-mcp-directiq 'https://mcp.directiq.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-directiq-mcp-directiq": {
      "url": "https://mcp.directiq.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-directiq-mcp-directiq": {
      "type": "http",
      "url": "https://mcp.directiq.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-directiq-mcp-directiq]
url = "https://mcp.directiq.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-directiq-mcp-directiq --url 'https://mcp.directiq.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-directiq-mcp-directiq:
    url: "https://mcp.directiq.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-directiq-mcp-directiq": {
      "Transport": "http",
      "Url": "https://mcp.directiq.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-directiq-mcp-directiq -t streamable-http -u 'https://mcp.directiq.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-directiq-mcp-directiq": {
      "type": "http",
      "url": "https://mcp.directiq.com/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-04 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 79, +13)

- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [security] New tool “directiq_delete_contact”, which the server declares destructive
- [security] New tool “directiq_delete_list”, which the server declares destructive
- [security] New tool “directiq_delete_tag”, which the server declares destructive
- [security] New tool “directiq_remove_contact_from_list”, which the server declares destructive
- [security] New tool “directiq_rename_list”, which the server declares destructive
- [security] New tool “directiq_rename_tag”, which the server declares destructive
- [security] New tool “directiq_untag_contact”, which the server declares destructive
- [security] New tool “directiq_upsert_contact”, which the server declares destructive
- [security] Tool “directiq_account_overview” rewrote its description, which is the text the model reads
- [security] Tool “directiq_contact_count” rewrote its description, which is the text the model reads
- [security] Tool “directiq_create_list” rewrote its description, which is the text the model reads
- [security] Tool “directiq_create_tag” rewrote its description, which is the text the model reads
- [security] Tool “directiq_get_contact” rewrote its description, which is the text the model reads
- [security] Tool “directiq_get_list” rewrote its description, which is the text the model reads
- [security] Tool “directiq_get_tag” rewrote its description, which is the text the model reads
- [security] Tool “directiq_list_contacts” rewrote its description, which is the text the model reads
- [security] Tool “directiq_list_lists” rewrote its description, which is the text the model reads
- [security] Tool “directiq_list_tags” rewrote its description, which is the text the model reads
- [security] Tool “directiq_read_request” rewrote its description, which is the text the model reads
- [security] Tool “directiq_send_email” rewrote its description, which is the text the model reads
- [security] Tool “directiq_update_contact” rewrote its description, which is the text the model reads
- [security] Tool “directiq_write_request” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 54 → 89
- [functional] Schema quality: good → excellent
- [functional] Server version: 0.1.0 → 0.2.0
- [functional] New tool “directiq_add_contact_to_list”
- [functional] New tool “directiq_campaign_report”
- [functional] New tool “directiq_campaign_stats”
- [functional] New tool “directiq_get_campaign”
- [functional] New tool “directiq_list_campaigns”
- [functional] New tool “directiq_list_segments”
- [functional] New tool “directiq_tag_contact”
- [cosmetic] “directiq_list_contacts” added an optional parameter “pageNumber”
- [cosmetic] “directiq_create_list” reworded the description of “name”
- [cosmetic] “directiq_get_contact” reworded the description of “id”
- [cosmetic] “directiq_get_list” reworded the description of “id”
- [cosmetic] “directiq_get_tag” reworded the description of “id”
- [cosmetic] “directiq_list_contacts” reworded the description of “pageSize”
- [cosmetic] “directiq_send_email” reworded the description of “bcc”
- [cosmetic] “directiq_send_email” reworded the description of “cc”
- [cosmetic] “directiq_send_email” reworded the description of “content”
- [cosmetic] “directiq_send_email” reworded the description of “from”
- [cosmetic] “directiq_send_email” reworded the description of “fromName”
- [cosmetic] “directiq_send_email” reworded the description of “subject”
- [cosmetic] “directiq_update_contact” reworded the description of “fields”
- [cosmetic] “directiq_update_contact” reworded the description of “id”
- [cosmetic] “directiq_list_contacts” dropped the optional parameter “page”

### 2026-10-28 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 64)

First indexed and scored.

## MCP tools (30)

### `directiq_account_overview` (~82 tokens)

Summarize the account in one call: total contacts, active/disabled status counts, list count, tag count, and confirmed sender addresses. A good first call in a conversation, and the way to find a valid "from" address for directiq_send_email. Each section that fails to load is returned as { error } without failing the rest.

### `directiq_get_contact` (~89 tokens)

Get one contact by numeric ID: email, first and last name, status, created and updated dates, tags, lists, and notes. Use when you already have the ID; to find a contact, page through directiq_list_contacts. Returns an error if no contact has that ID.

Input parameters:

- `id` (integer, required): Numeric contact ID (from directiq_list_contacts or directiq_get_contact)

### `directiq_list_contacts` (~122 tokens)

List contacts one page at a time, oldest first, with each contact's ID, email, name, status, tags, and lists. Returns { pageNumber, totalCount, result, hasNextPage }; request the next pageNumber while hasNextPage is true. Use to browse contacts or find an ID. For just the total, use directiq_contact_count instead.

Input parameters:

- `pageNumber` (integer): 1-based page number (default 1)
- `pageSize` (integer): Results per page, 50–500 (default 50)

### `directiq_contact_count` (~53 tokens)

Return the total number of contacts in the account as a single number. Use for a quick count; for counts plus active/disabled status, lists, tags, and senders, use directiq_account_overview.

### `directiq_upsert_contact` (~167 tokens)

Add a contact to a list, creating the contact if the email is new or updating its name if it already exists. Optionally applies tags (created if missing). Use this to create contacts; to change other fields on an existing contact, use directiq_update_contact. Returns import counts (inserted, alreadyExisting, addedToList); emails on a suppression or bounce list are counted but not added.

Input parameters:

- `email` (string, required): Contact email address
- `firstName` (string): First name; overwrites the existing value
- `lastName` (string): Last name; overwrites the existing value
- `listId` (integer, required): Numeric list ID (from directiq_list_lists)
- `tags` (array): Tag names to apply; missing tags are created

### `directiq_update_contact` (~112 tokens)

Update fields on an existing contact by ID, such as firstName, lastName, or email. Only the fields you pass change, and they overwrite the current values. To create a contact, use directiq_upsert_contact; to change list or tag membership, use the list and tag tools.

Input parameters:

- `fields` (object, required): Contact fields to change, e.g. {"firstName": "Jamie"}
- `id` (integer, required): Numeric contact ID (from directiq_list_contacts or directiq_get_contact)

### `directiq_delete_contact` (~75 tokens)

Permanently delete a contact by ID, removing it from every list and tag. This cannot be undone. Confirm with the user first; to only take a contact off one list, use directiq_remove_contact_from_list.

Input parameters:

- `id` (integer, required): Numeric contact ID (from directiq_list_contacts or directiq_get_contact)

### `directiq_list_lists` (~43 tokens)

List every contact list in the account with its ID and name. Use to find a list ID before adding contacts, sending campaigns, or calling directiq_get_list.

### `directiq_get_list` (~70 tokens)

Get one contact list by ID: name, created and modified dates, and total, active, and disabled contact counts. Use directiq_list_lists to find the ID. Returns an error if no list has that ID.

Input parameters:

- `id` (integer, required): Numeric list ID (from directiq_list_lists)

### `directiq_create_list` (~76 tokens)

Create a new, empty contact list and return it with its new ID. Calling it twice creates two lists with the same name, so check directiq_list_lists first. Add contacts afterwards with directiq_upsert_contact or directiq_add_contact_to_list.

Input parameters:

- `name` (string, required): List name, 1–200 characters

### `directiq_rename_list` (~60 tokens)

Rename a contact list by ID. Its contacts are unchanged; the previous name is overwritten.

Input parameters:

- `id` (integer, required): Numeric list ID (from directiq_list_lists)
- `name` (string, required): New name, 1–200 characters

### `directiq_delete_list` (~61 tokens)

Permanently delete a contact list by ID. The contacts themselves are kept, but their membership in this list is lost. This cannot be undone; confirm with the user first.

Input parameters:

- `id` (integer, required): Numeric list ID (from directiq_list_lists)

### `directiq_add_contact_to_list` (~95 tokens)

Add an existing contact (by contact ID) to a list. Adding a contact that is already on the list has no effect. To add someone by email who may not exist yet, use directiq_upsert_contact.

Input parameters:

- `contactId` (integer, required): Numeric contact ID (from directiq_list_contacts or directiq_get_contact)
- `listId` (integer, required): Numeric list ID (from directiq_list_lists)

### `directiq_remove_contact_from_list` (~82 tokens)

Remove a contact from one list. The contact stays in the account and on its other lists; to delete the contact entirely, use directiq_delete_contact.

Input parameters:

- `contactId` (integer, required): Numeric contact ID (from directiq_list_contacts or directiq_get_contact)
- `listId` (integer, required): Numeric list ID (from directiq_list_lists)

### `directiq_list_segments` (~46 tokens)

List saved segments (rule-based groups of contacts) with their IDs and names. Returns an empty array if the account has none. Segments are managed in the DirectIQ dashboard.

### `directiq_list_tags` (~41 tokens)

List every tag in the account with its ID and name. Use to check whether a tag exists or to find its ID before renaming or deleting it.

### `directiq_get_tag` (~57 tokens)

Get one tag by ID with its name and details. Use directiq_list_tags to find the ID. Returns an error if no tag has that ID.

Input parameters:

- `id` (integer, required): Numeric tag ID (from directiq_list_tags)

### `directiq_create_tag` (~57 tokens)

Create a new tag and return it with its ID. Check directiq_list_tags first to avoid duplicates. To tag a contact, use directiq_tag_contact, which also creates missing tags.

Input parameters:

- `name` (string, required): Tag name

### `directiq_rename_tag` (~58 tokens)

Rename a tag by ID. Contacts keep the tag under its new name; the previous name is overwritten.

Input parameters:

- `id` (integer, required): Numeric tag ID (from directiq_list_tags)
- `name` (string, required): New tag name

### `directiq_delete_tag` (~55 tokens)

Permanently delete a tag by ID and remove it from every contact. Contacts are kept. This cannot be undone; confirm with the user first.

Input parameters:

- `id` (integer, required): Numeric tag ID (from directiq_list_tags)

### `directiq_tag_contact` (~75 tokens)

Apply one or more tags to a contact by contact ID. Tags that do not exist yet are created. Applying a tag the contact already has has no effect.

Input parameters:

- `contactId` (integer, required): Numeric contact ID (from directiq_list_contacts or directiq_get_contact)
- `tags` (array, required): Tag names to apply

### `directiq_untag_contact` (~71 tokens)

Remove a tag from a contact, identified by the contact email and the tag name. The tag itself and the contact are kept; to delete the tag everywhere, use directiq_delete_tag.

Input parameters:

- `email` (string, required): Contact email address
- `tag` (string, required): Tag name to remove

### `directiq_list_campaigns` (~100 tokens)

List email campaigns and automation flows with ID, name, type (Regular or Flow), status, subject, sender, target lists, recipient count, and scheduled send time. Returns { campaigns, nextPageToken }; pass nextPageToken back to get the next page (null means no more). Use the IDs with directiq_campaign_stats for performance.

Input parameters:

- `nextPageToken` (string): Token from the previous page; omit for the first page

### `directiq_get_campaign` (~74 tokens)

Get one campaign by ID: name, type, status, subject, sender, target lists and segments, template ID, recipient count, and scheduled send time. For opens, clicks, and other results, use directiq_campaign_stats.

Input parameters:

- `id` (integer, required): Numeric campaign ID (from directiq_list_campaigns)

### `directiq_campaign_stats` (~97 tokens)

Summarize how a campaign performed: counts of recipients, opens, clicks, bounces, unsubscribes, and complaints, plus open, click, bounce, and unsubscribe rates as percentages of recipients. Use directiq_campaign_report to see which contacts did what. A section that fails to load is returned as an error without failing the rest.

Input parameters:

- `campaignId` (integer, required): Numeric campaign ID (from directiq_list_campaigns)

### `directiq_campaign_report` (~171 tokens)

List the contacts behind one campaign result, one page at a time: who received, opened, clicked, bounced, unsubscribed, or complained. Returns { totalCount, result }. Optionally filter to one email address, or for clicks, to one link. For totals and rates only, use directiq_campaign_stats.

Input parameters:

- `campaignId` (integer, required): Numeric campaign ID (from directiq_list_campaigns)
- `email` (string): Only return rows for this contact email
- `link` (string): For type "clicks" only: only return clicks on this URL
- `pageNumber` (integer): 1-based page number (default 1)
- `pageSize` (integer): Results per page, up to 500
- `type` (string, required): Which result to list

### `directiq_send_email` (~186 tokens)

Send one transactional email (a receipt, confirmation, or one-to-one message) immediately. It is delivered to real recipients and cannot be recalled, and it counts toward the account’s sending plan. The from address must be a confirmed sender on the account (see directiq_account_overview). Not for bulk marketing: campaigns are sent from the DirectIQ dashboard.

Input parameters:

- `bcc` (array): BCC recipient addresses
- `cc` (array): CC recipient addresses
- `content` (string, required): Message body as HTML or plain text, at least 2 characters
- `from` (string, required): Sender address; must be a confirmed sender on the account
- `fromName` (string): Sender display name, e.g. "Acme Support"
- `subject` (string, required): Subject line, at least 2 characters
- `to` (string, required): Recipient email address

### `directiq_list_endpoints` (~78 tokens)

List known DirectIQ API operations (HTTP method, API group, path, summary). Optionally filter by a search term. Call GET operations with directiq_read_request and POST/PUT/PATCH/DELETE operations with directiq_write_request.

Input parameters:

- `search` (string): Optional case-insensitive filter matched against each operation path or summary

### `directiq_read_request` (~152 tokens)

Issue an authenticated GET request to any DirectIQ endpoint and return the JSON response. Prefer a dedicated directiq_* tool when one exists; use this for read operations without one, found with directiq_list_endpoints (e.g. segments for a contact, email client reports). Full request/response schemas for each group are in the DirectIQ API docs at https://rest.directiq.com/{group}/swagger/index.html (core, contacts, subscription).

Input parameters:

- `group` (string, required): DirectIQ API group: core, contacts, or subscription
- `path` (string, required): Endpoint path within the group, e.g. '/contact/list' or '/email/send'
- `query` (object): Optional query parameters

### `directiq_write_request` (~194 tokens)

Issue an authenticated POST, PUT, PATCH, or DELETE request to any DirectIQ endpoint. May create, modify, or permanently delete account data, including bulk operations. Prefer a dedicated directiq_* tool when one exists; use this only for operations without one, found with directiq_list_endpoints, and confirm destructive calls with the user first. Full request/response schemas for each group are in the DirectIQ API docs at https://rest.directiq.com/{group}/swagger/index.html (core, contacts, subscription).

Input parameters:

- `body`: Optional JSON request body: an object, or an array for bulk operations
- `group` (string, required): DirectIQ API group: core, contacts, or subscription
- `method` (string, required): HTTP method
- `path` (string, required): Endpoint path within the group, e.g. '/contact/list' or '/email/send'
- `query` (object): Optional query parameters

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 66
- 2026-10-28: 66
- 2026-10-27: 65
- 2026-10-26: 65
- 2026-10-25: 65
- 2026-10-24: 64
- 2026-10-23: 64

## Common questions

### What is the DirectIQ MCP server?

DirectIQ is an MCP server listed in the public MCP registry as com.directiq.mcp/directiq. Manage DirectIQ contacts, lists and tags, see campaign results, and send transactional email. This page covers its hosted endpoint (https://mcp.directiq.com/mcp).

### Is the DirectIQ MCP server safe to use?

DirectIQ scores 82 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 DirectIQ MCP server expose?

DirectIQ exposes 30 tools: directiq_account_overview, directiq_get_contact, directiq_list_contacts, directiq_contact_count, directiq_upsert_contact, and 25 more. Their descriptions and schemas cost roughly 2,699 tokens of context every time the server is loaded.

### Does the DirectIQ MCP server require authentication?

Yes. DirectIQ 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 DirectIQ MCP server still maintained?

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

## Links

- Remote endpoint: https://mcp.directiq.com/mcp
- Authorisation metadata: https://mcp.directiq.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/directiq/mcp
- Website: https://www.directiq.com/mcp-setup/
- Changelog RSS feed: https://verifymcp.io/servers/com-directiq-mcp-directiq/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-directiq-mcp-directiq/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-directiq-mcp-directiq/mcp