Customer.io MCP by usefulapi
io.usefulapi/customeriousefulapi.iostreamable-httpv1.40.4Scanned
Query people, segments, campaigns, and message deliveries; send transactional email or broadcasts.
13 tools: 2 can delete or cancel things and 11 only read.
- Reads private data · 2
- Reads text others write · 2
- Can send data out · 2
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Customer.io MCP by usefulapi can do
The Customer.io MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 13 tools. It can delete or cancel things (2 tools: customerio_send_transactional_email and customerio_trigger_broadcast). 11 tools only read.
2 tools read private data (customerio_get_customer_messages and customerio_list_messages); 2 tools bring in text other people can write (customerio_get_customer_messages and customerio_list_messages); 2 tools can send data out of your system (customerio_send_transactional_email and customerio_trigger_broadcast). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Deletes or cancels 2Claude Code: deny
customerio_send_transactional_email⚠[U+FE0F] SENDS A REAL EMAIL.Can send data outNo findings
Why it is in this group
- The name "customerio_send_transactional_email" says "send": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "customerio_send_transactional_email" says "send": it sends or publishes something to other people.
Description, as the server wrote itContains invisible characters, shown as [U+…] ⚠[U+FE0F] SENDS A REAL EMAIL. Send a transactional email using a transactional message template. Delivers immediately to the `to` recipient. App API: POST /v1/send/email.
Annotations the server declares
- title: Send transactional email
- destructiveHint: true
customerio_trigger_broadcast⚠[U+FE0F] SENDS TO REAL RECIPIENTS.Can send data outNo findings
Why it is in this group
- The name "customerio_trigger_broadcast" says "trigger": a word for a change.
- The name "customerio_trigger_broadcast" also says "broadcast": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.recipients): what it sends cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "customerio_trigger_broadcast" says "broadcast": it sends or publishes something to other people.
Description, as the server wrote itContains invisible characters, shown as [U+…] ⚠[U+FE0F] SENDS TO REAL RECIPIENTS. Trigger an API-triggered broadcast, delivering to the resolved recipient set. App API: POST /v1/send/broadcast (posts to /v1/campaigns/{broadcast_id}/triggers).
Annotations the server declares
- title: Trigger broadcast
- destructiveHint: true
Only reads 11Show 11 read-only tools
customerio_get_campaignGet a single campaign by id.No findings
Why it is in this group
- The name "customerio_get_campaign" says "get": a word for reading.
Description, as the server wrote it Get a single campaign by id. App API: GET /v1/campaigns/{campaign_id}.
Annotations the server declares
- title: Get campaign
- readOnlyHint: true
customerio_get_campaign_metricsGet delivery/engagement metrics for a campaign over time.No findings
Why it is in this group
- The name "customerio_get_campaign_metrics" says "get": a word for reading.
Description, as the server wrote it Get delivery/engagement metrics for a campaign over time. App API: GET /v1/campaigns/{campaign_id}/metrics.
Annotations the server declares
- title: Get campaign metrics
- readOnlyHint: true
customerio_get_customer_attributesGet a single person's attributes (profile fields).No findings
Why it is in this group
- The name "customerio_get_customer_attributes" says "get": a word for reading.
Description, as the server wrote it Get a single person's attributes (profile fields). App API: GET /v1/customers/{customer_id}/attributes.
Annotations the server declares
- title: Get customer attributes
- readOnlyHint: true
customerio_get_customer_messagesList messages (deliveries) sent to a single person.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "customerio_get_customer_messages" says "get": a word for reading.
What it can reach
- private-dataThe name "customerio_get_customer_messages" says "get" and "message": it reads messages.
- private-dataThe description's first sentence says "list" and "message": it reads messages.
- untrusted-inputThe name "customerio_get_customer_messages" says "get" and "message": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "message": it reads messages, which other people can write.
Description, as the server wrote it List messages (deliveries) sent to a single person. App API: GET /v1/customers/{customer_id}/messages.
Annotations the server declares
- title: Get customer messages
- readOnlyHint: true
customerio_get_customer_segmentsList the segments a single person belongs to.No findings
Why it is in this group
- The name "customerio_get_customer_segments" says "get": a word for reading.
Description, as the server wrote it List the segments a single person belongs to. App API: GET /v1/customers/{customer_id}/segments.
Annotations the server declares
- title: Get customer segments
- readOnlyHint: true
customerio_list_campaignsList all campaigns in the workspace.No findings
Why it is in this group
- The name "customerio_list_campaigns" says "list": a word for reading.
Description, as the server wrote it List all campaigns in the workspace. App API: GET /v1/campaigns.
Annotations the server declares
- title: List campaigns
- readOnlyHint: true
customerio_list_collectionsList reusable data collections in the workspace.No findings
Why it is in this group
- The name "customerio_list_collections" says "list": a word for reading.
Description, as the server wrote it List reusable data collections in the workspace. App API: GET /v1/collections.
Annotations the server declares
- title: List collections
- readOnlyHint: true
customerio_list_exportsList data exports in the workspace.No findings
Why it is in this group
- The name "customerio_list_exports" says "list": a word for reading.
Description, as the server wrote it List data exports in the workspace. App API: GET /v1/exports.
Annotations the server declares
- title: List exports
- readOnlyHint: true
customerio_list_messagesList sent messages (deliveries) across the workspace, filterable by type/campaign/newsletter.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "customerio_list_messages" says "list": a word for reading.
What it can reach
- private-dataThe name "customerio_list_messages" says "list" and "message": it reads messages.
- private-dataThe description's first sentence says "list" and "message": it reads messages.
- untrusted-inputThe name "customerio_list_messages" says "list" and "message": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "message": it reads messages, which other people can write.
Description, as the server wrote it List sent messages (deliveries) across the workspace, filterable by type/campaign/newsletter. App API: GET /v1/messages.
Annotations the server declares
- title: List messages
- readOnlyHint: true
customerio_list_segmentsList all segments in the workspace (id + name + type).No findings
Why it is in this group
- The name "customerio_list_segments" says "list": a word for reading.
Description, as the server wrote it List all segments in the workspace (id + name + type). App API: GET /v1/segments.
Annotations the server declares
- title: List segments
- readOnlyHint: true
customerio_search_customersSearch/list people by a Customer.io filter (segment or attribute conditions).No findings
Why it is in this group
- The name "customerio_search_customers" says "search": a word for reading.
Description, as the server wrote it Search/list people by a Customer.io filter (segment or attribute conditions). e.g. filter={"segment":{"id":7}} or {"and":[...]}. App API: POST /v1/customers.
Annotations the server declares
- title: Search customers
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
8 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__customerio__customerio_send_transactional_email",
"mcp__customerio__customerio_trigger_broadcast"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:34 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://customerio.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://customerio.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://customerio.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://customerio.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http customerio https://customerio.usefulapi.io/mcpclaude mcp add --transport http customerio https://customerio.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__customerio__customerio_search_customers",
"mcp__customerio__customerio_get_customer_attributes",
"mcp__customerio__customerio_get_customer_segments",
"mcp__customerio__customerio_get_customer_messages",
"mcp__customerio__customerio_list_segments",
"mcp__customerio__customerio_list_campaigns",
"mcp__customerio__customerio_get_campaign",
"mcp__customerio__customerio_get_campaign_metrics",
"mcp__customerio__customerio_list_messages",
"mcp__customerio__customerio_list_exports",
"mcp__customerio__customerio_list_collections"
],
"ask": [],
"deny": [
"mcp__customerio__customerio_send_transactional_email",
"mcp__customerio__customerio_trigger_broadcast"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as customerio. Review it before you use it.
Capability tags behind 4 rules
- mcp__customerio__customerio_get_customer_messages private-data, untrusted-input
- mcp__customerio__customerio_list_messages private-data, untrusted-input
- mcp__customerio__customerio_send_transactional_email outbound
- mcp__customerio__customerio_trigger_broadcast outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/customerio/verify?hash=4304371e47fc7901ca08ff65912c6abfdfd9962166f0138767cc8f1e8b927396" | jq -e '.changed == false'Pinned hash 4304371e47fc, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/customerio/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/customerio)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Customer.io MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Customer.io MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 13 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Customer.io MCP by usefulapi delete data?
- Yes. 2 tools can delete, cancel or revoke something: customerio_send_transactional_email and customerio_trigger_broadcast.
Can the Customer.io MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Customer.io MCP by usefulapi have?
- 13 tools: 2 destructive, 11 read. customerio_send_transactional_email, customerio_trigger_broadcast, customerio_search_customers, customerio_get_customer_attributes, customerio_get_customer_segments, customerio_get_customer_messages, customerio_list_segments, customerio_list_campaigns and 5 more.
Does the Customer.io MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Customer.io MCP by usefulapi send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): customerio_send_transactional_email and customerio_trigger_broadcast.
Has the Customer.io MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.