Community Gmail server with auto-auth: search, read and send email via MCP.
Nothing to run from here
Mail Blaze MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
26
tools declared
remote
at its publisher
—
calls last 7d
What it does
Manage Mail Blaze lists, subscribers, templates, campaigns and reports; send transactional email.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mail-blaze-mcp-by-usefulapi https://mailblaze.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# mailblaze_list_lists, mailblaze_get_list, mailblaze_list_list_fields and 23 more
Mail Blaze MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 664 servers
usefulapi664 servers
25 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http mail-blaze-mcp-by-usefulapi https://mailblaze.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
26 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List the account's mailing lists (name, uid, subscriber counts, defaults). Use the list uid in the other tools. Paged: page + per_page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, starting at 1 (results come in sets of 10; keep going until a page comes back empty). |
| per_page | integer | no | Lists per page (default set by Mail Blaze). |
Get one mailing list by its uid: general settings, default sender, company details and counts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_uid | string | yes | List uid from mailblaze_list_lists. |
List the fields of a mailing list (label, tag, type, required). The tags (EMAIL, FNAME, LNAME, custom ones) are the keys used when adding or updating subscribers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_uid | string | yes | — |
| page | integer | no | Page number, starting at 1 (results come in sets of 10; keep going until a page comes back empty). |
List the segments defined on a mailing list (uid, name). A segment uid can be used when creating a campaign.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_uid | string | yes | — |
| page | integer | no | Page number, starting at 1 (results come in sets of 10; keep going until a page comes back empty). |
List the subscribers of a mailing list (sets of 10 per page; use page to go on). Contains personal data (emails, names).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_uid | string | yes | — |
| page | integer | no | Page number, starting at 1 (results come in sets of 10; keep going until a page comes back empty). |
Get one subscriber of a list by subscriber uid (status, fields, dates).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_uid | string | yes | — |
| subscriber_uid | string | yes | Subscriber uid from mailblaze_list_subscribers or mailblaze_find_subscriber_by_email. |
Look up a subscriber in one list by email address. Returns the subscriber (with its uid) or a not-found error.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_uid | string | yes | — |
| string | yes | — |
WRITE, MAY SEND A CONFIRMATION EMAIL: add one subscriber to a mailing list. Depending on the list's settings Mail Blaze may send the person a confirmation (double opt-in) email. Only add people who agreed to receive your email. An email that is already on the list answers with a conflict error.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_uid | string | yes | — |
| string | yes | — | |
| first_name | string | no | Sets the FNAME field. |
| last_name | string | no | Sets the LNAME field. |
| custom_fields | object | no | Custom field values keyed by the field's tag (see mailblaze_list_list_fields), e.g. {"PHONE": "+1 555 0100"}. |
WRITE, MAY SEND CONFIRMATION EMAILS: add up to 100 subscribers to a mailing list in one request; an email already on the list is updated instead. Depending on the list's settings Mail Blaze may send confirmation emails. Only add people who agreed to receive your email.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_uid | string | yes | — |
| subscribers | array | yes | 1 to 100 subscribers. |
WRITE: update a subscriber's name or custom fields. Pass the subscriber's current email (Mail Blaze requires it) plus only the values to change. Does not change subscription status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_uid | string | yes | — |
| subscriber_uid | string | yes | — |
| string | yes | The subscriber's email (Mail Blaze requires it on update). | |
| first_name | string | no | — |
| last_name | string | no | — |
| custom_fields | object | no | Custom field values keyed by the field's tag (see mailblaze_list_list_fields), e.g. {"PHONE": "+1 555 0100"}. |
WRITE: set a subscriber's status to unsubscribed so they receive no more campaigns from this list. By default Mail Blaze also adds the address to the account's local blacklist. Do this only when the person asked to stop (or a data-protection request requires it). The subscriber record is kept.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_uid | string | yes | — |
| subscriber_uid | string | yes | — |
WRITE: set a previously unsubscribed subscriber back to subscribed so campaigns reach them again. Only do this when the person asked to be re-added (consent).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_uid | string | yes | — |
| subscriber_uid | string | yes | — |
List the account's email templates (uid, name). A template uid is needed to create a campaign.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, starting at 1 (results come in sets of 10; keep going until a page comes back empty). |
Get one email template by uid (name and content).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| template_uid | string | yes | — |
WRITE: create an email template from HTML (the tool base64-encodes it). Mail Blaze requires the HTML to contain an unsubscribe link. Sends nothing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| html | string | yes | The full HTML of the email, including an unsubscribe link. |
List the account's email campaigns (uid, name, status, dates). Use the campaign uid for details and reports.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, starting at 1 (results come in sets of 10; keep going until a page comes back empty). |
Get one campaign by uid: sender, subject, list, template, status and schedule.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_uid | string | yes | — |
WRITE, SENDS EMAIL TO PEOPLE: create a campaign for a mailing list (or one of its segments) from an existing template and schedule it for send_at. Once it goes out it reaches every subscriber of the list or segment, may use sending credit and cannot be recalled. Confirm the list, segment, subject, template and send time with the user before calling. Needs a template uid (mailblaze_list_templates)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Internal campaign name. |
| from_name | string | yes | — |
| from_email | string | yes | Sender address; it must be a verified sender in Mail Blaze. |
| reply_to | string | yes | — |
| subject | string | yes | — |
| list_uid | string | yes | — |
| segment_uid | string | no | Send only to this segment of the list. |
| template_uid | string | yes | — |
| send_at | string | yes | When to send, 'YYYY-MM-DD HH:MM:SS' (interpreted by Mail Blaze in the account's time zone). |
Bulk report summary (sent, opens, clicks, bounces, unsubscribes) for up to 50 campaigns in one call. Read-only (it is a POST in the API only because of the id list).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_uids | array | yes | 1 to 50 campaign uids. |
Inbox-provider breakdown (e.g. Gmail, Outlook, Yahoo) of a campaign's delivery.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_uid | string | yes | — |
List the individual events of a campaign by kind: opens, clicks, bounces or unsubscribes. Cursor-paged: pass the reply's next_cursor back until it is null. For very large campaigns Mail Blaze answers 202 with a job_id; check it with mailblaze_get_report_job.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign_uid | string | yes | — |
| kind | string | yes | — |
| limit | integer | no | Events per page (default 100, max 1000). |
| cursor | string | no | The next_cursor from the previous reply, passed back exactly as returned. Omit for the first page. |
Email activity (sends, opens, clicks, bounces) of one subscriber by email address, optionally limited to one list. Cursor-paged.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | — | |
| list_uid | string | no | — |
| limit | integer | no | Events per page (default 100, max 1000). |
| cursor | string | no | The next_cursor from the previous reply, passed back exactly as returned. Omit for the first page. |
Status (and result when finished) of an asynchronous report job, as returned in a 202 reply with a job_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | — |
List the transactional emails sent through the account (uid, recipient, subject, status). Paged.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, starting at 1 (results come in sets of 10; keep going until a page comes back empty). |
Get one transactional email by uid: recipient, subject, status and timestamps.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| email_uid | string | yes | — |
WRITE, SENDS ONE EMAIL NOW: send a single one-to-one email to one recipient through Mail Blaze. It leaves immediately, uses sending credit and cannot be recalled. Give either html (the body) or template_id (a transactional template, with merge_tags covering every tag in it), not both. Confirm the recipient and content with the user before calling. Not for bulk or marketing mail; use a campaign for
| Parameter | Type | Required | Notes |
|---|---|---|---|
| to_email | string | yes | — |
| to_name | string | yes | Recipient name (required by Mail Blaze). |
| from_email | string | yes | Sender address; it must be a verified sender in Mail Blaze. |
| from_name | string | yes | Sender name (required by Mail Blaze). |
| reply_to_email | string | no | — |
| reply_to_name | string | no | — |
| subject | string | yes | — |
| html | string | no | HTML body (the tool base64-encodes it). Omit when using template_id. |
| template_id | string | no | Transactional template id. Omit when sending html. |
| merge_tags | object | no | Template merge tags (required with template_id); every tag in the template must be present. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Mail Blaze MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.15.5 · scanned 8 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest3890e0d96cbc11583669326ca40f081fe34848c6ef2b23ce62607882937df6b5
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| mailblaze_list_lists | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_get_list | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_list_list_fields | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_list_segments | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_list_subscribers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_get_subscriber | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_find_subscriber_by_email | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_add_subscriber | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| mailblaze_add_subscribers_bulk | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| mailblaze_update_subscriber | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| mailblaze_unsubscribe_subscriber | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| mailblaze_resubscribe_subscriber | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| mailblaze_list_templates | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_get_template | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_create_template | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| mailblaze_list_campaigns | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_get_campaign | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_create_campaign | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| mailblaze_get_campaign_summaries | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_get_campaign_inbox_breakdown | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_list_campaign_events | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_get_subscriber_activity | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_get_report_job | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_list_transactional_emails | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_get_transactional_email | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mailblaze_send_transactional_email | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest3890e0d96cbc1158
Scanned2026-11-08
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.15.5.
1.15.5
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Mail Blaze MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.