io.usefulapi/getresponse
REMOTE · GETRESPONSE.USEFULAPI.IO · SCANNED OCT 4
Manage GetResponse contacts, campaigns, newsletters and autoresponders.
Available components
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 Security89
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1384 tokens (~98/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 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
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.
remote · getresponse.usefulapi.io
claude mcp add --transport http io-usefulapi-getresponse 'https://getresponse.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-getresponse": {
"url": "https://getresponse.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-getresponse": {
"type": "http",
"url": "https://getresponse.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-getresponse] url = "https://getresponse.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-getresponse": {
"type": "remote",
"url": "https://getresponse.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-getresponse --url 'https://getresponse.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-getresponse:
url: "https://getresponse.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-getresponse": {
"Transport": "http",
"Url": "https://getresponse.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-getresponse -t streamable-http -u 'https://getresponse.usefulapi.io/mcp'
{
"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.
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.
- 4 Oct 26 +45
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.07 ▲ functional
- 3 Oct 26 −44
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 2 Oct 26 +59
- HTTPS: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 29 Sept 26 18
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 4 Oct 2026 · Probed https://getresponse.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 getresponse.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 | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://getresponse.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://getresponse.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://getresponse.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://getresponse.usefulapi.io/mcp |
| Authorisation server | https://getresponse.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://getresponse.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://getresponse.usefulapi.io/mcp | HTTPS enforced | 301 | https://getresponse.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 →
getresponse_create_contact Create contact ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | The campaign (list) id to add the contact to (required). |
| dayOfCycle | integer | – | Autoresponder cycle day to place the contact on (→ dayOfCycle). |
| string | yes | 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. |
No output schema declared.
No examples provided.
getresponse_delete_contact Delete contact ~97
Delete (remove) a contact from the account. This unsubscribes them and deletes their data. REST: DELETE /contacts/{contactId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contactId | string | yes | 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]). |
No output schema declared.
No examples provided.
getresponse_get_account Get account ~38
Get the authenticated GetResponse account profile (id, email, name, company, plan, timezone, etc.). REST: GET /accounts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
getresponse_get_campaign Get campaign (list) ~61
Get a single campaign (mailing list) by id, including subscription confirmation settings. REST: GET /campaigns/{campaignId}.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | yes | The campaign (list) id — the alphanumeric token, not the numeric id. |
No output schema declared.
No examples provided.
getresponse_get_contact Get contact ~79
Get a single contact by id, including campaign membership, tags, custom field values and engagement scoring. REST: GET /contacts/{contactId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contactId | string | yes | The contact id. |
| fields | string | – | Comma-separated list of fields to return, e.g. "name,email" (GetResponse `fields`). |
No output schema declared.
No examples provided.
getresponse_get_newsletter Get newsletter ~50
Get a single newsletter (email broadcast) by id, including its status and send settings. REST: GET /newsletters/{newsletterId}.
| Name | Type | Req | Description |
|---|---|---|---|
| newsletterId | string | yes | The newsletter id. |
No output schema declared.
No examples provided.
getresponse_list_autoresponders List autoresponders ~83
List autoresponders (drip/cycle emails sent automatically on a schedule after subscription). Paginated. REST: GET /autoresponders.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number (pagination). |
| perPage | integer | – | Records per page (GetResponse `perPage`; default 100, max 1000). |
No output schema declared.
No examples provided.
getresponse_list_campaigns List campaigns (lists) ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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]). |
No output schema declared.
No examples provided.
getresponse_list_contacts List contacts ~205
List/search contacts across the account. Paginated, with optional email/name/campaign filters, sort, and a fields selector. REST: GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | string | – | Restrict to contacts in this campaign (list) id (→ query[campaignId]). |
| 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]). |
No output schema declared.
No examples provided.
getresponse_list_custom_fields List custom fields ~79
List the account's custom field definitions (custom contact attributes) — id, name, type and values. REST: GET /custom-fields.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number (pagination). |
| perPage | integer | – | Records per page (GetResponse `perPage`; default 100, max 1000). |
No output schema declared.
No examples provided.
getresponse_list_from_fields List from-fields ~76
List the account's verified 'from' fields (sender name/email addresses usable when sending). REST: GET /from-fields.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number (pagination). |
| perPage | integer | – | Records per page (GetResponse `perPage`; default 100, max 1000). |
No output schema declared.
No examples provided.
getresponse_list_newsletters List newsletters ~114
List newsletters (one-off email broadcasts). Paginated, with optional subject filter and sort. REST: GET /newsletters.
| Name | Type | Req | Description |
|---|---|---|---|
| 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]). |
No output schema declared.
No examples provided.
getresponse_list_tags List tags ~69
List the account's tags (labels applied to contacts for segmentation). REST: GET /tags.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number (pagination). |
| perPage | integer | – | Records per page (GetResponse `perPage`; default 100, max 1000). |
No output schema declared.
No examples provided.
getresponse_update_contact Update contact ~107
Update an existing contact's mutable fields (name, tags, custom field values). Only the fields you supply are changed. REST: POST /contacts/{contactId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contactId | string | yes | 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. |
No output schema declared.
No examples provided.
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.