iContact MCP by usefulapi
REMOTE · ICONTACT.USEFULAPI.IO
Read iContact contacts, lists, campaigns and message stats; add contacts and manage subscriptions.
Available components
Last scanned (4 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2065 tokens (~103/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
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.
- 25 Oct 26 60
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 25 Oct 2026 · Probed https://icontact.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of icontact.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://icontact.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://icontact.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://icontact.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://icontact.usefulapi.io/mcp |
| Authorisation server | https://icontact.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://icontact.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/icontact/ |
| http (plaintext) | http://icontact.usefulapi.io/mcp | Inconclusive | 302 | http://icontact.usefulapi.io/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 →
icontact_create_contact Create contact ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | – | Company name. |
| city | string | – | – |
| string | yes | 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 | – | – |
No output schema declared.
No examples provided.
icontact_get_account Get account ~53
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/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
icontact_get_campaign Get campaign ~36
One campaign by id. GET /campaigns/{campaignId}.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | integer | yes | iContact campaign id. |
No output schema declared.
No examples provided.
icontact_get_contact Get contact ~42
One contact by id. GET /contacts/{contactId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | iContact contact id (see icontact_list_contacts). |
No output schema declared.
No examples provided.
icontact_get_list Get mailing list ~36
One mailing list by id. GET /lists/{listId}.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | integer | yes | iContact list id. |
No output schema declared.
No examples provided.
icontact_get_message Get message ~42
One message by id, with subject and HTML/text bodies. GET /messages/{messageId}.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | integer | yes | iContact message id. |
No output schema declared.
No examples provided.
icontact_get_message_statistics Get message statistics ~56
Delivery statistics of a message (released, bounces, opens, clicks, unsubscribes, complaints, forwards). GET /messages/{messageId}/statistics.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | integer | yes | iContact message id. |
No output schema declared.
No examples provided.
icontact_get_segment Get segment ~35
One segment by id. GET /segments/{segmentId}.
| Name | Type | Req | Description |
|---|---|---|---|
| segment_id | integer | yes | iContact segment id. |
No output schema declared.
No examples provided.
icontact_get_send Get send ~36
One send by id. GET /sends/{sendId}.
| Name | Type | Req | Description |
|---|---|---|---|
| send_id | integer | yes | iContact send id. |
No output schema declared.
No examples provided.
icontact_list_campaigns List campaigns ~99
List campaigns (the sender identity and settings that messages belong to). GET /campaigns.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
icontact_list_contacts List contacts ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
icontact_list_custom_fields List custom fields ~70
List the account's custom contact fields (name, type). GET /customfields.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
icontact_list_lists List mailing lists ~99
List the account's mailing lists (name, description, welcome-message settings). GET /lists.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
icontact_list_message_activity List message activity ~116
Who opened, clicked, bounced from or unsubscribed after a message: one page of events for one message. GET /messages/{messageId}/opens | clicks | bounces | unsubscribes.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Which events to list. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| message_id | integer | yes | iContact message id. |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
icontact_list_messages List messages ~130
List messages (subject, type, campaign, create date, HTML and text bodies). Filter by type or campaign. GET /messages.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
icontact_list_segments List segments ~66
List saved segments (rule-based groups of contacts). GET /segments.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Records to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
icontact_list_sends List sends ~113
List sends (a message sent to lists/segments: send id, message id, included/excluded lists, scheduled time, status). GET /sends.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
icontact_list_subscriptions List subscriptions ~115
List list memberships (subscriptionId, contactId, listId, status). Filter by list, contact or status. GET /subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
icontact_set_subscription Subscribe or unsubscribe contact ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | iContact contact id. |
| list_id | integer | yes | iContact list id. |
| status | string | yes | normal = subscribed, pending = awaiting confirmation, unsubscribed. |
No output schema declared.
No examples provided.
icontact_update_contact Update contact ~177
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | – | Company name. |
| city | string | – | – |
| contact_id | integer | yes | iContact contact id. |
| 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 | – | – |
No output schema declared.
No examples provided.
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.
remote · icontact.usefulapi.io
claude mcp add --transport http io-usefulapi-icontact 'https://icontact.usefulapi.io/mcp'
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.