Courier
REMOTE · MCP.COURIER.COM · SCANNED AUG 3
Send notifications, manage templates, and configure integrations with Courier.
Available components
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_audience). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 10121 tokens (~70/item across 144 items; 144 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 99% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.courier.com
claude mcp add --transport http trycourier-courier https://mcp.courier.com/
[mcp_servers.trycourier-courier] url = "https://mcp.courier.com/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"trycourier-courier": {
"type": "remote",
"url": "https://mcp.courier.com/",
"enabled": true
}
}
} openclaw mcp add trycourier-courier --url https://mcp.courier.com/ --transport streamable-http
mcp_servers:
trycourier-courier:
url: "https://mcp.courier.com/" {
"mcpServers": {
"trycourier-courier": {
"type": "http",
"url": "https://mcp.courier.com/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 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
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 64
First indexed and scored.
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 3 Aug 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 | 11 Jun 2026 | 9 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 634e69f13e12e0100ee909f741870a8b |
| 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 |
DNSSEC insecure
Validation of mcp.courier.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| courier.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.courier.com | Verified | 200 | |
| http (plaintext) | http://mcp.courier.com | HTTPS enforced | 301 | https://mcp.courier.com/ |
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.
list_tenants ~36
List all tenants in the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | — | Pagination cursor |
| limit | number | — | Max results per page |
No output schema declared.
No examples provided.
list_user_push_tokens ~30
List all push/device tokens for a user.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
list_user_tenants ~49
List all tenants a user belongs to.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | — | Pagination cursor |
| limit | number | — | Max results per page |
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
patch_profile ~62
Partially update a user profile via JSON Patch (RFC 6902). Use add/replace/remove operations on specific profile paths.
| Name | Type | Req | Description |
|---|---|---|---|
| patch | array | yes | Array of JSON Patch operations to apply to the profile |
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
patch_user_token ~58
Apply a JSON Patch (RFC 6902) to a specific push token.
| Name | Type | Req | Description |
|---|---|---|---|
| patch | array | yes | Array of JSON Patch operations |
| token | string | yes | The token identifier |
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
publish_journey ~93
Publish the current draft of a journey, making it live and invokable. Pass version to roll back to a prior published version instead of publishing the draft. Returns 404 if there is no draft to publish.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | yes | The journey template ID to publish |
| version | string | — | Historical version to roll back to (e.g. "v001"). Omit to publish the current draft. |
No output schema declared.
No examples provided.
publish_journey_template ~88
Publish the current draft of a journey-scoped notification template. Optionally pass version to roll back to a prior version.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | yes | The journey template ID that owns this notification |
| notification_id | string | yes | The notification template ID |
| version | string | — | Version to roll back to (e.g. "v1"). Omit to publish current draft. |
No output schema declared.
No examples provided.
publish_notification ~106
Publish a notification template, making it available for sending. Must be called before send_message_template unless the template was created with state: 'PUBLISHED'. Publishes the current draft by default; pass version (e.g. 'v001') to publish a specific historical version. Returns 204 on success.
| Name | Type | Req | Description |
|---|---|---|---|
| notification_id | string | yes | The notification template ID to publish |
| version | string | — | Historical version to publish (e.g. v001); omit to publish current draft |
No output schema declared.
No examples provided.
publish_preferences ~41
Publish the workspace's preferences page. Takes a snapshot of every section with its topics under a new published version, making the current state visible on the hosted preferences page.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
publish_tenant_template ~65
Publish a version of a tenant notification template.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | The template ID |
| tenant_id | string | yes | The tenant ID |
| version | string | — | Version to publish (e.g. v1, latest); defaults to latest if omitted |
No output schema declared.
No examples provided.
put_journey_template_content ~116
Replace the elemental content of a journey-scoped notification template. Overwrites all elements. Call publish_journey_template afterwards to make it live.
| Name | Type | Req | Description |
|---|---|---|---|
| elements | array | yes | Array of elemental content nodes |
| journey_id | string | yes | The journey template ID that owns this notification |
| notification_id | string | yes | The notification template ID |
| state | string | — | Template state after update |
| version | string | — | Content version string (e.g. "2022-01-01"). Server defaults when omitted. |
No output schema declared.
No examples provided.
put_journey_template_locale ~113
Set locale-specific content overrides for a journey-scoped notification template. Each element override must reference an existing element by its id.
| Name | Type | Req | Description |
|---|---|---|---|
| elements | array | yes | Array of element overrides with id and locale-specific content |
| journey_id | string | yes | The journey template ID that owns this notification |
| locale_id | string | yes | Locale identifier (e.g. es, fr, pt-BR) |
| notification_id | string | yes | The notification template ID |
| state | string | — | Template state after update |
No output schema declared.
No examples provided.
put_notification_content ~197
Replace the elemental content of a V2 notification template. Overwrites all elements. Use channel elements to target specific channels. Multi-channel example: elements: [{ type: "channel", channel: "email", elements: [{ type: "meta", title: "Hello" }, { type: "text", content: "Email body" }] }, { type: "channel", channel: "push", elements: [{ type: "meta", title: "Hello" }, { type: "text", content: "Push body" }] }, { type: "channel", channel: "inbox", elements: [{ type: "text", content: "Inbox plain text only" }] }].
| Name | Type | Req | Description |
|---|---|---|---|
| elements | array | yes | Array of elemental content nodes |
| notification_id | string | yes | The notification template ID (nt_ prefix) |
| state | string | — | Template state after update |
| version | string | — | Content version string |
No output schema declared.
No examples provided.
put_notification_element ~137
Update a single element within a V2 notification template.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | — | Channels this element applies to |
| data | object | — | Element data payload |
| element_id | string | yes | The element ID to update |
| if | string | — | Conditional expression for element visibility |
| loop | string | — | Loop expression for repeating elements |
| notification_id | string | yes | The notification template ID (nt_ prefix) |
| ref | string | — | Reference identifier |
| state | string | — | Template state after update |
| type | string | yes | Element type (e.g. text, action, image, divider, meta) |
No output schema declared.
No examples provided.
put_notification_locale ~167
Set locale-specific content overrides for a V2 notification template. Each element override must reference an existing element by its id. Example for Spanish locale: { notification_id: "nt_01abc", locale_id: "es", elements: [{ id: "elem_meta_1", title: "Restablecer contraseña" }, { id: "elem_text_1", content: "Haga clic en el enlace para restablecer su contraseña." }] }.
| Name | Type | Req | Description |
|---|---|---|---|
| elements | array | yes | Array of element overrides with id and locale-specific content |
| locale_id | string | yes | Locale identifier (e.g. es, fr, pt-BR) |
| notification_id | string | yes | The notification template ID (nt_ prefix) |
| state | string | — | Template state after update |
No output schema declared.
No examples provided.
release_digest ~67
Release a digest schedule early — send what users have collected so far now instead of waiting for the scheduled time. A 204 is also returned when the schedule has no in-progress instances to release.
| Name | Type | Req | Description |
|---|---|---|---|
| schedule_id | string | yes | The digest schedule id, in the form "sch/{uuid}" |
No output schema declared.
No examples provided.
remove_all_user_tenants ~29
Remove a user from all tenants.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
remove_user_from_tenant ~40
Remove a user from a tenant.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant_id | string | yes | The tenant ID |
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
replace_journey ~154
Replace (update) a journey draft. Full document replacement — include all nodes and properties in the body. Call publish_journey afterwards to make changes live, or pass state: "PUBLISHED" to publish immediately. Send node template IDs must already be scoped to this journey.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | — | Whether the journey is active. |
| journey_id | string | yes | The journey template ID to update |
| name | string | yes | Journey display name |
| nodes | array | yes | Complete array of journey nodes. Use server-assigned node ids from get_journey — do NOT invent new ids. Each node requires type plus type-specific fields. |
| state | string | — | Set to PUBLISHED to publish immediately after replace. |
No output schema declared.
No examples provided.
replace_journey_template ~91
Replace the draft of a journey-scoped notification template. Full document replacement. Call publish_journey_template afterwards to make it live.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | yes | The journey template ID that owns this notification |
| notification | object | yes | Full notification template definition |
| notification_id | string | yes | The notification template ID |
| state | string | — | "PUBLISHED" to publish immediately after replace |
No output schema declared.
No examples provided.
replace_notification ~59
Replace a notification template entirely (full document PUT).
| Name | Type | Req | Description |
|---|---|---|---|
| notification | object | yes | Full notification template payload |
| notification_id | string | yes | The notification template ID to replace |
| state | string | — | Template state after update (defaults to DRAFT) |
No output schema declared.
No examples provided.
replace_preference_section ~96
Replace a preference section. Full document replacement; missing optional fields are cleared. Topics attached to the section are unaffected.
| Name | Type | Req | Description |
|---|---|---|---|
| has_custom_routing | boolean | — | Whether the section defines custom routing for its topics |
| name | string | yes | Human-readable name for the section |
| routing_options | array | — | Default channels for the section. Omit to clear. |
| section_id | string | yes | Id of the preference section |
No output schema declared.
No examples provided.
replace_preference_topic ~169
Replace a topic within a section. Full document replacement; missing optional fields are cleared.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_preferences | array | — | Preference controls a recipient may customize. Omit to clear. |
| default_status | string | yes | Default subscription status applied when a recipient has not set their own |
| include_unsubscribe_header | boolean | — | Whether to include a list-unsubscribe header on emails for this topic |
| name | string | yes | Human-readable name for the preference topic |
| routing_options | array | — | Default channels delivered for this topic. Omit to clear. |
| section_id | string | yes | Id of the preference section |
| topic_data | object | — | Arbitrary metadata associated with the topic. Omit to clear. |
| topic_id | string | yes | Id of the subscription preference topic |
No output schema declared.
No examples provided.
replace_profile ~54
Fully replace a user profile (PUT). All existing data is overwritten; include every field you want to keep.
| Name | Type | Req | Description |
|---|---|---|---|
| profile | object | yes | Complete profile data to replace with |
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.
replace_routing_strategy ~115
Replace a routing strategy. Full document replacement; missing optional fields are cleared.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | object | — | Per-channel delivery configuration. Omit to clear. |
| description | string | — | Description. Omit to clear. |
| name | string | yes | Human-readable name |
| providers | object | — | Per-provider delivery configuration. Omit to clear. |
| routing | object | yes | Routing tree |
| routing_strategy_id | string | yes | The routing strategy ID |
| tags | array | — | Tags. Omit to clear. |
No output schema declared.
No examples provided.
replace_tenant_template ~122
Create or replace a tenant notification template (draft unless published is true).
| Name | Type | Req | Description |
|---|---|---|---|
| channels | — | — | Channel-specific delivery configuration |
| content | — | — | Elemental content object (e.g. elements and version per Courier Elemental schema) |
| providers | — | — | Provider-specific routing configuration |
| published | boolean | — | When true, publish immediately after save |
| routing | — | — | Message routing configuration |
| template_id | string | yes | The template ID |
| tenant_id | string | yes | The tenant ID |
| title | string | — | 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).
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | The message ID of the original message to resend |
No output schema declared.
No examples provided.
restore_list ~25
Restore a previously deleted list.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The list ID |
No output schema declared.
No examples provided.
run_bulk_job ~35
Run a bulk job, triggering delivery to all added users.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The bulk job ID to run |
No output schema declared.
No examples provided.
send_message ~122
Send a message to a user using inline title and body content (no template). Optionally specify routing channels.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Message body |
| channels | array | — | Channel names to route through (e.g. email, sms, push). Omit to use default routing. |
| data | object | — | Key-value data to include with the message |
| method | string | — | Routing method: deliver to all channels or stop after first success |
| title | string | yes | Message title |
| user_id | string | yes | The recipient user ID |
No output schema declared.
No examples provided.
send_message_template ~144
Send a message to a user using a published notification template. The template must be published before sending — call publish_notification first if needed. Example: { user_id: "user-123", template: "nt_01abc123", data: { name: "Alex", resetUrl: "https://app.example.com/reset" } }.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | — | Channel names to route through. Omit to use template routing config. |
| data | object | — | Key-value data for template variables |
| method | string | — | Routing method |
| template | string | yes | Template ID or notification slug |
| user_id | string | yes | The recipient user ID |
No output schema declared.
No examples provided.
send_message_to_list ~98
Send a message to all subscribers of a list using inline title and body content.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Message body |
| channels | array | — | Channel names to route through. Omit to use default routing. |
| data | object | — | Key-value data to include |
| list_id | string | yes | The list ID to send to |
| method | string | — | Routing method |
| title | string | yes | Message title |
No output schema declared.
No examples provided.
send_message_to_list_template ~93
Send a message to all subscribers of a list using a notification template.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | — | Channel names to route through. Omit to use template routing config. |
| data | object | — | Key-value data for template variables |
| list_id | string | yes | The list ID to send to |
| method | string | — | Routing method |
| template | string | yes | Template 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.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The list ID |
| preferences | object | — | Optional notification preferences |
| user_id | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| lists | array | yes | Array of lists to subscribe to |
| user_id | string | yes | The user 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.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | yes | The event name (appears as trigger in Automation Trigger node) |
| messageId | string | yes | Unique ID for deduplication (returns 409 if not unique) |
| properties | object | yes | Event properties payload |
| userId | string | — | User ID associated with the event |
No output schema declared.
No examples provided.
unsubscribe_user_from_list ~42
Unsubscribe a user from a list.
| Name | Type | Req | Description |
|---|---|---|---|
| list_id | string | yes | The list ID |
| user_id | string | yes | The user ID to unsubscribe |
No output schema declared.
No examples provided.
update_audience ~59
Create or update an audience with a filter definition.
| Name | Type | Req | Description |
|---|---|---|---|
| audience_id | string | yes | The audience ID |
| description | string | — | Description |
| filter | — | — | Filter definition object (operator, rules) |
| name | string | — | Display name |
No output schema declared.
No examples provided.
update_brand ~64
Replace an existing brand with new values.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | The brand ID to update |
| name | string | yes | Brand display name |
| settings | object | — | Brand settings (colors, email, inapp) |
| snippets | object | — | Brand snippets |
No output schema declared.
No examples provided.
update_notification_checks ~54
Update check statuses for a notification submission.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | Checks to update |
| notification_id | string | yes | The notification template ID |
| submission_id | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | — | Short alias |
| provider | string | yes | Provider key (must match existing; changing provider type is not supported) |
| provider_id | string | yes | The provider configuration ID |
| settings | object | — | Provider-specific settings |
| title | string | — | 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"] }.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_routing | array | — | Default channels when has_custom_routing is enabled |
| has_custom_routing | boolean | — | When true, use custom_routing instead of template defaults |
| status | string | yes | Subscription status for the topic |
| tenant_id | string | yes | The tenant ID |
| topic_id | string | yes | The 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 ~58
Create or update a translation for a specific locale.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Translation content (PO file format) |
| domain | string | — | Translation domain |
| locale | string | yes | Locale code (e.g. en_US, fr_FR) |
No output schema declared.
No examples provided.
update_user_preference_topic ~93
Update a user's preference for a specific subscription topic (opt in, opt out, or set channel preferences).
| Name | Type | Req | Description |
|---|---|---|---|
| custom_routing | array | — | Custom channel routing order |
| has_custom_routing | boolean | — | Whether custom channel routing is set |
| status | string | yes | Preference status |
| topic_id | string | yes | The subscription topic ID |
| user_id | string | yes | The user ID |
No output schema declared.
No examples provided.