Laposta MCP by usefulapi
REMOTE · LAPOSTA.USEFULAPI.IO
Read Laposta lists, members, campaigns and reports; add members and build campaigns.
Available components
Last scanned (8 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 −50
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “compare_the_results_of_recent_newsletters” functional
- New prompt “count_subscribers_on_each_mailing_list” functional
- New prompt “prepare_a_newsletter_draft_and_send_a_test” functional
- New prompt “review_a_campaign_before_it_goes_out” functional
- New prompt “see_what_one_subscriber_has_done” functional
- New prompt “subscribe_or_unsubscribe_people” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.7.0 → 1.9.0 functional
- Server version: 1.6.0 → 1.7.0 functional
- Server version: 1.5.2 → 1.6.0 functional
- 30 Oct 26 0
- Server version: 1.5.1 → 1.5.2 functional
- Server version: 1.5.0 → 1.5.1 functional
- 29 Oct 26 +1
- Server version: 1.4.0 → 1.5.0 functional
- Server version: 1.3.0 → 1.4.0 functional
- 28 Oct 26 0
- Server version: 1.1.0 → 1.3.0 functional
- 27 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- 26 Oct 26 62
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 5 Nov 2026 · Probed https://laposta.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 laposta.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://laposta.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/laposta/ |
| http (plaintext) | http://laposta.usefulapi.io/mcp | Inconclusive | 302 | http://laposta.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 →
laposta_add_member Add a member to a list ~251
WRITE: add one email address to a mailing list (subscribe). On a double opt-in list Laposta sends the confirmation email to that address. The address must have given consent. With upsert, an existing active member's fields are overwritten; an unsubscribed member is re-activated unless suppress_reactivation is set.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_fields | object | – | Custom field values keyed by the field's custom_name (the variable name shown by laposta_list_fields). Multi-choice fields take an array of option values. |
| string | yes | – | |
| ip | string | yes | IP address the signup came from (required by Laposta; use the signup source's address, or your own server's if it was entered by staff). |
| list_id | string | yes | The list id (from laposta_list_lists). |
| source_url | string | – | URL the signup came from. |
| suppress_email_notification | boolean | – | Do not send the list's signup notification email. |
| suppress_reactivation | boolean | – | With upsert: do not re-activate an unsubscribed member. |
| upsert | boolean | – | Overwrite the fields if the address is already an active member (default false: error). |
No output schema declared.
No examples provided.
laposta_create_campaign Create a campaign draft ~174
WRITE: create a new regular campaign (a draft: it is NOT filled, scheduled or sent). Fill it with laposta_set_campaign_content, check it with laposta_send_test_email and send it in the Laposta app. The from_email must be an approved sender address of the account.
| Name | Type | Req | Description |
|---|---|---|---|
| from_email | string | yes | Sender email address (must be an approved sender in Laposta). |
| from_name | string | yes | Sender name. |
| google_analytics | boolean | – | Link Google Analytics tracking. |
| list_ids | array | yes | Recipients: list ids and optionally segment ids. |
| name | string | yes | Internal campaign name. |
| previewtext | string | – | Preview text (max 120 characters). |
| reply_to | string | – | Reply-to address. |
| subject | string | yes | Subject line. |
No output schema declared.
No examples provided.
laposta_get_campaign Get a campaign ~53
Get one campaign: name, subject, preview text, sender, reply-to, recipients, delivery moments and web version URL.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign id (from laposta_list_campaigns). |
No output schema declared.
No examples provided.
laposta_get_campaign_content Get a campaign's content ~75
Get the plain-text content of a campaign (and its import_url if it was imported). Set include_html to also get the full HTML (large).
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign id (from laposta_list_campaigns). |
| include_html | boolean | – | Also return the HTML body (default false). |
No output schema declared.
No examples provided.
laposta_get_campaign_history Get a campaign's event history ~174
Recipient events of one campaign (delivered, opened, clicked, bounced, unsubscribed ...), newest first by default, optionally within a date range. Paged by cursor. For totals use laposta_get_report.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign id (from laposta_list_campaigns). |
| cursor | string | – | Cursor: pass the previous reply's next_cursor unchanged, with the same filters. |
| event_date_from | string | – | Events from this moment, inclusive. |
| event_date_to | string | – | Events before this moment, exclusive. |
| limit | integer | – | Items per page (default 25, max 100; a large page can be cut at 50,000 characters and lose its next_cursor). |
| order | string | – | Sort by event date (default desc). |
No output schema declared.
No examples provided.
laposta_get_list Get a mailing list ~42
Get one mailing list: name, state, notification addresses and member counts.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The list id (from laposta_list_lists). |
No output schema declared.
No examples provided.
laposta_get_member Get a member ~67
Get one member of a list by member id or email address: state, signup/confirm dates and custom field values.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The list id (from laposta_list_lists). |
| member | string | yes | The member id OR the member's email address. |
No output schema declared.
No examples provided.
laposta_get_member_history Get a member's event history ~205
The event history of one member (subscribed, confirmed, opened, clicked, bounced, unsubscribed, automations ...), newest first by default. Optionally limited to one campaign or a date range. Paged by cursor.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | – | Only events of this campaign. |
| cursor | string | – | Cursor: pass the previous reply's next_cursor unchanged, with the same filters. |
| event_date_from | string | – | Events from this moment, inclusive. |
| event_date_to | string | – | Events before this moment, exclusive. |
| limit | integer | – | Items per page (default 25, max 100; a large page can be cut at 50,000 characters and lose its next_cursor). |
| list_id | string | yes | The list id (from laposta_list_lists). |
| member | string | yes | The member id OR the member's email address. |
| order | string | – | Sort by event date (default desc). |
No output schema declared.
No examples provided.
laposta_get_report Get a campaign report ~55
Result figures of one campaign: sent, accepted, unique opens and clicks, bounces, complaints, unsubscribes and their ratios.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign id (from laposta_list_campaigns). |
No output schema declared.
No examples provided.
laposta_list_campaigns List campaigns ~76
List the account's campaigns (name, subject, sender, recipient lists, delivery moments). Use limit/offset to page.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Items to return (default 100, max 500). |
| offset | integer | – | Items to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
laposta_list_fields List a list's fields ~63
List the custom fields of a mailing list (name, custom_name used as the key in custom_fields, datatype, required, options). Call this before adding or updating a member.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The list id (from laposta_list_lists). |
No output schema declared.
No examples provided.
laposta_list_lists List mailing lists ~39
List all mailing lists of the Laposta account with member counts (active, unsubscribed, cleaned). Use the list_id in the other tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
laposta_list_members List members of a list ~224
List the members (subscribers) of a mailing list, one page at a time. Filter by state, free-text search (email and field values) or label. Contains personal data: only fetch what the task needs.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor: pass the previous reply's next_cursor unchanged, with the same filters. |
| label | string | – | Only members with this label (by name). |
| limit | integer | – | Items per page (default 25, max 100; a large page can be cut at 50,000 characters and lose its next_cursor). |
| list_id | string | yes | The list id (from laposta_list_lists). |
| order | string | – | Sort direction for order_by (default asc). |
| order_by | string | – | email, signup_date, or a text field's custom_name (comma-separated for several). |
| search | string | – | Only members containing this text in the email or any text/number/choice field. |
| state | string | – | Only members in this state (default: all). |
No output schema declared.
No examples provided.
laposta_list_reports List campaign reports ~79
Result figures of all campaigns: sent, accepted, opened, clicked, bounced, unsubscribed, with ratios. Use limit/offset to page.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Items to return (default 100, max 500). |
| offset | integer | – | Items to skip (default 0). Pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
laposta_list_segments List a list's segments ~48
List the segments of a mailing list (a segment id can be a campaign recipient together with its list).
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The list id (from laposta_list_lists). |
No output schema declared.
No examples provided.
laposta_send_test_email Send a campaign test email ~75
WRITE: send a test copy of a campaign (it must have content and not be sent yet) to ONE email address. Does not send the campaign to its recipients.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign id (from laposta_list_campaigns). |
| string | yes | Where to send the test. |
No output schema declared.
No examples provided.
laposta_set_campaign_content Set a campaign's content ~123
WRITE: replace a campaign's content with your HTML, or let Laposta import it from a URL (html wins if both are given). Does not send anything. The reply's report lists problems Laposta found (javascript, missing unsubscribe link, missing images).
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign id (from laposta_list_campaigns). |
| html | string | – | The complete HTML of the email. |
| import_url | string | – | A public URL Laposta fetches the HTML from. |
| inline_css | boolean | – | Inline the CSS. |
No output schema declared.
No examples provided.
laposta_update_member Update a member ~174
WRITE: change a member's custom field values and/or email address, or unsubscribe the member (state: unsubscribed). Only the fields you pass change. Re-subscribing a person is not offered here: do it in the Laposta app or with laposta_add_member upsert only when they asked for it.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_fields | object | – | Custom field values keyed by the field's custom_name (the variable name shown by laposta_list_fields). Multi-choice fields take an array of option values. |
| string | – | A new email address for this member. | |
| list_id | string | yes | The list id (from laposta_list_lists). |
| member | string | yes | The member id OR the member's email address. |
| state | string | – | Set to unsubscribed to unsubscribe the member. |
No output schema declared.
No examples provided.
How do I install the Laposta MCP by usefulapi server?
Laposta MCP by usefulapi is a hosted endpoint at https://laposta.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 · laposta.usefulapi.io
claude mcp add --transport http io-usefulapi-laposta 'https://laposta.usefulapi.io/mcp'
What is the Laposta MCP by usefulapi server?
Laposta MCP by usefulapi is listed in the public MCP registry as io.usefulapi/laposta. Read Laposta lists, members, campaigns and reports; add members and build campaigns. This page covers its hosted endpoint (https://laposta.usefulapi.io/mcp).
Is the Laposta MCP by usefulapi server safe to use?
Laposta 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 Laposta MCP by usefulapi server expose?
Laposta MCP by usefulapi exposes 18 tools: laposta_list_lists, laposta_get_list, laposta_list_fields, laposta_list_segments, laposta_list_members, and 13 more. Their descriptions and schemas cost roughly 1,997 tokens of context every time the server is loaded.
Does the Laposta MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Laposta 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 Laposta MCP by usefulapi server still maintained?
Laposta 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.