Emma MCP by usefulapi
REMOTE · EMMA.USEFULAPI.IO
Read audiences, groups, mailings and campaign results without sending email or changing contacts.
Available components
Last scanned (5 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 Nov 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Nov 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.10 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “compare_email_campaign_results” functional
- New prompt “inspect_link_clicks_and_recipient_activity” functional
- New prompt “review_audience_groups_and_membership” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.4.0 → 1.6.0 functional
- Server version: 1.3.0 → 1.4.0 functional
- Server version: 1.2.2 → 1.3.0 functional
- 30 Oct 26 +1
- Server version: 1.2.1 → 1.2.2 functional
- Server version: 1.2.0 → 1.2.1 functional
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 1.2.0 functional
- Server version: 1.0.0 → 1.1.0 functional
- 28 Oct 26 63
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 6 Nov 2026 · Probed https://emma.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 emma.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://emma.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/emma/ |
| http (plaintext) | http://emma.usefulapi.io/mcp | Inconclusive | 302 | http://emma.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 →
emma_find_member_by_email ~64
Find one member by email address, with all custom fields and status. A 404 means the address is not in the audience.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The member's email address. | |
| include_deleted | boolean | – | Find the member even if archived. |
No output schema declared.
No examples provided.
emma_get_group ~46
Get one member group with its member counts (active, opted-out, error).
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | integer | yes | The group id (member_group_id from emma_list_groups). |
No output schema declared.
No examples provided.
emma_get_import ~92
Status and results of one bulk member import (by import id), or, without an id, the list of all imports of the account.
| Name | Type | Req | Description |
|---|---|---|---|
| import_id | integer | – | The import id. |
| limit | integer | – | Results per page, 1-500 (default 100). |
| start | integer | – | Offset of the first result (default 0). Use next_start from the previous reply. |
No output schema declared.
No examples provided.
emma_get_mailing ~91
Get one mailing in full: content (HTML and plain text), recipients (groups, searches, segments), links, schedule, status.
| Name | Type | Req | Description |
|---|---|---|---|
| include_segment_names | boolean | – | Add the names of the recipient segments. |
| include_subscription_names | boolean | – | Add the names of the recipient subscriptions. |
| mailing_id | integer | yes | The mailing id (mailing_id from emma_list_mailings). |
No output schema declared.
No examples provided.
emma_get_mailing_response ~53
Response summary of one mailing: recipients, sent, delivered, bounced, opened, clicked (unique and total), forwarded, opt-outs, sign-ups.
| Name | Type | Req | Description |
|---|---|---|---|
| mailing_id | integer | yes | The mailing id. |
No output schema declared.
No examples provided.
emma_get_member ~54
Get one member by id, with all custom fields, status, SMS status and bounce count.
| Name | Type | Req | Description |
|---|---|---|---|
| include_deleted | boolean | – | Find the member even if archived. |
| member_id | integer | yes | The member id. |
No output schema declared.
No examples provided.
emma_get_member_groups ~73
List the groups one member belongs to.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-500 (default 100). |
| member_id | integer | yes | The member id. |
| start | integer | – | Offset of the first result (default 0). Use next_start from the previous reply. |
No output schema declared.
No examples provided.
emma_get_member_mailings ~86
The mailing history of one member: which mailings they were sent and what they did with them.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-500 (default 100). |
| member_id | integer | yes | The member id. |
| start | integer | – | Offset of the first result (default 0). Use next_start from the previous reply. |
No output schema declared.
No examples provided.
emma_get_response_summary ~98
Month-by-month response statistics for the whole account: mailings, sent, delivered, bounced, opened, clicked, forwarded, opt-outs, sign-ups (test mailings excluded).
| Name | Type | Req | Description |
|---|---|---|---|
| include_deleted | boolean | – | Include archived mailings. |
| range | string | – | Date range YYYY-MM-DD~YYYY-MM-DD, for example 2026-01-01~2026-06-30; one side may be empty. |
No output schema declared.
No examples provided.
emma_get_search_members ~89
The members that currently match a saved search. Paged: use next_start.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-500 (default 100). |
| search_id | integer | yes | The saved search id (from emma_list_searches). |
| start | integer | – | Offset of the first result (default 0). Use next_start from the previous reply. |
No output schema declared.
No examples provided.
emma_list_fields ~82
List the custom member fields of the account (shortcut names, display names, types).
| Name | Type | Req | Description |
|---|---|---|---|
| include_deleted | boolean | – | Also include deleted fields. |
| limit | integer | – | Results per page, 1-500 (default 100). |
| start | integer | – | Offset of the first result (default 0). Use next_start from the previous reply. |
No output schema declared.
No examples provided.
emma_list_group_members ~102
List the members of one group (email, status, custom fields). Paged: use next_start for more.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | integer | yes | The group id. |
| include_deleted | boolean | – | Include archived (deleted) members. |
| limit | integer | – | Results per page, 1-500 (default 100). |
| start | integer | – | Offset of the first result (default 0). Use next_start from the previous reply. |
No output schema declared.
No examples provided.
emma_list_groups ~112
List the member groups (audience lists) of the Emma account with their active, opted-out and error member counts. Defaults to normal groups; group_types can add test and hidden groups.
| Name | Type | Req | Description |
|---|---|---|---|
| group_types | array | – | g = group (default), t = test, h = hidden. |
| limit | integer | – | Results per page, 1-500 (default 100). |
| start | integer | – | Offset of the first result (default 0). Use next_start from the previous reply. |
No output schema declared.
No examples provided.
emma_list_mailing_activity ~219
Who did what with one mailing: members it was sent to (sends), still in the queue (in_progress), delivered or bounced (deliveries), opened (opens), clicked (clicks), forwarded, opted out (optouts) or signed up (signups). Each row has the member's email and timestamp. Paged: use next_start.
| Name | Type | Req | Description |
|---|---|---|---|
| delivery_type | string | – | Only for kind=deliveries: filter by delivery outcome (default all). |
| kind | string | yes | Which activity to list. |
| limit | integer | – | Results per page, 1-500 (default 100). |
| link_id | integer | – | Only for kind=clicks: limit to one link (link_id from emma_list_mailing_links). |
| mailing_id | integer | yes | The mailing id. |
| member_id | integer | – | Only for kind=clicks: limit to one member. |
| start | integer | – | Offset of the first result (default 0). Use next_start from the previous reply. |
No output schema declared.
No examples provided.
emma_list_mailing_links ~78
The links of one mailing with their unique and total clicks.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-500 (default 100). |
| mailing_id | integer | yes | The mailing id. |
| start | integer | – | Offset of the first result (default 0). Use next_start from the previous reply. |
No output schema declared.
No examples provided.
emma_list_mailing_members ~88
List the individual members a mailing was sent to (not groups or searches). Paged: use next_start.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-500 (default 100). |
| mailing_id | integer | yes | The mailing id. |
| start | integer | – | Offset of the first result (default 0). Use next_start from the previous reply. |
No output schema declared.
No examples provided.
emma_list_mailings ~209
List mailings (campaigns): id, name, subject, sender, status (p pending, a paused, i injecting, s sending, x canceled, c complete, w waiting, u unapproved, f failed), type, recipient count, scheduled time. Defaults to standard and test mailings in all statuses, newest first. Paged: use next_start.
| Name | Type | Req | Description |
|---|---|---|---|
| include_archived | boolean | – | Include archived mailings. |
| is_scheduled | boolean | – | Only mailings that have a scheduled send time. |
| limit | integer | – | Results per page, 1-500 (default 100). |
| mailing_statuses | array | – | Only these statuses (default: all). |
| mailing_types | array | – | m standard (default with t), t test, r trigger/automated, s subject-line split test, c content split test. |
| start | integer | – | Offset of the first result (default 0). Use next_start from the previous reply. |
No output schema declared.
No examples provided.
emma_list_members ~179
List the members (contacts) of the whole audience: id, email, status (a active, o opted out, e error), custom fields, bounce count. Paged: use next_start for more. With count_only the reply is just the number of members.
| Name | Type | Req | Description |
|---|---|---|---|
| count_only | boolean | – | Return only the number of members (count=true) instead of the list. |
| deleted_only | boolean | – | Only archived (deleted) members. |
| exclude_fields | boolean | – | Return only the base attributes, without custom fields (smaller reply). |
| include_deleted | boolean | – | Also include archived (deleted) members. |
| limit | integer | – | Results per page, 1-500 (default 100). |
| start | integer | – | Offset of the first result (default 0). Use next_start from the previous reply. |
No output schema declared.
No examples provided.
emma_list_searches ~82
List the saved searches (dynamic segments) of the account, with their criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| include_deleted | boolean | – | Also include deleted searches. |
| limit | integer | – | Results per page, 1-500 (default 100). |
| start | integer | – | Offset of the first result (default 0). Use next_start from the previous reply. |
No output schema declared.
No examples provided.
How do I install the Emma MCP by usefulapi server?
Emma MCP by usefulapi is a hosted endpoint at https://emma.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 · emma.usefulapi.io
claude mcp add --transport http io-usefulapi-emma 'https://emma.usefulapi.io/mcp'
What is the Emma MCP by usefulapi server?
Emma MCP by usefulapi is listed in the public MCP registry as io.usefulapi/emma. Read audiences, groups, mailings and campaign results without sending email or changing contacts. This page covers its hosted endpoint (https://emma.usefulapi.io/mcp).
Is the Emma MCP by usefulapi server safe to use?
Emma 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 Emma MCP by usefulapi server expose?
Emma MCP by usefulapi exposes 19 tools: emma_list_groups, emma_get_group, emma_list_group_members, emma_list_members, emma_get_member, and 14 more. Their descriptions and schemas cost roughly 1,897 tokens of context every time the server is loaded.
Does the Emma MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Emma 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 Emma MCP by usefulapi server still maintained?
Emma MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Emma MCP by usefulapi server?
VerifyMCP ran 4 checks on Emma MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Emma MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.