DirectIQ
REMOTE · MCP.DIRECTIQ.COM
Manage DirectIQ contacts, lists and tags, see campaign results, and send transactional email.
Available components
Last scanned (8 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2699 tokens (~89/item across 30 items; 30 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 30 Oct 26 +13
- 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 security
- 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” functional
- “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” cosmetic
- 28 Oct 26 +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.
- 25 Oct 26 +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.
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 64
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 5 Nov 2026 · Probed https://mcp.directiq.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.directiq.com | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 3 Nov 2026 | 19 May 2027 | RSA 2048 | SHA256-RSA | 5929984093ce1ee03de0ff4243bef84 |
| SANs: *.directiq.com | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.directiq.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| directiq.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge ApiKey header="x-api-key"
ApiKey header="x-api-key" Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.directiq.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.directiq.com/mcp | HTTPS enforced | 301 | https://mcp.directiq.com:443/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 →
directiq_account_overview ~82
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
directiq_add_contact_to_list ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contactId | integer | yes | Numeric contact ID (from directiq_list_contacts or directiq_get_contact) |
| listId | integer | yes | Numeric list ID (from directiq_list_lists) |
No output schema declared.
No examples provided.
directiq_campaign_report ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | integer | yes | Numeric campaign ID (from directiq_list_campaigns) |
| 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 | yes | Which result to list |
No output schema declared.
No examples provided.
directiq_campaign_stats ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | integer | yes | Numeric campaign ID (from directiq_list_campaigns) |
No output schema declared.
No examples provided.
directiq_contact_count ~53
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
directiq_create_list ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | List name, 1–200 characters |
No output schema declared.
No examples provided.
directiq_create_tag ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Tag name |
No output schema declared.
No examples provided.
directiq_delete_contact ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric contact ID (from directiq_list_contacts or directiq_get_contact) |
No output schema declared.
No examples provided.
directiq_delete_list ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric list ID (from directiq_list_lists) |
No output schema declared.
No examples provided.
directiq_delete_tag ~55
Permanently delete a tag by ID and remove it from every contact. Contacts are kept. This cannot be undone; confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric tag ID (from directiq_list_tags) |
No output schema declared.
No examples provided.
directiq_get_campaign ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric campaign ID (from directiq_list_campaigns) |
No output schema declared.
No examples provided.
directiq_get_contact ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric contact ID (from directiq_list_contacts or directiq_get_contact) |
No output schema declared.
No examples provided.
directiq_get_list ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric list ID (from directiq_list_lists) |
No output schema declared.
No examples provided.
directiq_get_tag ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric tag ID (from directiq_list_tags) |
No output schema declared.
No examples provided.
directiq_list_campaigns ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| nextPageToken | string | – | Token from the previous page; omit for the first page |
No output schema declared.
No examples provided.
directiq_list_contacts ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pageNumber | integer | – | 1-based page number (default 1) |
| pageSize | integer | – | Results per page, 50–500 (default 50) |
No output schema declared.
No examples provided.
directiq_list_endpoints ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Optional case-insensitive filter matched against each operation path or summary |
No output schema declared.
No examples provided.
directiq_list_lists ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
directiq_list_segments ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
directiq_list_tags ~41
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
directiq_read_request ~152
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).
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | yes | DirectIQ API group: core, contacts, or subscription |
| path | string | yes | Endpoint path within the group, e.g. '/contact/list' or '/email/send' |
| query | object | – | Optional query parameters |
No output schema declared.
No examples provided.
directiq_remove_contact_from_list ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contactId | integer | yes | Numeric contact ID (from directiq_list_contacts or directiq_get_contact) |
| listId | integer | yes | Numeric list ID (from directiq_list_lists) |
No output schema declared.
No examples provided.
directiq_rename_list ~60
Rename a contact list by ID. Its contacts are unchanged; the previous name is overwritten.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric list ID (from directiq_list_lists) |
| name | string | yes | New name, 1–200 characters |
No output schema declared.
No examples provided.
directiq_rename_tag ~58
Rename a tag by ID. Contacts keep the tag under its new name; the previous name is overwritten.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Numeric tag ID (from directiq_list_tags) |
| name | string | yes | New tag name |
No output schema declared.
No examples provided.
directiq_send_email ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bcc | array | – | BCC recipient addresses |
| cc | array | – | CC recipient addresses |
| content | string | yes | Message body as HTML or plain text, at least 2 characters |
| from | string | yes | Sender address; must be a confirmed sender on the account |
| fromName | string | – | Sender display name, e.g. "Acme Support" |
| subject | string | yes | Subject line, at least 2 characters |
| to | string | yes | Recipient email address |
No output schema declared.
No examples provided.
directiq_tag_contact ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contactId | integer | yes | Numeric contact ID (from directiq_list_contacts or directiq_get_contact) |
| tags | array | yes | Tag names to apply |
No output schema declared.
No examples provided.
directiq_untag_contact ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Contact email address | |
| tag | string | yes | Tag name to remove |
No output schema declared.
No examples provided.
directiq_update_contact ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | yes | Contact fields to change, e.g. {"firstName": "Jamie"} |
| id | integer | yes | Numeric contact ID (from directiq_list_contacts or directiq_get_contact) |
No output schema declared.
No examples provided.
directiq_upsert_contact ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Contact email address | |
| firstName | string | – | First name; overwrites the existing value |
| lastName | string | – | Last name; overwrites the existing value |
| listId | integer | yes | Numeric list ID (from directiq_list_lists) |
| tags | array | – | Tag names to apply; missing tags are created |
No output schema declared.
No examples provided.
directiq_write_request ~194
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).
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | Optional JSON request body: an object, or an array for bulk operations |
| group | string | yes | DirectIQ API group: core, contacts, or subscription |
| method | string | yes | HTTP method |
| path | string | yes | Endpoint path within the group, e.g. '/contact/list' or '/email/send' |
| query | object | – | Optional query parameters |
No output schema declared.
No examples provided.
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.
remote · mcp.directiq.com
claude mcp add --transport http com-directiq-mcp-directiq 'https://mcp.directiq.com/mcp'
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.