Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Courier

REMOTE · MCP.COURIER.COM

Send notifications, manage templates, and configure integrations with Courier.

Available components

−43 this week 36 Trust /100

Last scanned (16 hours ago)

Scores higher than 19% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Communication

Trust breakdown (7 categories)

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 Security89
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.

What we tested

Checks we ran (5)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC

Checks we could not complete (6)

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.

  • Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
  • 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 blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

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 →

Changelog

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.

  • 20 Nov 26 −43
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Tool safety: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Authorization: The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 19 Nov 26 0
    • Tool “bulk_add_user_tenants” rewrote its description, which is the text the model reads security
    • Tool “bulk_add_user_tokens” rewrote its description, which is the text the model reads security
    • “add_bulk_users” added an optional parameter “idempotency_key” cosmetic
    • “create_brand” added an optional parameter “idempotency_key” cosmetic
    • “create_broadcast” added an optional parameter “idempotency_key” cosmetic
    • “create_bulk_job” added an optional parameter “idempotency_key” cosmetic
    • “create_journey” added an optional parameter “idempotency_key” cosmetic
    • “create_journey_template” added an optional parameter “idempotency_key” cosmetic
    • “create_notification” added an optional parameter “idempotency_key” cosmetic
    • “create_preference_section” added an optional parameter “idempotency_key” cosmetic
    • “create_preference_topic” added an optional parameter “idempotency_key” cosmetic
    • “create_preview_device_set” added an optional parameter “idempotency_key” cosmetic
    • “create_preview_run” added an optional parameter “idempotency_key” cosmetic
    • “create_provider” added an optional parameter “idempotency_key” cosmetic
    • “create_routing_strategy” added an optional parameter “idempotency_key” cosmetic
    • “duplicate_broadcast” added an optional parameter “idempotency_key” cosmetic
    • “invoke_ad_hoc_automation” added an optional parameter “idempotency_key” cosmetic
    • “invoke_automation_template” added an optional parameter “idempotency_key” cosmetic
    • “invoke_journey” added an optional parameter “idempotency_key” cosmetic
    • “publish_journey” added an optional parameter “idempotency_key” cosmetic
    • “publish_journey_template” added an optional parameter “idempotency_key” cosmetic
    • “publish_notification” added an optional parameter “idempotency_key” cosmetic
    • “publish_preferences” added an optional parameter “idempotency_key” cosmetic
    • “release_user_digest” added an optional parameter “idempotency_key” cosmetic
    • “run_bulk_job” added an optional parameter “idempotency_key” cosmetic
    • “schedule_broadcast” added an optional parameter “idempotency_key” cosmetic
    • “send_broadcast” added an optional parameter “idempotency_key” cosmetic
    • “send_message” added an optional parameter “idempotency_key” cosmetic
    • “send_message_template” added an optional parameter “idempotency_key” cosmetic
    • “send_message_to_list” added an optional parameter “idempotency_key” cosmetic
    • “send_message_to_list_template” added an optional parameter “idempotency_key” cosmetic
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 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
  • 4 Oct 26 0
    • Stability: fail → pass ▲ security
Diagnostics

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 21 Nov 2026 · Probed https://mcp.courier.com

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.courier.com CN=WE1,O=Google Trust Services,C=US 7 Oct 2026 5 Jan 2027 ECDSA 256 ECDSA-SHA256 cc8e45d17eefa38c135221f5b38531b2
SANs: mcp.courier.com
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 mcp.courier.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
courier.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On connection
HTTP status 401
Header Value
strict-transport-security max-age=15552000; includeSubDomains
content-security-policy default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.courier.com Auth required 401
http (plaintext) http://mcp.courier.com HTTPS enforced 301 https://mcp.courier.com/
MCP tools · 173 exposed · ~18,718 tokens

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 →

Tool Tokens
replace_routing_strategy ~115

Replace a routing strategy. Full document replacement; missing optional fields are cleared.

NameTypeReqDescription
channelsobject–Per-channel delivery configuration. Omit to clear.
descriptionstring–Description. Omit to clear.
namestringyesHuman-readable name
providersobject–Per-provider delivery configuration. Omit to clear.
routingobjectyesRouting tree
routing_strategy_idstringyesThe routing strategy ID
tagsarray–Tags. Omit to clear.

No output schema declared.

No examples provided.

replace_tenant_template ~243

Create or replace a tenant notification template (draft unless published is true).

NameTypeReqDescription
channelsobject–Per-channel delivery configuration, keyed by channel name. Example: { "email": { "providers": ["sendgrid"], "routing_method": "single" } }
contentobjectyesElemental content document. Example: { "version": "2022-01-01", "elements": [{ "type": "meta", "title": "Welcome" }, { "type": "text", "content": "Thanks for signing up." }] }
providersobject–Per-provider configuration, keyed by provider name. Example: { "sendgrid": { "override": { "from": "noreply@example.com" } } }
publishedboolean–When true, publish immediately after save
routingobject–Message routing tree. Example: { "method": "single", "channels": ["email", "sms"] }
template_idstringyesThe template ID
tenant_idstringyesThe tenant ID
titlestring–Optional title merged into template content when provided

No output schema declared.

No examples provided.

resend_message ~75

Resend a previously sent message. Loads the original send request and enqueues a brand-new send to the same recipient with the same content, producing a new messageId; the original message is unchanged. Rate limited per message (429 on rapid repeats).

NameTypeReqDescription
message_idstringyesThe message ID of the original message to resend

No output schema declared.

No examples provided.

restore_list ~25

Restore a previously deleted list.

NameTypeReqDescription
list_idstringyesThe list ID

No output schema declared.

No examples provided.

run_bulk_job ~78

Run a bulk job, triggering delivery to all added users.

NameTypeReqDescription
idempotency_keystring–Optional. Pass the same key when you retry this exact call, and Courier returns the first result instead of doing it again. A key is kept for 25 hours.
job_idstringyesThe bulk job ID to run

No output schema declared.

No examples provided.

schedule_broadcast ~170

Schedule a broadcast to send later to a list or audience. Cancel with cancel_broadcast_schedule.

NameTypeReqDescription
broadcast_idstringyesThe broadcast id
idempotency_keystring–Optional. Pass the same key when you retry this exact call, and Courier returns the first result instead of doing it again. A key is kept for 25 hours.
recipient_idstringyesThe list or audience id
recipient_typestringyesWhether to send to a list or an audience
scheduled_tostringyesWall-clock time of the send with no timezone offset, e.g. 2026-10-01T09:00:00
timezonestring–IANA timezone scheduled_to is expressed in, e.g. America/New_York

No output schema declared.

No examples provided.

send_broadcast ~111

Send a broadcast now to every member of a list or audience. This delivers real messages.

NameTypeReqDescription
broadcast_idstringyesThe broadcast id
idempotency_keystring–Optional. Pass the same key when you retry this exact call, and Courier returns the first result instead of doing it again. A key is kept for 25 hours.
recipient_idstringyesThe list or audience id
recipient_typestringyesWhether to send to a list or an audience

No output schema declared.

No examples provided.

send_message ~183

Send a message to a user using inline title and body content (no template). Optionally specify routing channels. API reference: https://www.courier.com/docs/api-reference/send/send-a-message.

NameTypeReqDescription
bodystringyesMessage body
channelsarray–Channel names to route through (e.g. email, sms, push). Omit to use default routing.
dataobject–Key-value data to include with the message
idempotency_keystring–Optional. Pass the same key when you retry this exact call, and Courier returns the first result instead of doing it again. A key is kept for 25 hours.
methodstring–Routing method: deliver to all channels or stop after first success
titlestringyesMessage title
user_idstringyesThe recipient user ID

No output schema declared.

No examples provided.

send_message_template ~187

Send a message to a user using a published notification template. Only published templates can be sent; publishing a draft is a separate operation. Example: { user_id: "user-123", template: "nt_01abc123", data: { name: "Alex", resetUrl: "https://app.example.com/reset" } }.

NameTypeReqDescription
channelsarray–Channel names to route through. Omit to use template routing config.
dataobject–Key-value data for template variables
idempotency_keystring–Optional. Pass the same key when you retry this exact call, and Courier returns the first result instead of doing it again. A key is kept for 25 hours.
methodstring–Routing method
templatestringyesTemplate ID or notification slug
user_idstringyesThe recipient user ID

No output schema declared.

No examples provided.

send_message_to_list ~159

Send a message to all subscribers of a list using inline title and body content. API reference: https://www.courier.com/docs/api-reference/send/send-a-message.

NameTypeReqDescription
bodystringyesMessage body
channelsarray–Channel names to route through. Omit to use default routing.
dataobject–Key-value data to include
idempotency_keystring–Optional. Pass the same key when you retry this exact call, and Courier returns the first result instead of doing it again. A key is kept for 25 hours.
list_idstringyesThe list ID to send to
methodstring–Routing method
titlestringyesMessage title

No output schema declared.

No examples provided.

send_message_to_list_template ~136

Send a message to all subscribers of a list using a notification template.

NameTypeReqDescription
channelsarray–Channel names to route through. Omit to use template routing config.
dataobject–Key-value data for template variables
idempotency_keystring–Optional. Pass the same key when you retry this exact call, and Courier returns the first result instead of doing it again. A key is kept for 25 hours.
list_idstringyesThe list ID to send to
methodstring–Routing method
templatestringyesTemplate ID or notification slug

No output schema declared.

No examples provided.

subscribe_user_to_list ~59

Subscribe a user to a list. Creates the list if it doesn't exist.

NameTypeReqDescription
list_idstringyesThe list ID
preferencesobject–Optional notification preferences
user_idstringyesThe user ID to subscribe

No output schema declared.

No examples provided.

subscribe_user_to_lists ~50

Subscribe a user to one or more lists. Creates lists that do not exist.

NameTypeReqDescription
listsarrayyesArray of lists to subscribe to
user_idstringyesThe user ID

No output schema declared.

No examples provided.

trace_message ~172

Trace delivery in one call. Give EXACTLY ONE of message_id (a single message) or trace_id (the metadata.trace_id set on a send, which can span several messages). Returns each matching message with its event history, which carries the status reason when a message is undeliverable. Set include_output to also return the rendered content each provider received.

NameTypeReqDescription
include_outputboolean–Also return rendered content per provider. Off by default, since rendered email can be large.
limitinteger–Max messages to trace for a trace_id. Defaults to 10.
message_idstring–A message id, as returned by send. Mutually exclusive with trace_id.
trace_idstring–The metadata.trace_id set on the send. Mutually exclusive with message_id.

No output schema declared.

No examples provided.

track_inbound_event ~99

Track an inbound event that can trigger automations. Requires event name, messageId (for deduplication), and properties.

NameTypeReqDescription
eventstringyesThe event name (appears as trigger in Automation Trigger node)
messageIdstringyesUnique ID for deduplication (returns 409 if not unique)
propertiesobjectyesEvent properties payload
userIdstring–User ID associated with the event

No output schema declared.

No examples provided.

unsubscribe_user_from_list ~42

Unsubscribe a user from a list.

NameTypeReqDescription
list_idstringyesThe list ID
user_idstringyesThe user ID to unsubscribe

No output schema declared.

No examples provided.

update_audience ~142

Create or update an audience with a filter definition.

NameTypeReqDescription
audience_idstringyesThe audience ID
descriptionstring–Description
filter––Audience membership filter. Either a single condition ({ operator, path, value }) or a group ({ operator: "AND" | "OR", filters: [...] }) nesting to any depth. Example: { "operator": "AND", "filters"…
namestring–Display name

No output schema declared.

No examples provided.

update_brand ~64

Replace an existing brand with new values.

NameTypeReqDescription
brand_idstringyesThe brand ID to update
namestringyesBrand display name
settingsobject–Brand settings (colors, email, inapp)
snippetsobject–Brand snippets

No output schema declared.

No examples provided.

update_notification_checks ~54

Update check statuses for a notification submission.

NameTypeReqDescription
checksarrayyesChecks to update
notification_idstringyesThe notification template ID
submission_idstringyesThe submission ID for the checks resource

No output schema declared.

No examples provided.

update_provider ~106

Replace an existing provider configuration. Full replacement — retrieve current config with get_provider first; omitted optional fields are cleared. Changing API keys or settings affects live delivery if this integration is in use.

NameTypeReqDescription
aliasstring–Short alias
providerstringyesProvider key (must match existing; changing provider type is not supported)
provider_idstringyesThe provider configuration ID
settingsobject–Provider-specific settings
titlestring–Display name

No output schema declared.

No examples provided.

update_tenant_preference ~216

Set the default notification preference for a subscription topic on a tenant. This controls tenant-level defaults — it does NOT set per-user preferences (use the user preferences API for that). The topic_id must already exist as a subscription topic in the workspace; a 404 means the topic has not been created yet. Example: { tenant_id: "acme", topic_id: "marketing-updates", status: "OPTED_IN", has_custom_routing: true, custom_routing: ["email", "push"] }.

NameTypeReqDescription
custom_routingarray–Default channels when has_custom_routing is enabled
has_custom_routingboolean–When true, use custom_routing instead of template defaults
statusstringyesSubscription status for the topic
tenant_idstringyesThe tenant ID
topic_idstringyesThe subscription topic ID — must already exist in the workspace. A 404 response means the topic does not exist; create it in the Preferences Editor first.

No output schema declared.

No examples provided.

update_translation ~80

Create or update a translation for a specific locale. API reference: https://www.courier.com/docs/api-reference/translations/update-translations-by-locale.

NameTypeReqDescription
bodystringyesTranslation content (PO file format)
domainstring–Translation domain
localestringyesLocale code (e.g. en_US, fr_FR)

No output schema declared.

No examples provided.

update_user_preference_topic ~144

Update a user's preference for a specific subscription topic (opt in, opt out, or set channel preferences).

NameTypeReqDescription
custom_routingarray–Custom channel routing order
digest_schedule_idstring|null–Put the user on one of the topic's digest schedules. Pass null to clear their choice and fall back to the default schedule.
has_custom_routingboolean–Whether custom channel routing is set
statusstringyesPreference status
tenant_idstring–Update the preference for this tenant context only
topic_idstringyesThe subscription topic ID
user_idstringyesThe user ID

No output schema declared.

No examples provided.

Install

How do I install the Courier MCP server?

Courier is a hosted endpoint at https://mcp.courier.com/, 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 · mcp.courier.com

# add to Claude Code
claude mcp add --transport http trycourier-courier 'https://mcp.courier.com/'
Common questions

What is the Courier MCP server?

Courier is an MCP server listed in the public MCP registry as io.github.trycourier/courier. Send notifications, manage templates, and configure integrations with Courier. This page covers its hosted endpoint (https://mcp.courier.com).

Is the Courier MCP server safe to use?

Courier scores 36 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 Courier MCP server expose?

Courier exposes 173 tools: list_messages, get_message, get_message_content, get_message_history, list_notifications, and 168 more. Their descriptions and schemas cost roughly 18,718 tokens of context every time the server is loaded.

Does the Courier MCP server require authentication?

Yes. Courier asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Courier MCP server still maintained?

Courier is still listed as active in the MCP registry. We last reached this channel on 21 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 Courier MCP server?

VerifyMCP ran 5 checks on Courier, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Courier: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 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.