io.usefulapi/mailchimp

REMOTE · MAILCHIMP.USEFULAPI.IO · SCANNED AUG 3

Read audiences, members, campaigns and reports; add, update, tag and archive subscribers.

Available components

69 69 Trust /100

Trust breakdown (6 categories)

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 →

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 not yet verified: we couldn't determine whether a plaintext access path exists. 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 Usability74

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 Management3

Stability observed for 1 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

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mailchimp.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http io-usefulapi-mailchimp https://mailchimp.usefulapi.io/mcp

# ~/.codex/config.toml

[mcp_servers.io-usefulapi-mailchimp]
url = "https://mailchimp.usefulapi.io/mcp"

// opencode.json

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

# add to OpenClaw

openclaw mcp add io-usefulapi-mailchimp --url https://mailchimp.usefulapi.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-usefulapi-mailchimp:
    url: "https://mailchimp.usefulapi.io/mcp"

// mcp.json

{
  "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.

Changelog

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.

3 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
2 Aug 26 +51
- 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: excellent functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
1 Aug 26 18

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

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 3 Aug 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

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

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

MCP tools — 18 exposed · ~2,120 tokens

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.

Tool Tokens

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.

Input Output Examples

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).

Input Output Examples

Name	Type	Req	Description
email	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).

Input Output Examples

Name	Type	Req	Description
email	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 Output Examples

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}.

Input Output Examples

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}.

Input Output Examples

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}.

Input Output Examples

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).

Input Output Examples

Name	Type	Req	Description
email	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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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).

Input Output Examples

Name	Type	Req	Description
count	integer	—	Records to return (Mailchimp `count`; default 10, max 1000).
email	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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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).

Input Output Examples

Name	Type	Req	Description
email	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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

1 Aug 3 Aug