Sendlane MCP by usefulapi
REMOTE · SENDLANE.USEFULAPI.IO
Manage Sendlane lists, contacts, tags and custom fields; read campaign and SMS reports.
Available components
Last scanned (23 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 16 Oct 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 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 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
- 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 & 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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2821 tokens (~91/item across 31 items; 31 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 32 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
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 12 Oct 26 59
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 16 Oct 2026 · Probed https://sendlane.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 sendlane.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 | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://sendlane.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://sendlane.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://sendlane.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://sendlane.usefulapi.io/mcp |
| Authorisation server | https://sendlane.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sendlane.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/sendlane/ |
| http (plaintext) | http://sendlane.usefulapi.io/mcp | Inconclusive | 302 | http://sendlane.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 →
sendlane_add_contact_tags Tag a contact ~48
WRITE: put one or more existing tags on a contact. POST /contacts/{contactId}/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | – |
| tag_ids | array | yes | – |
No output schema declared.
No examples provided.
sendlane_add_contacts_to_list Add contacts to a list ~92
WRITE: add one or more contacts (up to 100) to a list; a contact that does not exist is created. Each needs an email or a phone. Sendlane accepts the request for processing (HTTP 202). Only add people who agreed to receive marketing. POST /lists/{listId}/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | array | yes | – |
| list_id | integer | yes | – |
No output schema declared.
No examples provided.
sendlane_create_list Create list ~47
WRITE: create an audience list. Not idempotent: calling it twice makes two lists. POST /lists.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
sendlane_create_tag Create tag ~28
WRITE: create a contact tag. POST /tags.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
sendlane_get_campaign Get campaign ~32
One email campaign by id. GET /campaigns/{campaignId}.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | integer | yes | – |
No output schema declared.
No examples provided.
sendlane_get_campaign_report Get campaign report ~147
Statistics of one email campaign: sent, opens, clicks (unique too), bounced, suppressed, unsubscribed, spam, revenue. from/to limit the period. GET /campaigns/{campaignId}/report.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | integer | yes | – |
| from | string | – | Only records from this time on. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
| to | string | – | Only records up to this time. Needs `from`. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
No output schema declared.
No examples provided.
sendlane_get_contact Get contact ~49
One contact by id, with lists, tags, custom fields, consent, lifetime value and subscribed/suppressed state. GET /contacts/{contactId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | – |
No output schema declared.
No examples provided.
sendlane_get_contact_custom_fields Get contact custom fields ~82
The custom field values of one contact. GET /contacts/{contactId}/custom-fields.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | – |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
sendlane_get_contact_subscriptions Get contact subscriptions ~50
The list subscriptions of one contact: list, subscribed/suppressed state, who added it and when. GET /contacts/{contactId}/subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | – |
No output schema declared.
No examples provided.
sendlane_get_contact_tags Get contact tags ~78
The tags on one contact. GET /contacts/{contactId}/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | – |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
sendlane_get_list Get list ~31
One audience list by id. GET /lists/{listId}.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | integer | yes | – |
No output schema declared.
No examples provided.
sendlane_get_sms_report Get SMS report ~145
Statistics of one SMS message: sent, delivered, clicks, failed, replies, unsubscribed, credits, revenue. from/to limit the period. GET /sms-messages/{messageId}/report.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Only records from this time on. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
| message_id | integer | yes | – |
| to | string | – | Only records up to this time. Needs `from`. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
No output schema declared.
No examples provided.
sendlane_get_tag Get tag ~30
One tag by id. GET /tags/{tagId}.
| Name | Type | Req | Description |
|---|---|---|---|
| tag_id | integer | yes | – |
No output schema declared.
No examples provided.
sendlane_list_campaigns List campaigns ~76
Email campaigns: id, name, status, scheduled and sent time, automation. GET /campaigns.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
sendlane_list_contacts List contacts ~177
All contacts of the account: email, name, phone, lists, tags, custom fields, subscribed/suppressed state. Filter by creation time with from/to. GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Only records from this time on. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| to | string | – | Only records up to this time. Needs `from`. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
No output schema declared.
No examples provided.
sendlane_list_custom_fields List custom fields ~82
The custom contact fields of the account: id, name, type. Use the ids when setting field values. GET /custom-fields.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
sendlane_list_list_contacts List contacts of a list ~183
Contacts on one list: email, name, phone, subscribed/suppressed state, tags, custom fields, lifetime value. GET /lists/{listId}/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Only records from this time on. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| list_id | integer | yes | – |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| to | string | – | Only records up to this time. Needs `from`. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
No output schema declared.
No examples provided.
sendlane_list_list_unsubscribed List unsubscribed contacts of a list ~170
Contacts that unsubscribed from one list. GET /lists/{listId}/unsubscribed.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Only records from this time on. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| list_id | integer | yes | – |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| to | string | – | Only records up to this time. Needs `from`. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
No output schema declared.
No examples provided.
sendlane_list_lists List lists ~77
List the audience lists of the account: id, name, description, status, created date. GET /lists.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
sendlane_list_segment_contacts List contacts of a segment ~85
Contacts in one segment: id, email, name, phone. GET /segments/{segmentId}/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| segment_id | integer | yes | – |
No output schema declared.
No examples provided.
sendlane_list_segments List segments ~76
The segments of the account: id, name, list, match rule, last count. GET /segments.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
sendlane_list_sender_profiles List sender profiles ~78
The sender profiles (from name, from/reply email, postal address, default flag). GET /senders.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
sendlane_list_sms_messages List SMS messages ~77
SMS messages (campaign and automation): id, name, campaign status, automation. GET /sms-messages.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
sendlane_list_tag_contacts List contacts with a tag ~164
Contacts that carry one tag. GET /tags/{tagId}/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Only records from this time on. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| tag_id | integer | yes | – |
| to | string | – | Only records up to this time. Needs `from`. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
No output schema declared.
No examples provided.
sendlane_list_tags List tags ~72
The contact tags of the account: id, name, audience count. GET /tags.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
sendlane_list_unsubscribed_contacts List unsubscribed contacts ~158
Contacts that unsubscribed from the account. GET /contacts/unsubscribed.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Only records from this time on. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| to | string | – | Only records up to this time. Needs `from`. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. |
No output schema declared.
No examples provided.
sendlane_remove_contact_from_list Remove a contact from a list ~56
WRITE: remove one contact from one list (the contact stays in the account). DELETE /lists/{listId}/contacts/{contactId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | – |
| list_id | integer | yes | – |
No output schema declared.
No examples provided.
sendlane_remove_contact_tag Untag a contact ~54
WRITE: remove one tag from a contact (the tag itself is kept). DELETE /contacts/{contactId}/tags/{tagId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | – |
| tag_id | integer | yes | – |
No output schema declared.
No examples provided.
sendlane_set_contact_custom_fields Set contact custom fields ~58
WRITE: add custom field values to a contact. Field ids come from sendlane_list_custom_fields. POST /contacts/{contactId}/custom-fields.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | – |
| custom_fields | array | yes | – |
No output schema declared.
No examples provided.
sendlane_unsubscribe_contact Unsubscribe a contact ~43
WRITE: unsubscribe one contact from email marketing. The contact stops receiving campaigns. POST /contacts/{contactId}/unsubscribe.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | – |
No output schema declared.
No examples provided.
sendlane_update_list Update list ~65
WRITE: rename a list and/or change its description (a full update: name is required, an omitted description may be cleared). PUT /lists/{listId}.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| list_id | integer | yes | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Sendlane MCP by usefulapi server?
Sendlane MCP by usefulapi is a hosted endpoint at https://sendlane.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 · sendlane.usefulapi.io
claude mcp add --transport http io-usefulapi-sendlane 'https://sendlane.usefulapi.io/mcp'
What is the Sendlane MCP by usefulapi server?
Sendlane MCP by usefulapi is listed in the public MCP registry as io.usefulapi/sendlane. Manage Sendlane lists, contacts, tags and custom fields; read campaign and SMS reports. This page covers its hosted endpoint (https://sendlane.usefulapi.io/mcp).
Is the Sendlane MCP by usefulapi server safe to use?
Sendlane MCP by usefulapi scores 63 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 Sendlane MCP by usefulapi server expose?
Sendlane MCP by usefulapi exposes 31 tools: sendlane_list_lists, sendlane_get_list, sendlane_list_list_contacts, sendlane_list_list_unsubscribed, sendlane_list_contacts, and 26 more. Their descriptions and schemas cost roughly 2,610 tokens of context every time the server is loaded.
Does the Sendlane MCP by usefulapi server require authentication?
Yes. Sendlane MCP by usefulapi 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 Sendlane MCP by usefulapi server still maintained?
Sendlane MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.