Mailchimp (AlexlaGuardia) MCP Server

mcp-mailchimp PyPI v0.3.0

Published by alexlaguardia — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
93/100
Last scanned
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable
inspection depth (source) — how much of the target the scan could see

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([list_files]) and tools that can send data out ([create_webhook, delete_webhook, upload_file]) are exposed together. An agent can move private data to the sink.

Evidence: sources [list_files] → sinks [create_webhook, delete_webhook, upload_file]

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow list_files → create_webhook

Tools 71

Show each tool and what it can reach · statically extracted from the published source
  • create_webhooknetwork egress
  • delete_webhooknetwork egress
  • list_filesreads sensitive data
  • upload_filenetwork egress
  • add_member_noteno sensitive capability
  • add_or_update_memberno sensitive capability
  • archive_memberno sensitive capability
  • batch_subscribe_membersno sensitive capability
  • cancel_campaignno sensitive capability
  • create_audienceno sensitive capability
  • create_batch_operationno sensitive capability
  • create_campaignno sensitive capability
  • create_merge_fieldno sensitive capability
  • create_segmentno sensitive capability
  • create_templateno sensitive capability
  • delete_campaignno sensitive capability
  • delete_member_permanentno sensitive capability
  • delete_segmentno sensitive capability
  • delete_templateno sensitive capability
  • get_ab_test_resultsno sensitive capability
  • get_audienceno sensitive capability
  • get_audience_growthno sensitive capability
  • get_audience_locationsno sensitive capability
  • get_automationno sensitive capability
  • get_campaignno sensitive capability
  • get_campaign_contentno sensitive capability
  • get_campaign_reportno sensitive capability
  • get_click_reportno sensitive capability
  • get_ecommerce_customerno sensitive capability
  • get_email_client_statsno sensitive capability
  • get_landing_pageno sensitive capability
  • get_memberno sensitive capability
  • get_member_activityno sensitive capability
  • get_open_reportno sensitive capability
  • get_segment_membersno sensitive capability
  • get_sent_to_reportno sensitive capability
  • get_templateno sensitive capability
  • get_unsubscribe_reportno sensitive capability
  • list_audiencesno sensitive capability
  • list_automation_emailsno sensitive capability
  • list_automationsno sensitive capability
  • list_campaignsno sensitive capability
  • list_ecommerce_storesno sensitive capability
  • list_interest_categoriesno sensitive capability
  • list_interestsno sensitive capability
  • list_landing_pagesno sensitive capability
  • list_member_notesno sensitive capability
  • list_membersno sensitive capability
  • list_merge_fieldsno sensitive capability
  • list_segmentsno sensitive capability
  • list_store_cartsno sensitive capability
  • list_store_ordersno sensitive capability
  • list_store_productsno sensitive capability
  • list_store_promo_codesno sensitive capability
  • list_tagsno sensitive capability
  • list_templatesno sensitive capability
  • list_webhooksno sensitive capability
  • manage_member_tagsno sensitive capability
  • pause_automationno sensitive capability
  • pingno sensitive capability
  • replicate_campaignno sensitive capability
  • schedule_campaignno sensitive capability
  • search_membersno sensitive capability
  • send_campaignno sensitive capability
  • send_test_emailno sensitive capability
  • set_campaign_contentno sensitive capability
  • start_automationno sensitive capability
  • unschedule_campaignno sensitive capability
  • update_audienceno sensitive capability
  • update_campaignno sensitive capability
  • update_segmentno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.3.0 latest A 93/100 1 1.8.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-mailchimp/badge.svg)](https://mcptrustchecker.com/registry/mcp-mailchimp)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-mailchimp"><img src="https://mcptrustchecker.com/registry/mcp-mailchimp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-mailchimp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-mailchimp --online --registry pypi

Use the free API → How scoring works

Other implementations of Mailchimp 7

Independent packages implementing the same tool, scanned with the same engine. Compare all 8 side by side →

More in Business & CRM