Community Gmail server with auto-auth: search, read and send email via MCP.
Nothing to run from here
Notify 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.
73/100
trust score
21
tools declared
local
runs on your machine
—
downloads a day
What it does
Transactional email for coding agents: send, test, verify domains, webhooks, logs.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user notifycx-notify-mcp '--' npx -y notifycx-mcp
# 2 — ask your agent for something these tools do
# bootstrap_start, bootstrap_confirm, send_email and 18 more
Notify costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NOAll 1 server
notifycx1 server
1 category
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. This one runs on your machine: your client starts Notify as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user notifycx-notify-mcp '--' npx -y notifycx-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take NOTIFY_API_KEY (Notify API key (nk_...). Optional until bootstrap_start/bootstrap_confirm returns one.) if you want to set it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
21 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Start Notify agent signup or key recovery without the dashboard. Sends a 6-digit email OTP. No NOTIFY_API_KEY required. Ask the user to paste the code, then call bootstrap_confirm. Requires acceptTerms: true (https://notify.cx/terms).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | User email for the Notify account | |
| intent | string | no | signup (default) or recover existing account |
| acceptTerms | boolean | yes | Must be true — user accepts Terms and AUP |
Confirm the email OTP from bootstrap_start. Returns api_key once — instruct the user to put it in MCP env NOTIFY_API_KEY (do not leave the secret in chat). Then use add_domain / send_email. No NOTIFY_API_KEY required for this call.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | — | |
| code | string | yes | 6-digit code from email |
| intent | string | no | — |
| clientHint | string | no | e.g. cursor, chatgpt |
Send transactional email via Notify (password reset, receipt, magic link, invoice, etc.) with a verified from domain. Use when the user wants production delivery. Prefer html for the body. For non-delivering API rehearsal before domain verification, use send_test_email instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| to | string | yes | Recipient email address |
| from | string | yes | Sender address or Name <email@verified-domain.com>. Production custom from requires a verified domain. |
| subject | string | yes | Email subject line |
| html | string | no | HTML (or plain text) body. Prefer html; message/text also work. |
| message | string | no | Alias for html/body content |
| text | string | no | Alias for html/body content |
API rehearsal for Notify: same request shape as production send but does not deliver and does not count toward quota. Use before domain verification or when testing the HTTP contract. For real inbox delivery, use send_email after verifying SPF/DKIM.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| to | string | yes | Recipient email address |
| from | string | yes | Sender address or Name <email@verified-domain.com>. Production custom from requires a verified domain. |
| subject | string | yes | Email subject line |
| html | string | no | HTML (or plain text) body. Prefer html; message/text also work. |
| message | string | no | Alias for html/body content |
| text | string | no | Alias for html/body content |
List Notify sending domains and verification status (SPF/DKIM). Includes structured dnsRecords (type/name/value) for the user to publish at their DNS host.
No parameter schema on file.
Get one Notify sending domain by hostname, including dnsRecords (type/name/value) and raw DNS tokens for pending verification. Show dnsRecords to the user so they can add them at their hosting provider.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain hostname, e.g. example.com |
Add a sending domain and start SPF/DKIM verification. Returns dnsRecords (type/name/value) the user must add at their DNS host — Notify does not publish DNS. After DNS is configured, call check_domain. Then use send_email with a from address on that domain.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain hostname to verify, e.g. example.com |
| dnsProvider | string | no | Optional DNS provider hint for host/name formatting |
Poll SES for domain SPF/DKIM verification status after DNS records were added. Call after add_domain. When both succeed, production send_email with that from domain is unlocked and the plan email limit lifts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Domain hostname to check |
List recent Notify email delivery logs. Use after a send to check delivery, bounce, open, or click status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number (default 1) |
| limit | integer | no | Page size (default 20, max 100) |
| eventType | string | no | Filter logs by analytics event type |
Get Notify plan usage and quota (hourly/monthly sends, account_verified). Use when debugging limits or confirming production unlock.
No parameter schema on file.
List API key metadata for the account (id, name, prefix only — never the full secret).
No parameter schema on file.
Create an API key (full_access required). Free plan allows one key. Prefer sending_access + domainId for app keys on Pro+.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| permission | string | no | — |
| domainId | string | no | — |
Rotate an API key secret by keyId. Returns the new api_key once — update NOTIFY_API_KEY / app secrets.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyId | string | yes | — |
Deactivate an API key by keyId. Cannot delete the last full_access key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyId | string | yes | — |
Get a Stripe Checkout URL for Pro or Scale (full_access key). User opens the URL in a browser to pay — not the Notify dashboard.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan | string | no | — |
List Notify webhook subscriptions (URL, events, domain scope).
No parameter schema on file.
Get one Notify webhook by id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Webhook subscription id |
Create a Notify webhook for delivery events on a verified domain. Requires Pro or Scale (free plan has 0 webhooks). Use list_domains to get domainId.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| webhookUrl | string | yes | HTTPS URL to receive webhook events |
| subscribedEvents | array | yes | Event types to subscribe to |
| domainId | string | yes | Verified sending domain id from list_domains |
| matchMode | string | no | Optional match scope (default domain) |
| matchHosts | array | no | When matchMode is hosts |
| matchFroms | array | no | When matchMode is froms |
Update an existing Notify webhook (URL, events, domain scope).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Webhook subscription id |
| webhookUrl | no | — | |
| subscribedEvents | no | — | |
| domainId | no | — | |
| matchMode | yes | — | |
| matchHosts | yes | — | |
| matchFroms | yes | — |
Delete a Notify webhook subscription by id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Webhook subscription id |
Send a test Notify webhook payload to a URL (does not require an existing subscription id).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| webhookUrl | string | yes | HTTPS URL to receive the test payload |
| eventType | string | yes | Event type for the test payload |
| domainId | string | no | Optional verified domain id for scoped test payloads |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Notify 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: —
CTrust score 73 / 100
Release 1.2.3 · scanned 5 Nov 2026
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 score77
Client score73
Findings4 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest9274c090f27733d1b66bfa61d7ca787b02be3ba7ee9db98313479e0b30cb97b7
Score vectorthreat 77 → client 73
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (21 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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 |
|---|---|---|
| bootstrap_start | no tags | |
| bootstrap_confirm | no tags | |
| send_email | external-sink | external-sink: keyword "send_email" |
| send_test_email | no tags | |
| list_domains | no tags | |
| get_domain | no tags | |
| add_domain | no tags | |
| check_domain | no tags | |
| list_email_logs | no tags | |
| get_usage | no tags | |
| list_api_keys | no tags | |
| create_api_key | no tags | |
| regenerate_api_key | no tags | |
| delete_api_key | no tags | |
| create_billing_checkout | no tags | |
| list_webhooks | no tags | |
| get_webhook | no tags | |
| create_webhook | external-sink | external-sink: keyword "webhook" |
| update_webhook | external-sink | external-sink: keyword "webhook" |
| delete_webhook | external-sink | external-sink: keyword "webhook" |
| test_webhook | external-sink | external-sink: keyword "webhook" |
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.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest9274c090f27733d1
Scanned2026-11-05
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.2.3. Pin a release below and the command asks for exactly that one.
1.2.3
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 Notify 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.