# SendPost MCP by usefulapi (remote · sendpost.usefulapi.io)

Inspect SendPost delivery statistics, sending IPs, message metadata, domains, and suppressions.

- Trust score: 18/100 (low)
- Change this week: −43
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Endpoint: `https://sendpost.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.1`

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

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - 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.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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

## Install

### How do I install the SendPost MCP by usefulapi server?

SendPost MCP by usefulapi is a hosted endpoint at https://sendpost.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-sendpost 'https://sendpost.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-sendpost": {
      "type": "http",
      "url": "https://sendpost.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-11-02 (score 18, −47)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.10 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-31 (score 65, +4)

- [security improvement] Authorization: partial → pass
- [functional improvement] MCP protocol: fail → pass
- [functional] New prompt “audit_sending_domain_configuration”
- [functional] New prompt “compare_delivery_statistics”
- [functional] New prompt “inspect_message_metadata”
- [functional] New prompt “inspect_sending_ips_and_pools”
- [functional] New prompt “review_suppressed_recipients”
- [functional] MCP protocol version: 2025-06-18 → 2025-11-25
- [functional] Server version: 1.2.0 → 1.4.0
- [functional] Server version: 1.1.0 → 1.2.0
- [functional] Server version: 1.0.2 → 1.1.0

### 2026-10-30 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.1 → 1.0.2
- [functional] Server version: 1.0.0 → 1.0.1

### 2026-10-29 (score 61)

First indexed and scored.

## MCP tools (15)

### `sendpost_list_subaccounts` (~67 tokens)

List SendPost sub-accounts

READ (account key): List sub-accounts and safe account metadata. API keys and SMTP credentials are never returned.

Input parameters:

- `limit` (integer): Maximum records, up to 100.
- `offset` (integer): Records to skip for pagination.
- `search` (string)

### `sendpost_get_subaccount` (~42 tokens)

Get SendPost sub-account

READ (account key): Get a sub-account's safe metadata, labels and blocked state. Credentials are excluded.

Input parameters:

- `subaccount_id` (integer, required)

### `sendpost_list_ips` (~67 tokens)

List SendPost sending IPs

READ (account key): List sending IPs, warmup and state metadata. Does not allocate or change IPs.

Input parameters:

- `limit` (integer): Maximum records, up to 100.
- `offset` (integer): Records to skip for pagination.
- `search` (string)

### `sendpost_get_ip` (~39 tokens)

Get SendPost sending IP

READ (account key): Inspect an existing sending IP's public address, reverse DNS and warmup state.

Input parameters:

- `ip_id` (integer, required)

### `sendpost_list_ip_pools` (~66 tokens)

List SendPost IP pools

READ (account key): List IP pool names, routing strategy, overflow settings and safe public IP metadata.

Input parameters:

- `limit` (integer): Maximum records, up to 100.
- `offset` (integer): Records to skip for pagination.
- `search` (string)

### `sendpost_get_ip_pool` (~49 tokens)

Get SendPost IP pool

READ (account key): Inspect one IP pool's routing strategy, overflow settings and public IP metadata. Provider credentials and routing internals are excluded.

Input parameters:

- `ippool_id` (integer, required)

### `sendpost_list_account_stats` (~73 tokens)

List SendPost account daily statistics

READ (account key): Daily delivery, bounce, open, click, unsubscribe and spam counts across sub-accounts. Use up to 366 days per call.

Input parameters:

- `from` (string, required): Start date, YYYY-MM-DD (UTC).
- `to` (string, required): End date, YYYY-MM-DD (UTC).

### `sendpost_get_account_stats` (~66 tokens)

Get SendPost account aggregate statistics

READ (account key): Aggregate delivery and engagement counts across sub-accounts over a date range, up to 366 days.

Input parameters:

- `from` (string, required): Start date, YYYY-MM-DD (UTC).
- `to` (string, required): End date, YYYY-MM-DD (UTC).

### `sendpost_get_account_group_stats` (~83 tokens)

Get SendPost account group statistics

READ (account key): Aggregate delivery and engagement counts for an existing group/tag across sub-accounts, up to 366 days.

Input parameters:

- `from` (string, required): Start date, YYYY-MM-DD (UTC).
- `group` (string, required): Existing message group/tag, for example transactional.
- `to` (string, required): End date, YYYY-MM-DD (UTC).

### `sendpost_list_subaccount_stats` (~77 tokens)

List SendPost sub-account statistics

READ (account key): Read a sub-account's delivery and engagement statistic records for a date range, up to 366 days.

Input parameters:

- `from` (string, required): Start date, YYYY-MM-DD (UTC).
- `subaccount_id` (integer, required)
- `to` (string, required): End date, YYYY-MM-DD (UTC).

### `sendpost_get_subaccount_stats` (~76 tokens)

Get SendPost sub-account aggregate statistics

READ (account key): Aggregate delivery and engagement counts for one sub-account over a date range, up to 366 days.

Input parameters:

- `from` (string, required): Start date, YYYY-MM-DD (UTC).
- `subaccount_id` (integer, required)
- `to` (string, required): End date, YYYY-MM-DD (UTC).

### `sendpost_get_message_metadata` (~67 tokens)

Get SendPost message metadata

READ (account key): Inspect a submitted message's ID, sender, recipient, subject, groups and routing metadata. Excludes bodies, attachments, custom headers and recipient custom fields. Large messages may exceed the 1 MiB read limit.

Input parameters:

- `message_id` (string, required)

### `sendpost_list_domains` (~67 tokens)

List SendPost sending domains

READ (sub-account key): Audit sending domains, DNS record configuration and verification failures. Does not create or verify domains.

Input parameters:

- `limit` (integer): Maximum records, up to 100.
- `offset` (integer): Records to skip for pagination.
- `search` (string)

### `sendpost_get_domain` (~35 tokens)

Get SendPost sending domain

READ (sub-account key): Inspect a sending domain's DNS records and verification status.

Input parameters:

- `domain_id` (integer, required)

### `sendpost_list_suppressions` (~110 tokens)

List SendPost suppressed recipients

READ (sub-account key): Inspect suppressions and documented reasons within a date range, with pagination. Does not add or remove suppressions.

Input parameters:

- `from` (string, required): Start date, YYYY-MM-DD (UTC).
- `limit` (integer): Maximum records, up to 100.
- `offset` (integer): Records to skip for pagination.
- `search` (string)
- `to` (string, required): End date, YYYY-MM-DD (UTC).
- `type` (string)

## Diagnostics

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

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 65
- 2026-10-31: 65
- 2026-10-30: 61
- 2026-10-29: 61

## Common questions

### What is the SendPost MCP by usefulapi server?

SendPost MCP by usefulapi is listed in the public MCP registry as io.usefulapi/sendpost. Inspect SendPost delivery statistics, sending IPs, message metadata, domains, and suppressions. This page covers its hosted endpoint (https://sendpost.usefulapi.io/mcp).

### Is the SendPost MCP by usefulapi server safe to use?

SendPost 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 SendPost MCP by usefulapi server expose?

SendPost MCP by usefulapi exposes 15 tools: sendpost_list_subaccounts, sendpost_get_subaccount, sendpost_list_ips, sendpost_get_ip, sendpost_list_ip_pools, and 10 more. Their descriptions and schemas cost roughly 984 tokens of context every time the server is loaded.

### Does the SendPost MCP by usefulapi server require authentication?

Its publisher declares no required credentials for SendPost 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 SendPost MCP by usefulapi server still maintained?

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

## Links

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