# io.usefulapi/getresponse (remote · getresponse.usefulapi.io)

Manage GetResponse contacts, campaigns, newsletters and autoresponders.

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

## Components

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

## Channel facts

- Endpoint: `https://getresponse.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-04.

- **Endpoint Security**: 89/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 is enforced; there's no plaintext access path.
  - 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**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1384 tokens (~98/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 14 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 io.usefulapi/getresponse MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-getresponse": {
      "type": "http",
      "url": "https://getresponse.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-04 (score 78, +45)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.07

### 2026-10-03 (score 33, −44)

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

### 2026-10-02 (score 77, +59)

- [security improvement] HTTPS: unverified → pass
- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: 100
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 100

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (14)

### `getresponse_get_account` (~38 tokens)

Get account

Get the authenticated GetResponse account profile (id, email, name, company, plan, timezone, etc.). REST: GET /accounts.

### `getresponse_list_campaigns` (~146 tokens)

List campaigns (lists)

List the account's campaigns — GetResponse's name for mailing lists a contact can subscribe to. Paginated. Optional name filter and sort. REST: GET /campaigns.

Input parameters:

- `name` (string): Filter by campaign (list) name substring (→ query[name]).
- `page` (integer): 1-based page number (pagination).
- `perPage` (integer): Records per page (GetResponse `perPage`; default 100, max 1000).
- `sortCreatedOn` (string): Sort by created date ASC/DESC (→ sort[createdOn]).
- `sortName` (string): Sort by campaign name ASC/DESC (→ sort[name]).

### `getresponse_get_campaign` (~61 tokens)

Get campaign (list)

Get a single campaign (mailing list) by id, including subscription confirmation settings. REST: GET /campaigns/{campaignId}.

Input parameters:

- `campaignId` (string, required): The campaign (list) id — the alphanumeric token, not the numeric id.

### `getresponse_list_contacts` (~205 tokens)

List contacts

List/search contacts across the account. Paginated, with optional email/name/campaign filters, sort, and a fields selector. REST: GET /contacts.

Input parameters:

- `campaignId` (string): Restrict to contacts in this campaign (list) id (→ query[campaignId]).
- `email` (string): Filter by email substring (→ query[email]).
- `fields` (string): Comma-separated list of fields to return, e.g. "name,email" (GetResponse `fields`).
- `name` (string): Filter by name substring (→ query[name]).
- `page` (integer): 1-based page number (pagination).
- `perPage` (integer): Records per page (GetResponse `perPage`; default 100, max 1000).
- `sortCreatedOn` (string): Sort by created date ASC/DESC (→ sort[createdOn]).
- `sortEmail` (string): Sort by email ASC/DESC (→ sort[email]).

### `getresponse_get_contact` (~79 tokens)

Get contact

Get a single contact by id, including campaign membership, tags, custom field values and engagement scoring. REST: GET /contacts/{contactId}.

Input parameters:

- `contactId` (string, required): The contact id.
- `fields` (string): Comma-separated list of fields to return, e.g. "name,email" (GetResponse `fields`).

### `getresponse_list_newsletters` (~114 tokens)

List newsletters

List newsletters (one-off email broadcasts). Paginated, with optional subject filter and sort. REST: GET /newsletters.

Input parameters:

- `page` (integer): 1-based page number (pagination).
- `perPage` (integer): Records per page (GetResponse `perPage`; default 100, max 1000).
- `sortCreatedOn` (string): Sort by created date ASC/DESC (→ sort[createdOn]).
- `subject` (string): Filter by subject substring (→ query[subject]).

### `getresponse_get_newsletter` (~50 tokens)

Get newsletter

Get a single newsletter (email broadcast) by id, including its status and send settings. REST: GET /newsletters/{newsletterId}.

Input parameters:

- `newsletterId` (string, required): The newsletter id.

### `getresponse_list_autoresponders` (~83 tokens)

List autoresponders

List autoresponders (drip/cycle emails sent automatically on a schedule after subscription). Paginated. REST: GET /autoresponders.

Input parameters:

- `page` (integer): 1-based page number (pagination).
- `perPage` (integer): Records per page (GetResponse `perPage`; default 100, max 1000).

### `getresponse_list_tags` (~69 tokens)

List tags

List the account's tags (labels applied to contacts for segmentation). REST: GET /tags.

Input parameters:

- `page` (integer): 1-based page number (pagination).
- `perPage` (integer): Records per page (GetResponse `perPage`; default 100, max 1000).

### `getresponse_list_custom_fields` (~79 tokens)

List custom fields

List the account's custom field definitions (custom contact attributes) — id, name, type and values. REST: GET /custom-fields.

Input parameters:

- `page` (integer): 1-based page number (pagination).
- `perPage` (integer): Records per page (GetResponse `perPage`; default 100, max 1000).

### `getresponse_list_from_fields` (~76 tokens)

List from-fields

List the account's verified 'from' fields (sender name/email addresses usable when sending). REST: GET /from-fields.

Input parameters:

- `page` (integer): 1-based page number (pagination).
- `perPage` (integer): Records per page (GetResponse `perPage`; default 100, max 1000).

### `getresponse_create_contact` (~180 tokens)

Create contact

Add a contact to a campaign (mailing list). GetResponse processes this asynchronously and returns HTTP 202 (queued) with no body — the contact appears in the list within a few minutes. REST: POST /contacts.

Input parameters:

- `campaignId` (string, required): The campaign (list) id to add the contact to (required).
- `dayOfCycle` (integer): Autoresponder cycle day to place the contact on (→ dayOfCycle).
- `email` (string, required): Contact email address (required).
- `ipAddress` (string): Contact IP address, used by GetResponse for geolocation.
- `name` (string): Contact name (defaults to 'Friend' if omitted).
- `note` (string): A free-text note to attach to the contact.
- `tags` (array): Array of tag ids to apply to the contact.

### `getresponse_update_contact` (~107 tokens)

Update contact

Update an existing contact's mutable fields (name, tags, custom field values). Only the fields you supply are changed. REST: POST /contacts/{contactId}.

Input parameters:

- `contactId` (string, required): The contact id to update.
- `customFieldValues` (array): Custom field values to set (each { customFieldId, value:[...] }).
- `name` (string): New contact name.
- `tags` (array): Array of tag ids to set on the contact.

### `getresponse_delete_contact` (~97 tokens)

Delete contact

Delete (remove) a contact from the account. This unsubscribes them and deletes their data. REST: DELETE /contacts/{contactId}.

Input parameters:

- `contactId` (string, required): The contact id to delete.
- `ipAddress` (string): Optional IP address to record for the deletion (→ query[ipAddress]).
- `messageId` (string): Optional id of the message this deletion is attributed to (→ query[messageId]).

## Diagnostics

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

## Score history

- 2026-10-04: 78
- 2026-10-03: 33
- 2026-10-02: 77
- 2026-10-01: 18
- 2026-09-30: 18
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/getresponse MCP server?

io.usefulapi/getresponse is an MCP server listed in the public MCP registry as io.usefulapi/getresponse. Manage GetResponse contacts, campaigns, newsletters and autoresponders. This page covers its hosted endpoint (https://getresponse.usefulapi.io/mcp).

### Is the io.usefulapi/getresponse MCP server safe to use?

io.usefulapi/getresponse scores 78 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 io.usefulapi/getresponse MCP server expose?

io.usefulapi/getresponse exposes 14 tools: getresponse_get_account, getresponse_list_campaigns, getresponse_get_campaign, getresponse_list_contacts, getresponse_get_contact, and 9 more. Their descriptions and schemas cost roughly 1,384 tokens of context every time the server is loaded.

### Does the io.usefulapi/getresponse MCP server require authentication?

Yes. io.usefulapi/getresponse 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 io.usefulapi/getresponse MCP server still maintained?

io.usefulapi/getresponse is still listed as active in the MCP registry. We last reached this channel on 4 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://getresponse.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-getresponse/getresponse.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-getresponse/getresponse.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-getresponse/getresponse