# iContact MCP by usefulapi (remote · icontact.usefulapi.io)

Read iContact contacts, lists, campaigns and message stats; add contacts and manage subscriptions.

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

## Components

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

## Channel facts

- Endpoint: `https://icontact.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.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-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**: 83/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).
  - Tool/resource definitions use about 2065 tokens (~103/item across 20 items; 20 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "icontact_get_send" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 21 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the iContact MCP by usefulapi server?

iContact MCP by usefulapi is a hosted endpoint at https://icontact.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-icontact 'https://icontact.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-icontact": {
      "type": "http",
      "url": "https://icontact.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 60)

First indexed and scored.

## MCP tools (20)

### `icontact_get_account` (~53 tokens)

Get account

The iContact account behind the credentials (company name, address, plan fields) and its client folders, with the folder this server uses. GET /a/ and GET /a/{accountId}/c/.

### `icontact_list_contacts` (~213 tokens)

List contacts

List contacts (email, name, address, phone, status, create date). Filter by status, exact email, first/last name or a list the contact belongs to. GET /contacts.

Input parameters:

- `email` (string): Only the contact with this email address.
- `first_name` (string): Only contacts with this first name.
- `last_name` (string): Only contacts with this last name.
- `limit` (integer): Results per page, 1-100 (default 25).
- `list_id` (integer): Only contacts subscribed to this list id (see icontact_list_lists).
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Sort by a field of the resource, optionally with a direction, e.g. createDate:desc.
- `status` (string): Contact status; total = every contact, including those on no list (e.g. just created and not yet subscribed).

### `icontact_get_contact` (~42 tokens)

Get contact

One contact by id. GET /contacts/{contactId}.

Input parameters:

- `contact_id` (integer, required): iContact contact id (see icontact_list_contacts).

### `icontact_create_contact` (~178 tokens)

Create contact

WRITE: add one contact to the account (it is not added to any list; use icontact_set_subscription for that). Not idempotent: an email that already exists is reported by iContact as a warning. POST /contacts.

Input parameters:

- `business` (string): Company name.
- `city` (string)
- `email` (string, required): Email address.
- `fax` (string)
- `first_name` (string)
- `last_name` (string)
- `phone` (string)
- `postal_code` (string)
- `prefix` (string): Name prefix, e.g. Dr.
- `state` (string)
- `status` (string): Contact status (default normal).
- `street` (string)
- `street2` (string)
- `suffix` (string)

### `icontact_update_contact` (~177 tokens)

Update contact

WRITE: change fields of one contact; only the fields you pass are sent. Setting status to donotcontact or deleted stops mail to that contact. POST /contacts/{contactId}.

Input parameters:

- `business` (string): Company name.
- `city` (string)
- `contact_id` (integer, required): iContact contact id.
- `email` (string): New email address.
- `fax` (string)
- `first_name` (string)
- `last_name` (string)
- `phone` (string)
- `postal_code` (string)
- `prefix` (string): Name prefix, e.g. Dr.
- `state` (string)
- `status` (string): New contact status.
- `street` (string)
- `street2` (string)
- `suffix` (string)

### `icontact_list_lists` (~99 tokens)

List mailing lists

List the account's mailing lists (name, description, welcome-message settings). GET /lists.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Sort by a field of the resource, optionally with a direction, e.g. createDate:desc.

### `icontact_get_list` (~36 tokens)

Get mailing list

One mailing list by id. GET /lists/{listId}.

Input parameters:

- `list_id` (integer, required): iContact list id.

### `icontact_list_subscriptions` (~115 tokens)

List subscriptions

List list memberships (subscriptionId, contactId, listId, status). Filter by list, contact or status. GET /subscriptions.

Input parameters:

- `contact_id` (integer): Only subscriptions of this contact.
- `limit` (integer): Results per page, 1-100 (default 25).
- `list_id` (integer): Only subscriptions to this list.
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.
- `status` (string): Subscription status.

### `icontact_set_subscription` (~94 tokens)

Subscribe or unsubscribe contact

WRITE: put a contact on a list (status normal, or pending to start double opt-in) or unsubscribe it (status unsubscribed). Only for contacts who agreed to receive mail. POST /subscriptions.

Input parameters:

- `contact_id` (integer, required): iContact contact id.
- `list_id` (integer, required): iContact list id.
- `status` (string, required): normal = subscribed, pending = awaiting confirmation, unsubscribed.

### `icontact_list_campaigns` (~99 tokens)

List campaigns

List campaigns (the sender identity and settings that messages belong to). GET /campaigns.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Sort by a field of the resource, optionally with a direction, e.g. createDate:desc.

### `icontact_get_campaign` (~36 tokens)

Get campaign

One campaign by id. GET /campaigns/{campaignId}.

Input parameters:

- `campaign_id` (integer, required): iContact campaign id.

### `icontact_list_messages` (~130 tokens)

List messages

List messages (subject, type, campaign, create date, HTML and text bodies). Filter by type or campaign. GET /messages.

Input parameters:

- `campaign_id` (integer): Only messages of this campaign.
- `limit` (integer): Results per page, 1-100 (default 25).
- `message_type` (string): Message type.
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Sort by a field of the resource, optionally with a direction, e.g. createDate:desc.

### `icontact_get_message` (~42 tokens)

Get message

One message by id, with subject and HTML/text bodies. GET /messages/{messageId}.

Input parameters:

- `message_id` (integer, required): iContact message id.

### `icontact_get_message_statistics` (~56 tokens)

Get message statistics

Delivery statistics of a message (released, bounces, opens, clicks, unsubscribes, complaints, forwards). GET /messages/{messageId}/statistics.

Input parameters:

- `message_id` (integer, required): iContact message id.

### `icontact_list_message_activity` (~116 tokens)

List message activity

Who opened, clicked, bounced from or unsubscribed after a message: one page of events for one message. GET /messages/{messageId}/opens | clicks | bounces | unsubscribes.

Input parameters:

- `kind` (string, required): Which events to list.
- `limit` (integer): Results per page, 1-100 (default 25).
- `message_id` (integer, required): iContact message id.
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.

### `icontact_list_sends` (~113 tokens)

List sends

List sends (a message sent to lists/segments: send id, message id, included/excluded lists, scheduled time, status). GET /sends.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.
- `order_by` (string): Sort by a field of the resource, optionally with a direction, e.g. createDate:desc.

### `icontact_get_send` (~36 tokens)

Get send

One send by id. GET /sends/{sendId}.

Input parameters:

- `send_id` (integer, required): iContact send id.

### `icontact_list_segments` (~66 tokens)

List segments

List saved segments (rule-based groups of contacts). GET /segments.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.

### `icontact_get_segment` (~35 tokens)

Get segment

One segment by id. GET /segments/{segmentId}.

Input parameters:

- `segment_id` (integer, required): iContact segment id.

### `icontact_list_custom_fields` (~70 tokens)

List custom fields

List the account's custom contact fields (name, type). GET /customfields.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `offset` (integer): Records to skip (default 0). Pass the previous reply's next_offset.

## Diagnostics

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

## Score history

- 2026-10-25: 60

## Common questions

### What is the iContact MCP by usefulapi server?

iContact MCP by usefulapi is listed in the public MCP registry as io.usefulapi/icontact. Read iContact contacts, lists, campaigns and message stats; add contacts and manage subscriptions. This page covers its hosted endpoint (https://icontact.usefulapi.io/mcp).

### Is the iContact MCP by usefulapi server safe to use?

iContact MCP by usefulapi scores 60 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 iContact MCP by usefulapi server expose?

iContact MCP by usefulapi exposes 20 tools: icontact_get_account, icontact_list_contacts, icontact_get_contact, icontact_create_contact, icontact_update_contact, and 15 more. Their descriptions and schemas cost roughly 1,806 tokens of context every time the server is loaded.

### Does the iContact MCP by usefulapi server require authentication?

Yes. iContact 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 iContact MCP by usefulapi server still maintained?

iContact 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://icontact.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/icontact/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-icontact/icontact.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-icontact/icontact.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-icontact/icontact