MailerLite MCP by usefulapi
REMOTE · MAILERLITE.USEFULAPI.IO
Read subscribers, groups, campaigns, fields, segments, automations, webhooks; safe additive writes.
Available components
Last scanned (3 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: 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.
- 2 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- Stability: 0.97 → pass security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_or_update_a_subscriber” functional
- New prompt “check_your_fields_segments_automations_and_webhooks” functional
- New prompt “create_a_group_and_add_subscribers_to_it” functional
- New prompt “find_subscribers_by_status_or_look_one_up” functional
- New prompt “review_your_campaigns_by_status” functional
- New prompt “see_your_groups_and_who_is_in_each_one” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 +1
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 −2
- Stability: pass → 0.87 functional
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 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 5 Nov 2026 · Probed https://mailerlite.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 mailerlite.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mailerlite.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/mailerlite/ |
| http (plaintext) | http://mailerlite.usefulapi.io/mcp | Inconclusive | 302 | http://mailerlite.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 →
mailerlite_assign_subscriber_to_group Assign subscriber to group ~63
Adds a subscriber to a group (additive membership). MailerLite API: POST /subscribers/{subscriber_id}/groups/{group_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | Group id. |
| subscriber_id | string | yes | Subscriber id. |
No output schema declared.
No examples provided.
mailerlite_create_group Create group ~41
Creates a subscriber group/list (additive). MailerLite API: POST /groups.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name of the new group. |
No output schema declared.
No examples provided.
mailerlite_get_campaign Get campaign ~44
Fetch a single campaign by id. Read-only. MailerLite API: GET /campaigns/{campaign_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | Campaign id. |
No output schema declared.
No examples provided.
mailerlite_get_subscriber Get subscriber ~46
Fetch a single subscriber by id or email address. MailerLite API: GET /subscribers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Subscriber id OR email address. |
No output schema declared.
No examples provided.
mailerlite_list_automations List automations ~87
List automations (workflows), optionally filtered by enabled state. Page-paginated. MailerLite API: GET /automations.
| Name | Type | Req | Description |
|---|---|---|---|
| filter_enabled | boolean | – | Filter by enabled state (→ filter[enabled]). |
| limit | integer | – | Max automations per page (default 25). |
| page | integer | – | Page number (page-based pagination). |
No output schema declared.
No examples provided.
mailerlite_list_campaigns List campaigns ~94
List campaigns, optionally filtered by status. Page-paginated. Read-only — this server does NOT send campaigns. MailerLite API: GET /campaigns.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max campaigns per page (default 25). |
| page | integer | – | Page number (page-based pagination). |
| status | string | – | Filter by status (→ filter[status]): sent | draft | ready. |
No output schema declared.
No examples provided.
mailerlite_list_fields List fields ~102
List custom/default subscriber fields, optionally filtered by type or keyword. Page-paginated. MailerLite API: GET /fields.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | – | Filter by keyword (→ filter[keyword]). |
| limit | integer | – | Max fields per page (default 25). |
| page | integer | – | Page number (page-based pagination). |
| type | string | – | Filter by field type (→ filter[type]): text | number | date. |
No output schema declared.
No examples provided.
mailerlite_list_group_subscribers List group subscribers ~107
List the subscribers belonging to a group, optionally filtered by status. Cursor-paginated. MailerLite API: GET /groups/{group_id}/subscribers.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous response's meta.next_cursor. |
| group_id | string | yes | Group id. |
| limit | integer | – | Max subscribers per page (default 25, max 100). |
| status | string | – | Filter by status (→ filter[status]). |
No output schema declared.
No examples provided.
mailerlite_list_groups List groups ~100
List subscriber groups/lists, optionally filtered by name. Page-paginated. MailerLite API: GET /groups.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max groups per page (default 25). |
| name | string | – | Filter by name (→ filter[name]). |
| page | integer | – | Page number (page-based pagination). |
| sort | string | – | Sort field, e.g. name, total, -total, created_at. |
No output schema declared.
No examples provided.
mailerlite_list_segments List segments ~56
List segments. Page-paginated. MailerLite API: GET /segments.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max segments per page (default 25). |
| page | integer | – | Page number (page-based pagination). |
No output schema declared.
No examples provided.
mailerlite_list_subscribers List subscribers ~100
List subscribers, optionally filtered by status. Cursor-paginated. MailerLite API: GET /subscribers.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous response's meta.next_cursor. |
| limit | integer | – | Max subscribers to return per page (default 25, max 100). |
| status | string | – | Filter by status (→ filter[status]): active | unsubscribed | unconfirmed | bounced | junk. |
No output schema declared.
No examples provided.
mailerlite_list_webhooks List webhooks ~61
List configured webhooks. Page-paginated. MailerLite API: GET /webhooks.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max webhooks per page (default 25). |
| page | integer | – | Page number (page-based pagination). |
No output schema declared.
No examples provided.
mailerlite_upsert_subscriber Upsert subscriber ~120
Creates or updates a subscriber (upsert by email). Additive — does NOT send any email. MailerLite API: POST /subscribers.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Subscriber email address (upsert key). | |
| fields | object | – | Custom/default field values keyed by field key, e.g. { name, last_name, company }. |
| groups | array | – | Group id strings to add the subscriber to. |
| status | string | – | Subscriber status: active | unsubscribed | unconfirmed | bounced | junk. |
No output schema declared.
No examples provided.
How do I install the MailerLite MCP by usefulapi server?
MailerLite MCP by usefulapi is a hosted endpoint at https://mailerlite.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 · mailerlite.usefulapi.io
claude mcp add --transport http io-usefulapi-mailerlite 'https://mailerlite.usefulapi.io/mcp'
What is the MailerLite MCP by usefulapi server?
MailerLite MCP by usefulapi is listed in the public MCP registry as io.usefulapi/mailerlite. Read subscribers, groups, campaigns, fields, segments, automations, webhooks; safe additive writes. This page covers its hosted endpoint (https://mailerlite.usefulapi.io/mcp).
Is the MailerLite MCP by usefulapi server safe to use?
MailerLite MCP by usefulapi scores 18 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 MailerLite MCP by usefulapi server expose?
MailerLite MCP by usefulapi exposes 13 tools: mailerlite_list_subscribers, mailerlite_get_subscriber, mailerlite_list_groups, mailerlite_list_group_subscribers, mailerlite_list_campaigns, and 8 more. Their descriptions and schemas cost roughly 1,021 tokens of context every time the server is loaded.
Does the MailerLite MCP by usefulapi server require authentication?
Its publisher declares no required credentials for MailerLite MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the MailerLite MCP by usefulapi server still maintained?
MailerLite MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.