Skip to content

MailBluster MCP by usefulapi

io.usefulapi/mailblusterusefulapi.iostreamable-httpv1.27.4Scanned

Manage MailBluster leads, custom fields, products and orders: look up, add and update records.

13 tools: 5 can delete or cancel things, 2 change things and 6 only read.

Tools: 5 delete, 0 irreversible, 2 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 13
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

7 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 MailBluster MCP by usefulapi can do

The MailBluster MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 13 tools. It can delete or cancel things (5 tools: mailbluster_create_lead, mailbluster_update_lead, mailbluster_update_product, mailbluster_create_order and 1 more) and create or change data (2 tools: mailbluster_create_field and mailbluster_create_product). 6 tools only read.

1 tool reads private data (mailbluster_get_lead); 13 tools bring in text other people can write (mailbluster_list_fields, mailbluster_create_field, mailbluster_get_lead and 10 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.27.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 5Claude Code: deny
  • mailbluster_create_leadWRITE: add a lead (contact) to the brand.Reads text others writeNo findings

    Why it is in this group

    • The name "mailbluster_create_lead" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: add a lead (contact) to the brand. `subscribed` defaults to FALSE: the lead is stored but is not subscribed to email. Only set subscribed=true when the person has given consent to receive email from this brand (the user is responsible for lawful consent); this server never subscribes anyone on its own. No email is sent by this tool (double opt-in is not offered). If the lead already exists the call fails unless overwrite_existing=true, which replaces the stored data (then `subscribed` must be given explicitly). POST /leads.

    Annotations the server declares

    • title: Create lead
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • mailbluster_create_orderWRITE: record an order (a tracking record: it does not take payment, charge a card or send email).Reads text others writeNo findings

    Why it is in this group

    • The name "mailbluster_create_order" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: record an order (a tracking record: it does not take payment, charge a card or send email). The customer's email becomes a lead if none exists, and the lead's tags are merged. `customer.subscribed` is REQUIRED because MailBluster would otherwise default it to true: pass false unless the customer has consented to email. For a customer who already exists, the value may replace their stored subscription state. Only set subscribed=true when the person has given consent to receive email from this brand (the user is responsible for lawful consent); this server never subscribes anyone on its own. POST /orders.

    Annotations the server declares

    • title: Create order record
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • mailbluster_update_leadWRITE: change an existing lead's name, custom fields, email, timezone, IP address, subscription flag or tags (send only what should change).Reads text others writeNo findings

    Why it is in this group

    • The name "mailbluster_update_lead" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: change an existing lead's name, custom fields, email, timezone, IP address, subscription flag or tags (send only what should change). `subscribed` is left alone unless you pass it; false unsubscribes the lead, true re-subscribes. Only set subscribed=true when the person has given consent to receive email from this brand (the user is responsible for lawful consent); this server never subscribes anyone on its own. PUT /leads/{md5(email)}.

    Annotations the server declares

    • title: Update lead
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • mailbluster_update_orderWRITE: change an order record's campaign, currency, total or items (send only what should change; `items`, when given, REPLACES all previous items).Reads text others writeNo findings

    Why it is in this group

    • The name "mailbluster_update_order" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: change an order record's campaign, currency, total or items (send only what should change; `items`, when given, REPLACES all previous items). The customer cannot be changed here. No payment or email is involved. PUT /orders/{order_id}.

    Annotations the server declares

    • title: Update order record
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • mailbluster_update_productWRITE: rename a product record.Reads text others writeNo findings

    Why it is in this group

    • The name "mailbluster_update_product" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: rename a product record. PUT /products/{product_id}.

    Annotations the server declares

    • title: Update product
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Changes things 2Claude Code: ask
  • mailbluster_create_fieldWRITE: create a custom lead field.Reads text others writeNo findings

    Why it is in this group

    • The name "mailbluster_create_field" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: create a custom lead field. The merge tag is the key used in lead `fields` and in email templates. Creating a field changes the brand's data model but sends nothing. POST /fields.

    Annotations the server declares

    • title: Create custom lead field
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • mailbluster_create_productWRITE: register a product record (your own id plus a name) so orders can reference it.Reads text others writeNo findings

    Why it is in this group

    • The name "mailbluster_create_product" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: register a product record (your own id plus a name) so orders can reference it. Sends nothing to anyone and charges nothing. POST /products.

    Annotations the server declares

    • title: Create product
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 6Show 6 read-only tools
  • mailbluster_get_leadGet one lead by email address (the server computes the MD5 id MailBluster uses): name, custom fields, timezone, subscribed and opt-in status, tags, created/updated dates.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "mailbluster_get_lead" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "get" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Get one lead by email address (the server computes the MD5 id MailBluster uses): name, custom fields, timezone, subscribed and opt-in status, tags, created/updated dates. MailBluster has no list-leads endpoint. GET /leads/{md5(email)}.

    Annotations the server declares

    • title: Get lead
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • mailbluster_get_orderGet one order record by the id it was created with.Reads text others writeNo findings

    Why it is in this group

    • The name "mailbluster_get_order" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Get one order record by the id it was created with. GET /orders/{order_id}.

    Annotations the server declares

    • title: Get order
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • mailbluster_get_productGet one product record by the id you registered it under.Reads text others writeNo findings

    Why it is in this group

    • The name "mailbluster_get_product" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Get one product record by the id you registered it under. GET /products/{product_id}.

    Annotations the server declares

    • title: Get product
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • mailbluster_list_fieldsList the brand's custom lead fields: id, label and merge tag.Reads text others writeNo findings

    Why it is in this group

    • The name "mailbluster_list_fields" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List the brand's custom lead fields: id, label and merge tag. Use the merge tags as keys of `fields` when creating or updating leads. GET /fields.

    Annotations the server declares

    • title: List custom lead fields
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • mailbluster_list_ordersList order records (id, currency, total price, customer lead, campaign, line items).Reads text others writeNo findings

    Why it is in this group

    • The name "mailbluster_list_orders" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List order records (id, currency, total price, customer lead, campaign, line items). These are records kept in MailBluster for tracking; no payment is involved. Paged: see meta.nextPageNo. GET /orders.

    Annotations the server declares

    • title: List orders
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • mailbluster_list_productsList product records (id, name, dates) the brand has registered for e-commerce tracking.Reads text others writeNo findings

    Why it is in this group

    • The name "mailbluster_list_products" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List product records (id, name, dates) the brand has registered for e-commerce tracking. Paged: the reply's meta has total and nextPageNo (null on the last page). GET /products.

    Annotations the server declares

    • title: List products
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: 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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:36 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

  1. 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: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://mailbluster.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://mailbluster.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.

  1. 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: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://mailbluster.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://mailbluster.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.27.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http mailbluster https://mailbluster.usefulapi.io/mcp
claude mcp add --transport http mailbluster https://mailbluster.usefulapi.io/mcp

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__mailbluster__mailbluster_list_fields",
      "mcp__mailbluster__mailbluster_get_lead",
      "mcp__mailbluster__mailbluster_list_products",
      "mcp__mailbluster__mailbluster_get_product",
      "mcp__mailbluster__mailbluster_list_orders",
      "mcp__mailbluster__mailbluster_get_order"
    ],
    "ask": [
      "mcp__mailbluster__mailbluster_create_field",
      "mcp__mailbluster__mailbluster_create_product"
    ],
    "deny": [
      "mcp__mailbluster__mailbluster_create_lead",
      "mcp__mailbluster__mailbluster_update_lead",
      "mcp__mailbluster__mailbluster_update_product",
      "mcp__mailbluster__mailbluster_create_order",
      "mcp__mailbluster__mailbluster_update_order"
    ]
  }
}

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 mailbluster. Review it before you use it.

Capability tags behind 13 rules
  • mcp__mailbluster__mailbluster_list_fields untrusted-input
  • mcp__mailbluster__mailbluster_create_field untrusted-input
  • mcp__mailbluster__mailbluster_get_lead private-data, untrusted-input
  • mcp__mailbluster__mailbluster_create_lead untrusted-input
  • mcp__mailbluster__mailbluster_update_lead untrusted-input
  • mcp__mailbluster__mailbluster_list_products untrusted-input
  • mcp__mailbluster__mailbluster_get_product untrusted-input
  • mcp__mailbluster__mailbluster_create_product untrusted-input
  • mcp__mailbluster__mailbluster_update_product untrusted-input
  • mcp__mailbluster__mailbluster_list_orders untrusted-input
  • mcp__mailbluster__mailbluster_get_order untrusted-input
  • mcp__mailbluster__mailbluster_create_order untrusted-input
  • mcp__mailbluster__mailbluster_update_order untrusted-input

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/mailbluster/verify?hash=0b8855f5eb84b86205bef4682897c6ed6c121d5679b4f7bf796db134831803b1" | jq -e '.changed == false'

Pinned hash 0b8855f5eb84, 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/mailbluster/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/mailbluster
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/mailbluster.svg)](https://radar.anlyon.com/servers/io.usefulapi/mailbluster)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

MailBluster MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the MailBluster MCP by usefulapi safe?

No scan can promise that. What its definitions show: 13 tools, 7 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 MailBluster MCP by usefulapi delete data?

Yes. 5 tools can delete, cancel or revoke something: mailbluster_create_lead, mailbluster_update_lead, mailbluster_update_product, mailbluster_create_order and mailbluster_update_order.

Can the MailBluster 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 MailBluster MCP by usefulapi have?

13 tools: 5 destructive, 2 write, 6 read. mailbluster_create_lead, mailbluster_update_lead, mailbluster_update_product, mailbluster_create_order, mailbluster_update_order, mailbluster_create_field, mailbluster_create_product, mailbluster_list_fields and 5 more.

Does the MailBluster MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the MailBluster MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the MailBluster MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.