io.usefulapi/mailchimp
REMOTE · MAILCHIMP.USEFULAPI.IO · SCANNED SEP 20
Read audiences, members, campaigns and reports; add, update, tag and archive subscribers.
Available components
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 answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2120 tokens (~117/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 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
How do I install the io.usefulapi/mailchimp MCP server?
io.usefulapi/mailchimp is a hosted endpoint at https://mailchimp.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 · mailchimp.usefulapi.io
claude mcp add --transport http io-usefulapi-mailchimp 'https://mailchimp.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-mailchimp": {
"url": "https://mailchimp.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-mailchimp": {
"type": "http",
"url": "https://mailchimp.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-mailchimp] url = "https://mailchimp.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-mailchimp": {
"type": "remote",
"url": "https://mailchimp.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-mailchimp --url 'https://mailchimp.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-mailchimp:
url: "https://mailchimp.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-mailchimp": {
"Transport": "http",
"Url": "https://mailchimp.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-mailchimp -t streamable-http -u 'https://mailchimp.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-mailchimp": {
"type": "http",
"url": "https://mailchimp.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 1 Sept 26 +1
- Stability: 0.97 → pass security
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Aug 26 0
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
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 20 Sept 2026 · Probed https://mailchimp.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 | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 9b41aabf7f27e1e513f62e72d6c36fb3 |
| SANs: usefulapi.io, mailchimp.usefulapi.io, *.mailchimp.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 mailchimp.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 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 | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://mailchimp.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://mailchimp.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://mailchimp.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mailchimp.usefulapi.io/mcp |
| Authorisation server | https://mailchimp.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mailchimp.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://mailchimp.usefulapi.io/mcp | Inconclusive | 401 |
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 →
mailchimp_add_member Add member ~155
Add a new member (subscriber) to an audience (list). Note: status "pending" triggers a double-opt-in confirmation email. REST: POST /lists/{list_id}/members.
| Name | Type | Req | Description |
|---|---|---|---|
| email_address | string | yes | The member's email address (required). |
| list_id | string | yes | The audience (list) id to add the member to. |
| merge_fields | object | – | Merge-field values, e.g. { FNAME: "Ada", LNAME: "Lovelace" }. |
| status | string | – | Subscription status (default "subscribed"; "pending" sends a double-opt-in email). |
| tags | array | – | Array of tag-name strings to apply to the new member. |
No output schema declared.
No examples provided.
mailchimp_add_member_tags Add/remove member tags ~191
Add and/or remove tags on an audience member (by email or subscriber_hash). `tags` are added (status active); `removeTags` are removed (status inactive). Mailchimp returns HTTP 204 (no body). REST: POST /lists/{list_id}/members/{subscriber_hash}/tags (email → MD5 hash).
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Member email address — MD5-hashed (lowercased) into the subscriber_hash for you. | |
| list_id | string | yes | The audience (list) id. |
| removeTags | array | – | Tag names to REMOVE from the member (mapped to status "inactive"). |
| subscriberHash | string | – | The subscriber_hash (MD5 of lowercased email) or contact id, if you have it instead of `email`. |
| tags | array | – | Tag names to ADD to the member (mapped to status "active"). |
No output schema declared.
No examples provided.
mailchimp_archive_member Archive member ~130
Archive (soft-remove) an audience member — reversible; this is NOT the permanent-delete action. REST: DELETE /lists/{list_id}/members/{subscriber_hash} (email → MD5 hash). Returns HTTP 204 (no body).
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Member email address — MD5-hashed (lowercased) into the subscriber_hash for you. | |
| list_id | string | yes | The audience (list) id. |
| subscriberHash | string | – | The subscriber_hash (MD5 of lowercased email) or contact id, if you have it instead of `email`. |
No output schema declared.
No examples provided.
mailchimp_get_account Get account ~40
Get the API Root — the authenticated Mailchimp account: account name, total subscribers, contact info, plan and industry stats. REST: GET /.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mailchimp_get_audience Get audience (list) ~55
Get a single audience (list) by id, including subscriber stats, default from-name/email and settings. REST: GET /lists/{list_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The audience (list) id. |
No output schema declared.
No examples provided.
mailchimp_get_campaign Get campaign ~47
Get a single campaign by id, including its settings, recipients and send status. REST: GET /campaigns/{campaign_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign id. |
No output schema declared.
No examples provided.
mailchimp_get_campaign_report Get campaign report ~59
Get the report for one campaign — opens, clicks, bounces, unsubscribes and other engagement summary stats. REST: GET /reports/{campaign_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign id to fetch the report for. |
No output schema declared.
No examples provided.
mailchimp_get_member Get member ~127
Get a single audience member (subscriber) by email or subscriber_hash, including status, merge fields, tags and stats. REST: GET /lists/{list_id}/members/{subscriber_hash} (email → MD5 hash).
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Member email address — MD5-hashed (lowercased) into the subscriber_hash for you. | |
| list_id | string | yes | The audience (list) id. |
| subscriberHash | string | – | The subscriber_hash (MD5 of lowercased email) or contact id, if you have it instead of `email`. |
No output schema declared.
No examples provided.
mailchimp_list_audiences List audiences (lists) ~138
List the account's audiences — Mailchimp's `/lists` resource (an audience is a list of subscribers). Paginated, with optional sort. REST: GET /lists.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Records to return (Mailchimp `count`; default 10, max 1000). |
| offset | integer | – | Number of records to skip (Mailchimp `offset`, for pagination). |
| sortDir | string | – | Sort direction ASC/DESC (Mailchimp `sort_dir`). |
| sortField | string | – | Field to sort by (Mailchimp `sort_field`, e.g. date_created / create_time). |
No output schema declared.
No examples provided.
mailchimp_list_automations List automations ~79
List the account's classic automations (automated email workflows). Paginated. REST: GET /automations.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Records to return (Mailchimp `count`; default 10, max 1000). |
| offset | integer | – | Number of records to skip (Mailchimp `offset`, for pagination). |
No output schema declared.
No examples provided.
mailchimp_list_campaigns List campaigns ~185
List the account's campaigns (email sends). Paginated, with optional type/status/audience filters and sort. REST: GET /campaigns.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Records to return (Mailchimp `count`; default 10, max 1000). |
| list_id | string | – | Restrict to campaigns sent to this audience (list) id. |
| offset | integer | – | Number of records to skip (Mailchimp `offset`, for pagination). |
| sortDir | string | – | Sort direction ASC/DESC (Mailchimp `sort_dir`). |
| sortField | string | – | Field to sort by (Mailchimp `sort_field`, e.g. date_created / create_time). |
| status | string | – | Filter by campaign status (Mailchimp `status`). |
| type | string | – | Filter by campaign type (Mailchimp `type`). |
No output schema declared.
No examples provided.
mailchimp_list_member_tags List member tags ~168
List the tags applied to a single audience member (by email or subscriber_hash). Paginated. REST: GET /lists/{list_id}/members/{subscriber_hash}/tags (email → MD5 hash).
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Records to return (Mailchimp `count`; default 10, max 1000). |
| string | – | Member email address — MD5-hashed (lowercased) into the subscriber_hash for you. | |
| list_id | string | yes | The audience (list) id. |
| offset | integer | – | Number of records to skip (Mailchimp `offset`, for pagination). |
| subscriberHash | string | – | The subscriber_hash (MD5 of lowercased email) or contact id, if you have it instead of `email`. |
No output schema declared.
No examples provided.
mailchimp_list_members List members ~166
List members of an audience (list). Paginated, with an optional status filter and sort. REST: GET /lists/{list_id}/members.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Records to return (Mailchimp `count`; default 10, max 1000). |
| list_id | string | yes | The audience (list) id to list members from. |
| offset | integer | – | Number of records to skip (Mailchimp `offset`, for pagination). |
| sortDir | string | – | Sort direction ASC/DESC (Mailchimp `sort_dir`). |
| sortField | string | – | Field to sort by (Mailchimp `sort_field`, e.g. date_created / create_time). |
| status | string | – | Filter by member status (Mailchimp `status`). |
No output schema declared.
No examples provided.
mailchimp_list_reports List reports ~97
List campaign reports (aggregate performance for sent campaigns). Paginated, with an optional type filter. REST: GET /reports.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Records to return (Mailchimp `count`; default 10, max 1000). |
| offset | integer | – | Number of records to skip (Mailchimp `offset`, for pagination). |
| type | string | – | Filter reports by campaign type (Mailchimp `type`). |
No output schema declared.
No examples provided.
mailchimp_list_segments List segments ~96
List an audience's segments and tags (saved segments include static tags). Paginated. REST: GET /lists/{list_id}/segments.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Records to return (Mailchimp `count`; default 10, max 1000). |
| list_id | string | yes | The audience (list) id. |
| offset | integer | – | Number of records to skip (Mailchimp `offset`, for pagination). |
No output schema declared.
No examples provided.
mailchimp_list_templates List templates ~152
List the account's email templates (saved and pre-built layouts). Paginated, with optional type filter and sort. REST: GET /templates.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Records to return (Mailchimp `count`; default 10, max 1000). |
| offset | integer | – | Number of records to skip (Mailchimp `offset`, for pagination). |
| sortDir | string | – | Sort direction ASC/DESC (Mailchimp `sort_dir`). |
| sortField | string | – | Field to sort by (Mailchimp `sort_field`, e.g. date_created / create_time). |
| type | string | – | Filter by template type (Mailchimp `type`: user / base / gallery). |
No output schema declared.
No examples provided.
mailchimp_search_members Search members ~78
Search for members across the account (or one audience) by email, name or other fields. Returns exact + full-text matches. REST: GET /search-members.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | – | Restrict the search to this audience (list) id. |
| query | string | yes | The search query (email, name, etc.). |
No output schema declared.
No examples provided.
mailchimp_update_member Update member ~157
Update an existing audience member (by email or subscriber_hash). Only the fields you supply change. REST: PATCH /lists/{list_id}/members/{subscriber_hash} (email → MD5 hash).
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Member email address — MD5-hashed (lowercased) into the subscriber_hash for you. | |
| list_id | string | yes | The audience (list) id. |
| merge_fields | object | – | Merge-field values to set, e.g. { FNAME: "Ada" }. |
| status | string | – | New subscription status. |
| subscriberHash | string | – | The subscriber_hash (MD5 of lowercased email) or contact id, if you have it instead of `email`. |
No output schema declared.
No examples provided.
What is the io.usefulapi/mailchimp MCP server?
io.usefulapi/mailchimp is an MCP server listed in the public MCP registry as io.usefulapi/mailchimp. Read audiences, members, campaigns and reports; add, update, tag and archive subscribers. This page covers its hosted endpoint (https://mailchimp.usefulapi.io/mcp).
Is the io.usefulapi/mailchimp MCP server safe to use?
io.usefulapi/mailchimp scores 86 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 io.usefulapi/mailchimp MCP server expose?
io.usefulapi/mailchimp exposes 18 tools: mailchimp_get_account, mailchimp_list_audiences, mailchimp_get_audience, mailchimp_list_members, mailchimp_get_member, and 13 more. Their descriptions and schemas cost roughly 2,120 tokens of context every time the server is loaded.
Does the io.usefulapi/mailchimp MCP server require authentication?
Yes. io.usefulapi/mailchimp 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 io.usefulapi/mailchimp MCP server still maintained?
io.usefulapi/mailchimp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.