# Sendlane MCP by usefulapi (remote · sendlane.usefulapi.io)

Manage Sendlane lists, contacts, tags and custom fields; read campaign and SMS reports.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `sendlane.usefulapi.io`: 63/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-sendlane/sendlane.md), [page](https://verifymcp.io/servers/io-usefulapi-sendlane/sendlane)

## Channel facts

- Endpoint: `https://sendlane.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 2821 tokens (~91/item across 31 items; 31 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 59% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 32 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http io-usefulapi-sendlane 'https://sendlane.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-sendlane": {
      "url": "https://sendlane.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-sendlane": {
      "type": "http",
      "url": "https://sendlane.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-sendlane]
url = "https://sendlane.usefulapi.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-usefulapi-sendlane --url 'https://sendlane.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-sendlane:
    url: "https://sendlane.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-sendlane": {
      "Transport": "http",
      "Url": "https://sendlane.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-sendlane -t streamable-http -u 'https://sendlane.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-sendlane": {
      "type": "http",
      "url": "https://sendlane.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 63, +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.

### 2026-10-14 (score 62, +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.

### 2026-10-13 (score 61, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] 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

### 2026-10-12 (score 59)

First indexed and scored.

## MCP tools (31)

### `sendlane_list_lists` (~77 tokens)

List lists

List the audience lists of the account: id, name, description, status, created date. GET /lists.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `sendlane_get_list` (~31 tokens)

Get list

One audience list by id. GET /lists/{listId}.

Input parameters:

- `list_id` (integer, required)

### `sendlane_list_list_contacts` (~183 tokens)

List contacts of a list

Contacts on one list: email, name, phone, subscribed/suppressed state, tags, custom fields, lifetime value. GET /lists/{listId}/contacts.

Input parameters:

- `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, required)
- `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.

### `sendlane_list_list_unsubscribed` (~170 tokens)

List unsubscribed contacts of a list

Contacts that unsubscribed from one list. GET /lists/{listId}/unsubscribed.

Input parameters:

- `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, required)
- `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.

### `sendlane_list_contacts` (~177 tokens)

List contacts

All contacts of the account: email, name, phone, lists, tags, custom fields, subscribed/suppressed state. Filter by creation time with from/to. GET /contacts.

Input parameters:

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

### `sendlane_get_contact` (~49 tokens)

Get contact

One contact by id, with lists, tags, custom fields, consent, lifetime value and subscribed/suppressed state. GET /contacts/{contactId}.

Input parameters:

- `contact_id` (integer, required)

### `sendlane_list_unsubscribed_contacts` (~158 tokens)

List unsubscribed contacts

Contacts that unsubscribed from the account. GET /contacts/unsubscribed.

Input parameters:

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

### `sendlane_get_contact_subscriptions` (~50 tokens)

Get contact subscriptions

The list subscriptions of one contact: list, subscribed/suppressed state, who added it and when. GET /contacts/{contactId}/subscriptions.

Input parameters:

- `contact_id` (integer, required)

### `sendlane_get_contact_tags` (~78 tokens)

Get contact tags

The tags on one contact. GET /contacts/{contactId}/tags.

Input parameters:

- `contact_id` (integer, required)
- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `sendlane_get_contact_custom_fields` (~82 tokens)

Get contact custom fields

The custom field values of one contact. GET /contacts/{contactId}/custom-fields.

Input parameters:

- `contact_id` (integer, required)
- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `sendlane_list_tags` (~72 tokens)

List tags

The contact tags of the account: id, name, audience count. GET /tags.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `sendlane_get_tag` (~30 tokens)

Get tag

One tag by id. GET /tags/{tagId}.

Input parameters:

- `tag_id` (integer, required)

### `sendlane_list_tag_contacts` (~164 tokens)

List contacts with a tag

Contacts that carry one tag. GET /tags/{tagId}/contacts.

Input parameters:

- `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, required)
- `to` (string): Only records up to this time. Needs `from`. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z.

### `sendlane_list_custom_fields` (~82 tokens)

List custom fields

The custom contact fields of the account: id, name, type. Use the ids when setting field values. GET /custom-fields.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `sendlane_list_segments` (~76 tokens)

List segments

The segments of the account: id, name, list, match rule, last count. GET /segments.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `sendlane_list_segment_contacts` (~85 tokens)

List contacts of a segment

Contacts in one segment: id, email, name, phone. GET /segments/{segmentId}/contacts.

Input parameters:

- `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, required)

### `sendlane_list_campaigns` (~76 tokens)

List campaigns

Email campaigns: id, name, status, scheduled and sent time, automation. GET /campaigns.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `sendlane_get_campaign` (~32 tokens)

Get campaign

One email campaign by id. GET /campaigns/{campaignId}.

Input parameters:

- `campaign_id` (integer, required)

### `sendlane_get_campaign_report` (~147 tokens)

Get campaign report

Statistics of one email campaign: sent, opens, clicks (unique too), bounced, suppressed, unsubscribed, spam, revenue. from/to limit the period. GET /campaigns/{campaignId}/report.

Input parameters:

- `campaign_id` (integer, required)
- `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.

### `sendlane_list_sms_messages` (~77 tokens)

List SMS messages

SMS messages (campaign and automation): id, name, campaign status, automation. GET /sms-messages.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `sendlane_get_sms_report` (~145 tokens)

Get SMS report

Statistics of one SMS message: sent, delivered, clicks, failed, replies, unsubscribed, credits, revenue. from/to limit the period. GET /sms-messages/{messageId}/report.

Input parameters:

- `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, required)
- `to` (string): Only records up to this time. Needs `from`. ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z.

### `sendlane_list_sender_profiles` (~78 tokens)

List sender profiles

The sender profiles (from name, from/reply email, postal address, default flag). GET /senders.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `sendlane_create_list` (~47 tokens)

Create list

WRITE: create an audience list. Not idempotent: calling it twice makes two lists. POST /lists.

Input parameters:

- `description` (string)
- `name` (string, required)

### `sendlane_update_list` (~65 tokens)

Update list

WRITE: rename a list and/or change its description (a full update: name is required, an omitted description may be cleared). PUT /lists/{listId}.

Input parameters:

- `description` (string)
- `list_id` (integer, required)
- `name` (string, required)

### `sendlane_add_contacts_to_list` (~92 tokens)

Add contacts to a list

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.

Input parameters:

- `contacts` (array, required)
- `list_id` (integer, required)

### `sendlane_remove_contact_from_list` (~56 tokens)

Remove a contact from a list

WRITE: remove one contact from one list (the contact stays in the account). DELETE /lists/{listId}/contacts/{contactId}.

Input parameters:

- `contact_id` (integer, required)
- `list_id` (integer, required)

### `sendlane_unsubscribe_contact` (~43 tokens)

Unsubscribe a contact

WRITE: unsubscribe one contact from email marketing. The contact stops receiving campaigns. POST /contacts/{contactId}/unsubscribe.

Input parameters:

- `contact_id` (integer, required)

### `sendlane_create_tag` (~28 tokens)

Create tag

WRITE: create a contact tag. POST /tags.

Input parameters:

- `name` (string, required)

### `sendlane_add_contact_tags` (~48 tokens)

Tag a contact

WRITE: put one or more existing tags on a contact. POST /contacts/{contactId}/tags.

Input parameters:

- `contact_id` (integer, required)
- `tag_ids` (array, required)

### `sendlane_remove_contact_tag` (~54 tokens)

Untag a contact

WRITE: remove one tag from a contact (the tag itself is kept). DELETE /contacts/{contactId}/tags/{tagId}.

Input parameters:

- `contact_id` (integer, required)
- `tag_id` (integer, required)

### `sendlane_set_contact_custom_fields` (~58 tokens)

Set contact custom fields

WRITE: add custom field values to a contact. Field ids come from sendlane_list_custom_fields. POST /contacts/{contactId}/custom-fields.

Input parameters:

- `contact_id` (integer, required)
- `custom_fields` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-sendlane/sendlane#diagnostics

## Score history

- 2026-10-17: 63
- 2026-10-16: 63
- 2026-10-15: 62
- 2026-10-14: 62
- 2026-10-13: 61
- 2026-10-12: 59

## Common questions

### 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 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://sendlane.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/sendlane/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-sendlane/sendlane.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-sendlane/sendlane.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-sendlane/sendlane