Community Gmail server with auto-auth: search, read and send email via MCP.
Nothing to run from here
DirectIQ is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
15
tools declared
remote
at its publisher
—
calls last 7d
What it does
Manage DirectIQ contacts, lists and tags, see campaign results, and send transactional email.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http directiq-mcp https://mcp.directiq.com/mcp --header 'x-api-key: ${X_API_KEY}'
# 2 — ask your agent for something these tools do
# directiq_get_contact, directiq_list_contacts, directiq_contact_count and 12 more
It needs X_API_KEY (DirectIQ API key (Dashboard > Settings > API Keys)): this sends it in the x-api-key header from your environment, so export it first — its endpoint answers 401 without it.
DirectIQ costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DIAll 1 server
directiq1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads X_API_KEY (DirectIQ API key (Dashboard > Settings > API Keys)) from your environment each time it connects and sends it in the x-api-key header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx X_API_KEY … and open a new terminal (Windows).
claude mcp add --scope user --transport http directiq-mcp https://mcp.directiq.com/mcp --header 'x-api-key: ${X_API_KEY}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: x-api-key header — DirectIQ API key (Dashboard > Settings > API Keys). You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get a single contact by its numeric ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Numeric contact ID |
List contacts, optionally paginated.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number |
| pageSize | integer | no | Results per page (max 500) |
Get the total number of contacts in the account.
No parameter schema on file.
Update a contact by ID. Provide the fields to change (e.g. firstName, lastName, email).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Numeric contact ID |
| fields | object | yes | Object of contact fields to update |
List all contact lists.
No parameter schema on file.
Get a contact list by its numeric ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Numeric list ID |
Create a new contact list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | List name (max 200 characters) |
List all tags.
No parameter schema on file.
Get a tag by its numeric ID.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Numeric tag ID |
Create a new tag.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Tag name |
Send a transactional email.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | yes | Sender email address (must be a confirmed sender) |
| to | string | yes | Recipient email address |
| subject | string | yes | Email subject (min 2 characters) |
| content | string | yes | Email body (HTML or text, min 2 characters) |
| fromName | string | no | Sender display name |
| cc | array | no | CC recipients |
| bcc | array | no | BCC recipients |
Summarize the account: total contacts, active/disabled status counts, list count, tag count, and confirmed sender addresses. Individual sections degrade gracefully if unavailable.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Optional case-insensitive filter matched against each operation path or summary |
Issue an authenticated GET request to any DirectIQ endpoint. Use directiq_list_endpoints to discover GET operations (group, path) that have no dedicated tool. 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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 | no | Optional query parameters |
Issue an authenticated POST, PUT, PATCH, or DELETE request to any DirectIQ endpoint. May create, modify, or permanently delete account data. Use directiq_list_endpoints to discover operations (method, group, path) that have no dedicated tool. Full request/response schemas for each group are in the DirectIQ API docs at https://rest.directiq.com/{group}/swagger/index.html (core, contacts, subscripti
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 | no | Optional query parameters |
| body | no | Optional JSON request body: an object, or an array for bulk operations |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install DirectIQ or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 0.2.0 · scanned 30 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestadb49bcc12c74c0c7cce1bf66f143ee6a52734ee77ae4279b313b70c78afa599
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| directiq_get_contact | no tags | |
| directiq_list_contacts | no tags | |
| directiq_contact_count | no tags | |
| directiq_update_contact | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| directiq_list_lists | no tags | |
| directiq_get_list | no tags | |
| directiq_create_list | state-write | state-write: declares readOnlyHint: false |
| directiq_list_tags | no tags | |
| directiq_get_tag | no tags | |
| directiq_create_tag | state-write | state-write: declares readOnlyHint: false |
| directiq_send_email | external-sink | external-sink: keyword "send_email", declares readOnlyHint: false, openWorldHint: true |
| directiq_account_overview | no tags | |
| directiq_list_endpoints | no tags | |
| directiq_read_request | no tags | |
| directiq_write_request | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestadb49bcc12c74c0c
Scanned2026-10-30
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
0.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish DirectIQ can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.