Cosend
REMOTE · MCP.COSEND.APP
WhatsApp Business inbox for AI apps: read and answer chats, run campaigns, deploy automations.
Available components
Last scanned (20 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Communication
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 30302 tokens (~242/item across 125 items; 125 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability check failed: schema churn in the 18 days we've observed: 2 tool removals, 1 breaking changes, 0 auth/transport breaks, 102 additions. See how to fix → Fail
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
- Structured output schemas are declared (1% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 126 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 46 to 50.
- 20 Nov 26 0
- Tool “rollback_automation” rewrote its description, which is the text the model reads security
- Tool “switch_on_automation” rewrote its description, which is the text the model reads security
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43.
- 18 Nov 26 0
- Tool “get_inbox_overview” rewrote its description, which is the text the model reads security
- “update_contact” reworded the description of “attributes” cosmetic
- “upsert_contact” reworded the description of “attributes” cosmetic
- 17 Nov 26 −1
- Stability: 0.43 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “automation_recipes” was removed ▼ security
- Tool “describe_automation” was removed ▼ security
- Tool “draft_reply” was removed ▼ security
- Tool “get_authoring_chat” was removed ▼ security
- Tool “get_automation_catalogue” was removed ▼ security
- Tool “manage_automation” was removed ▼ security
- Tool “set_automation_state” was removed ▼ security
- Tool “translate_message” was removed ▼ security
- Tool “upsert_automation” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- New tool “buy_cosend_number”, which the server declares destructive security
- New tool “copy_automation”, which the server declares destructive security
- New tool “create_custom_automation”, which the server declares destructive security
- New tool “delete_automation”, which the server declares destructive security
- New tool “keep_cosend_number”, which the server declares destructive security
- New tool “rollback_automation”, which the server declares destructive security
- New tool “set_up_accurate_warehouse_arrival”, which the server declares destructive security
- New tool “set_up_ai_receptionist”, which the server declares destructive security
- New tool “set_up_appointment_reminder”, which the server declares destructive security
- New tool “set_up_lead_capture”, which the server declares destructive security
- New tool “set_up_missed_call_text_back”, which the server declares destructive security
- New tool “set_up_order_confirmation”, which the server declares destructive security
- New tool “set_up_order_updates”, which the server declares destructive security
- New tool “set_up_payment_reminder”, which the server declares destructive security
- New tool “set_up_quote_intake”, which the server declares destructive security
- New tool “set_up_review_request”, which the server declares destructive security
- New tool “set_up_welcome_menu”, which the server declares destructive security
- New tool “stop_cosend_number”, which the server declares destructive security
- New tool “switch_off_automation”, which the server declares destructive security
- New tool “switch_on_automation”, which the server declares destructive security
- New tool “update_accurate_warehouse_arrival”, which the server declares destructive security
- New tool “update_ai_receptionist”, which the server declares destructive security
- New tool “update_appointment_reminder”, which the server declares destructive security
- New tool “update_automation_details”, which the server declares destructive security
- New tool “update_custom_automation”, which the server declares destructive security
- New tool “update_lead_capture”, which the server declares destructive security
- New tool “update_missed_call_text_back”, which the server declares destructive security
- New tool “update_order_confirmation”, which the server declares destructive security
- New tool “update_order_updates”, which the server declares destructive security
- New tool “update_payment_reminder”, which the server declares destructive security
- New tool “update_quote_intake”, which the server declares destructive security
- New tool “update_review_request”, which the server declares destructive security
- New tool “update_welcome_menu”, which the server declares destructive security
- Tool “deploy_automation” rewrote its description, which is the text the model reads security
- Tool “get_report” rewrote its description, which is the text the model reads security
- Tool “import_contacts” rewrote its description, which is the text the model reads security
- Tool “manage_number” rewrote its description, which is the text the model reads security
- Tool “run_automation” rewrote its description, which is the text the model reads security
- Tool “send_campaign” rewrote its description, which is the text the model reads security
- Tool “update_campaign” rewrote its description, which is the text the model reads security
- Schema quality: 215 → 241 ▼ functional
- “deploy_automation” added a required parameter “actions”, so existing callers break ▼ functional
- “run_automation” added a required parameter “actions”, so existing callers break ▼ functional
- First check of Tool coverage: 1 functional
- New tool “list_automation_building_blocks” functional
- New tool “list_automation_recipes” functional
- New tool “list_cosend_numbers” functional
- “import_contacts” added an optional parameter “details” cosmetic
- “import_contacts” added an optional parameter “new_fields” cosmetic
- “update_campaign” added an optional parameter “ab” cosmetic
- “update_campaign” added an optional parameter “buttons” cosmetic
- “update_campaign” added an optional parameter “cards” cosmetic
- “update_campaign” added an optional parameter “header” cosmetic
- “update_campaign” added an optional parameter “kind” cosmetic
- “update_campaign” added an optional parameter “let_join” cosmetic
- “update_campaign” added an optional parameter “reply_rules” cosmetic
- “update_campaign” added an optional parameter “steps” cosmetic
- “update_campaign” added an optional parameter “track_clicks” cosmetic
- “get_report” reworded the description of “card” cosmetic
- “manage_number” reworded the description of “action” cosmetic
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
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.cosend.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.cosend.app | CN=WE1,O=Google Trust Services,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e6d88c9d95117b110e3d3f2b21818bf1 |
| SANs: mcp.cosend.app | ||||||
| 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.cosend.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| cosend.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.cosend.app/.well-known/oauth-protected-resource/mcp", scope="messages:read messages:write contacts:read contacts:write templates:read templates:write automations:read automations:write runs:read runs:write connectors:read connectors:write usage:read members:read billing:read settings:read connections:read connections:write approvals:read approvals:write campaigns:read campaigns:write"
Bearer resource_metadata="https://mcp.cosend.app/.well-known/oauth-protected-resource/mcp", scope="messages:read messages:write contacts:read contacts:write templates:read templates:write automations:read automations:write runs:read runs:write connectors:read connectors:write usage:read members:read billing:read settings:read connections:read connections:write approvals:read approvals:write campaigns:read campaigns:write" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Protected resource metadata
| Document | https://mcp.cosend.app/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.cosend.app/mcp |
| Authorisation server | https://auth.cosend.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.cosend.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.cosend.app/mcp | HTTPS enforced | 301 | https://mcp.cosend.app/mcp |
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 →
test_automation Test an automation on a sample customer ~188
Runs the newest version of an automation once on a sample customer as a dry run: each step is recorded as what it would have done, and every message stays inside the test. payload lays trigger fields over the sample; fail_step runs the error branch as if that step had failed. Returns the run, whose steps are read through the run tools. It uses one automation run if it starts. A version that cannot be tested is refused in words.
| Name | Type | Req | Description |
|---|---|---|---|
| fail_step | string | – | Optional. The id of a step: the test runs the error branch as if that step had failed, and shows what the branch would do. Refused when the automation has no error branch or no such step. |
| id | string | yes | The automation id. |
| payload | object | – | Optional. Trigger subtrees (`message`, `order`, …) laid over the sample's, field by field. |
No output schema declared.
No examples provided.
try_assistant Try the AI assistant ~507
Asks one AI assistant (automation_id) a customer’s question and returns what it would do: its reply, the intent and confidence it read, the knowledge sources it used, whether it would hand the chat to a person, and the message a customer would receive. The trial stays inside Cosend, out of customers’ view. Each chat is one AI conversation on the plan, counted when the assistant is first asked in it; send the chat_id an answer returns, with history, to continue the same chat. For an assistant that is switched off, connection_id with holding_message (and escalate_keywords or closed hours) tries it with the set-up’s answers. Owners and admins.
| Name | Type | Req | Description |
|---|---|---|---|
| automation_id | string | yes | The AI assistant being tried: an automation of this workspace with one AI step. The answer comes from its own persona and knowledge, and from no other assistant’s. Alone, the try also uses the escala… |
| chat_id | – | – | The Try it chat this message continues: the chat_id an earlier answer in it gave. Each chat counts as one AI conversation, billed like a real one, from the first time the assistant is asked in it. Nu… |
| closed | object | – | With connection_id: the set-up's closed message, opening hours (HH:MM, in the workspace's timezone) and closed-hours passing message. While closed, the answer's closed_message is the message with the… |
| connection_id | string | – | For a receptionist that is not switched on: the number it is being set up on. Requires holding_message; escalate_keywords and closed as the set-up has them. They replace the settings of automation_id… |
| escalate_keywords | array | – | With connection_id: the words that pass a chat to a person. |
| history | array | – | – |
| holding_message | string | – | Required with connection_id, and only with it: the message a customer is sent when the assistant cannot answer. |
| message | string | yes | – |
No output schema declared.
No examples provided.
update_accurate_warehouse_arrival Change “Warehouse arrival message” settings ~276
Changes the settings of an automation set up from Cosend’s “Warehouse arrival message” recipe, named by id, as its settings page in Cosend does: the settings given replace their values, the rest keep theirs, and the result is saved as a new version. If the automation is switched on, the new settings go live with the save, or the save is refused in words and it keeps running what it ran; if it is off, they wait for it to be switched on. An automation from another recipe, or one written by hand, is refused. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the new version.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it. |
| id | string | yes | The automation set up from the “Warehouse arrival message” recipe whose settings change. |
| settings | object | yes | The settings to change, as the recipe’s settings form asks them. A setting left out keeps the value it has. |
No output schema declared.
No examples provided.
update_ai_receptionist Change “AI receptionist” settings ~271
Changes the settings of an automation set up from Cosend’s “AI receptionist” recipe, named by id, as its settings page in Cosend does: the settings given replace their values, the rest keep theirs, and the result is saved as a new version. If the automation is switched on, the new settings go live with the save, or the save is refused in words and it keeps running what it ran; if it is off, they wait for it to be switched on. An automation from another recipe, or one written by hand, is refused. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the new version.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it. |
| id | string | yes | The automation set up from the “AI receptionist” recipe whose settings change. |
| settings | object | yes | The settings to change, as the recipe’s settings form asks them. A setting left out keeps the value it has. |
No output schema declared.
No examples provided.
update_appointment_reminder Change “Appointment reminder” settings ~271
Changes the settings of an automation set up from Cosend’s “Appointment reminder” recipe, named by id, as its settings page in Cosend does: the settings given replace their values, the rest keep theirs, and the result is saved as a new version. If the automation is switched on, the new settings go live with the save, or the save is refused in words and it keeps running what it ran; if it is off, they wait for it to be switched on. An automation from another recipe, or one written by hand, is refused. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the new version.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it. |
| id | string | yes | The automation set up from the “Appointment reminder” recipe whose settings change. |
| settings | object | yes | The settings to change, as the recipe’s settings form asks them. A setting left out keeps the value it has. |
No output schema declared.
No examples provided.
update_assistant_persona Change the AI assistant’s persona ~246
Changes the persona of one AI assistant, named by id. Only the fields sent change; a list (links, never_say) is the whole new list. The persona is set through typed fields: business_name, what_you_do, tone, may_quote_prices, links, never_say and confidence_threshold. Each change needs a confirmed call: without confirmation_token the call is a preview that returns what would happen and a token for a person to approve; called again with that token, it saves. When the assistant is switched on, customers meet the new persona at their next message. Owners and admins.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | – | – |
| confidence_threshold | number | – | – |
| confirmation_token | string | – | For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it. |
| id | string | yes | The id in the resource path. |
| links | array | – | – |
| may_quote_prices | boolean | – | – |
| never_say | array | – | – |
| tone | string | – | – |
| what_you_do | string | – | – |
No output schema declared.
No examples provided.
update_automation_details Rename an automation ~146
Changes an existing automation’s name or description, and nothing else: what it does and its settings stay as they are. connection_id puts an automation made before numbers, which runs on every number, on one WhatsApp number, once; one that has a number keeps it. Returns the automation.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | – | – | The WhatsApp number for an automation that has none and runs on every number. Accepted once; an automation that has a number keeps it, and another one (or null) is refused. The value it already has,… |
| description | – | – | – |
| id | string | yes | The automation id. |
| name | string | – | – |
No output schema declared.
No examples provided.
update_campaign Change a campaign draft ~365
Saves one or more steps of a campaign draft, named by id, and returns it. A step is its name; its number; its template (template_id, a marketing template on that number’s WhatsApp account); the value of each blank (variable_map: a contact field’s key, first_name or name, with fallback text for people who have none, or one text for everyone); what the template shows on top (header: a picture, video or document uploaded to Cosend by its media_id, and the template’s own file when none is chosen; a place by its latitude, longitude, name and address; or the title’s blanks, as variable_map); the value of a link button’s blank and a coupon code (buttons, by the button’s index); its audience, which is a saved audience by its id (audience.segment_id) and nothing else; a time to send it, in a time zone; and its quiet hours, when nothing is sent. Changing the number clears the template and the blanks. A scheduled campaign that is changed is a draft again, and any estimate it had is cleared. It sends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| ab | – | – | – |
| audience | object | – | – |
| buttons | array | – | – |
| cards | array | – | – |
| connection_id | string | – | – |
| header | – | – | – |
| id | string | yes | The id in the resource path. |
| kind | string | – | – |
| let_join | boolean | – | – |
| name | string | – | – |
| quiet_hours | object | – | – |
| reply_rules | array | – | – |
| schedule | – | – | – |
| steps | array | – | – |
| template_id | – | – | – |
| track_clicks | boolean | – | – |
| variable_map | array | – | – |
No output schema declared.
No examples provided.
update_contact Edit a contact ~335
Changes one contact, named by id, by whichever of these are given: name (the name the business sets, which shows first; null goes back to the WhatsApp names; owners and admins only), attributes (field values by key), tags (the whole list, replacing the old one), locale, timezone, and is_blocked (true blocks the contact on their number so nothing is sent to them and their messages are not answered; false unblocks; owners and admins only). The change stays inside Cosend, out of the contact’s view. Returns the contact.
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | object | – | Free-form values. PATCH replaces them whole; a POST for a contact that already exists writes the keys sent over its values and removes none. A key registered in /v1/contact-fields must hold a value o… |
| connection_id | string | – | – |
| id | string | yes | The id in the resource path. |
| is_blocked | boolean | – | – |
| locale | – | – | – |
| name | – | – | – |
| profile_name | – | – | – |
| tags | array | – | – |
| timezone | – | – | – |
No output schema declared.
No examples provided.
update_conversation Update a conversation ~175
Changes one conversation, named by id, by whichever of these are given: assignee_id (a member’s usr_ id; null takes the assignee off), snoozed_until (a time; null ends the snooze), labels (the whole list of labels, replacing the old one), priority, and state. state resolved marks the chat Done, as the Done button does: nobody holds it afterwards and every automation on that number treats the customer’s next message as a first message. The change stays inside Cosend, out of the customer’s view. Returns the conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_id | – | – | – |
| id | string | yes | The id in the resource path. |
| labels | array | – | – |
| priority | string | – | – |
| snoozed_until | – | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
update_custom_automation Save a new version of an automation ~381
Saves a new version of one automation, named by id, from an automation document (ir) written in full, as Cosend’s automation editor saves one: what it starts on, its steps and its limits, in the document schema that ir_version names. What a document can use on a number, each trigger, step and integration action with what it takes, and that schema itself, are in the read-only list of automation building blocks for the number. The document is checked as it is saved; one that does not pass is refused with each failing path as a JSON pointer. A “Run a script” step runs TypeScript written in the step, in a sandbox with no network and nothing imported; an outside address is reached only by a step that calls an allowlisted URL. A document marked as made from a recipe (meta.created_by "recipe") is refused: a recipe is set up and changed with its own tools. The automation keeps running the version it ran until the new one is deployed and switched on. Each call needs confirming: without confirmation_token it changes nothing and returns a preview naming every action the document’s steps take, and a token for a person to approve; called again with that token, it saves. Returns the new version.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it. |
| id | string | yes | The id in the resource path. |
| ir | object | yes | The automation’s flow document (the IR), as a JSON object. `ir_version` selects the document schema Cosend validates it against. A document that does not match is refused with `automation_invalid`, w… |
No output schema declared.
No examples provided.
update_lead_capture Change “Lead capture from ads” settings ~274
Changes the settings of an automation set up from Cosend’s “Lead capture from ads” recipe, named by id, as its settings page in Cosend does: the settings given replace their values, the rest keep theirs, and the result is saved as a new version. If the automation is switched on, the new settings go live with the save, or the save is refused in words and it keeps running what it ran; if it is off, they wait for it to be switched on. An automation from another recipe, or one written by hand, is refused. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the new version.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it. |
| id | string | yes | The automation set up from the “Lead capture from ads” recipe whose settings change. |
| settings | object | yes | The settings to change, as the recipe’s settings form asks them. A setting left out keeps the value it has. |
No output schema declared.
No examples provided.
update_missed_call_text_back Change “Missed call text-back” settings ~278
Changes the settings of an automation set up from Cosend’s “Missed call text-back” recipe, named by id, as its settings page in Cosend does: the settings given replace their values, the rest keep theirs, and the result is saved as a new version. If the automation is switched on, the new settings go live with the save, or the save is refused in words and it keeps running what it ran; if it is off, they wait for it to be switched on. An automation from another recipe, or one written by hand, is refused. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the new version.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it. |
| id | string | yes | The automation set up from the “Missed call text-back” recipe whose settings change. |
| settings | object | yes | The settings to change, as the recipe’s settings form asks them. A setting left out keeps the value it has. |
No output schema declared.
No examples provided.
update_number Change a number’s settings or profile ~496
Changes one WhatsApp number, named by id. action settings takes delivery_mode (stored or direct) and override_callback_url (where Meta’s webhooks for the number go; null clears it). action display_name takes display_name and submits it to Meta’s review; Meta’s decision shows on the number later. action profile takes any of about, description, address, email, websites, vertical and profile_picture (a media id from an upload on this number); every customer sees the profile. Each action needs a confirmed call: without confirmation_token the call is a preview that names the number and returns a token for a person to approve. The number’s webhook verify token and relay secret stay sealed in the number’s settings in the Cosend dashboard, and read as null here. Owners and admins.
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | – | – |
| action | string | yes | settings changes how Meta’s messages for the number are handled. display_name submits a new name to Meta’s review. profile edits the business profile customers see. |
| address | – | – | – |
| confirmation_token | string | – | For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it. |
| delivery_mode | string | – | – |
| description | – | – | – |
| display_name | string | – | – |
| – | – | – | |
| id | string | yes | The id in the resource path. |
| override_callback_url | – | – | Your endpoint for Meta’s webhooks for this number. On a `direct` number Cosend sets it as the number’s webhook override at Meta, and Meta sends the number’s messages, echoes, calls and history to it… |
| profile_picture | object | – | – |
| retention_months | – | – | Retention is set once for the whole account, not per connection. Set it with PATCH /v1/account/data-policy. |
| vertical | – | – | – |
| websites | array | – | – |
No output schema declared.
No examples provided.
update_order_confirmation Change “Order confirmation” settings ~269
Changes the settings of an automation set up from Cosend’s “Order confirmation” recipe, named by id, as its settings page in Cosend does: the settings given replace their values, the rest keep theirs, and the result is saved as a new version. If the automation is switched on, the new settings go live with the save, or the save is refused in words and it keeps running what it ran; if it is off, they wait for it to be switched on. An automation from another recipe, or one written by hand, is refused. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the new version.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it. |
| id | string | yes | The automation set up from the “Order confirmation” recipe whose settings change. |
| settings | object | yes | The settings to change, as the recipe’s settings form asks them. A setting left out keeps the value it has. |
No output schema declared.
No examples provided.
update_order_updates Change “Shipping and cancellation updates” settings ~273
Changes the settings of an automation set up from Cosend’s “Shipping and cancellation updates” recipe, named by id, as its settings page in Cosend does: the settings given replace their values, the rest keep theirs, and the result is saved as a new version. If the automation is switched on, the new settings go live with the save, or the save is refused in words and it keeps running what it ran; if it is off, they wait for it to be switched on. An automation from another recipe, or one written by hand, is refused. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the new version.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it. |
| id | string | yes | The automation set up from the “Shipping and cancellation updates” recipe whose settings change. |
| settings | object | yes | The settings to change, as the recipe’s settings form asks them. A setting left out keeps the value it has. |
No output schema declared.
No examples provided.
update_payment_reminder Change “Payment reminder” settings ~270
Changes the settings of an automation set up from Cosend’s “Payment reminder” recipe, named by id, as its settings page in Cosend does: the settings given replace their values, the rest keep theirs, and the result is saved as a new version. If the automation is switched on, the new settings go live with the save, or the save is refused in words and it keeps running what it ran; if it is off, they wait for it to be switched on. An automation from another recipe, or one written by hand, is refused. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the new version.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it. |
| id | string | yes | The automation set up from the “Payment reminder” recipe whose settings change. |
| settings | object | yes | The settings to change, as the recipe’s settings form asks them. A setting left out keeps the value it has. |
No output schema declared.
No examples provided.
update_quote_intake Change “Quote requests” settings ~270
Changes the settings of an automation set up from Cosend’s “Quote requests” recipe, named by id, as its settings page in Cosend does: the settings given replace their values, the rest keep theirs, and the result is saved as a new version. If the automation is switched on, the new settings go live with the save, or the save is refused in words and it keeps running what it ran; if it is off, they wait for it to be switched on. An automation from another recipe, or one written by hand, is refused. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the new version.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it. |
| id | string | yes | The automation set up from the “Quote requests” recipe whose settings change. |
| settings | object | yes | The settings to change, as the recipe’s settings form asks them. A setting left out keeps the value it has. |
No output schema declared.
No examples provided.
update_review_request Change “Review request” settings ~269
Changes the settings of an automation set up from Cosend’s “Review request” recipe, named by id, as its settings page in Cosend does: the settings given replace their values, the rest keep theirs, and the result is saved as a new version. If the automation is switched on, the new settings go live with the save, or the save is refused in words and it keeps running what it ran; if it is off, they wait for it to be switched on. An automation from another recipe, or one written by hand, is refused. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the new version.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it. |
| id | string | yes | The automation set up from the “Review request” recipe whose settings change. |
| settings | object | yes | The settings to change, as the recipe’s settings form asks them. A setting left out keeps the value it has. |
No output schema declared.
No examples provided.
update_welcome_menu Change “Welcome and away menu” settings ~274
Changes the settings of an automation set up from Cosend’s “Welcome and away menu” recipe, named by id, as its settings page in Cosend does: the settings given replace their values, the rest keep theirs, and the result is saved as a new version. If the automation is switched on, the new settings go live with the save, or the save is refused in words and it keeps running what it ran; if it is off, they wait for it to be switched on. An automation from another recipe, or one written by hand, is refused. Each call needs confirming: without confirmation_token it changes nothing and returns a preview with the settings as Cosend filled them in and its check of them, and a token for a person to approve; called again with that token, it saves. Returns the new version.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_token | string | – | For a call that needs approval: left out, the call does nothing and returns a preview and a token; given that token, with the same arguments, the call does it. |
| id | string | yes | The automation set up from the “Welcome and away menu” recipe whose settings change. |
| settings | object | yes | The settings to change, as the recipe’s settings form asks them. A setting left out keeps the value it has. |
No output schema declared.
No examples provided.
upload_media Upload a file ~378
Uploads one file to a WhatsApp number’s media library and returns its media id (med_…), which a message, the number’s profile picture or the AI assistant’s knowledge then takes. The file travels inline as data_base64 with its mime_type, and goes to Meta and to Cosend’s storage in one call. Through an AI app a file is up to 5 MB; a larger video, audio file or document is uploaded in the Cosend dashboard. mime_type decides how WhatsApp sends it: image (jpeg, png), video (mp4, 3gpp), audio (aac, amr, mpeg, mp4, ogg), document (pdf, plain text, Word, Excel and PowerPoint) or sticker (webp). A type WhatsApp does not take, or a file over the limit, is refused before anything is stored. Every upload is its own file on that number, even with the same bytes. The file waits in the media library until a message, the profile or the assistant’s knowledge uses it.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | string | yes | – |
| data_base64 | string | yes | – |
| filename | – | – | – |
| mime_type | string | yes | One of the types WhatsApp accepts, which also decides how the file is sent: image (image/jpeg, image/png; 5 MB), video (video/mp4, video/3gpp; 16 MB), audio (audio/aac, audio/amr, audio/mpeg, audio/m… |
No output schema declared.
No examples provided.
upsert_contact Create or update a contact ~388
Creates a contact, or updates the one that already exists for that phone number or BSUID (the business-scoped user id Meta sends; a contact may have one and no phone). On a contact that exists only the fields you send change, and nothing is removed: tags are added to its tags, attributes are merged into its attributes, changing the name needs an owner or admin, and profile_name is only filled when WhatsApp has not given one; a field sent as null is left as it is. Writes only to Cosend: it sends nothing and the contact is not notified. Who can be messaged stays the same: a send needs no opt-in, only an opt-out stops one, and opt-outs are recorded on their own ledger.
| Name | Type | Req | Description |
|---|---|---|---|
| attributes | object | – | Free-form values. PATCH replaces them whole; a POST for a contact that already exists writes the keys sent over its values and removes none. A key registered in /v1/contact-fields must hold a value o… |
| bsuid | – | – | – |
| connection_id | string | yes | – |
| locale | – | – | – |
| name | – | – | – |
| phone_e164 | – | – | – |
| profile_name | – | – | – |
| tags | array | – | A new contact gets these tags. A contact that already exists gets them added to its own, and keeps every tag it has. |
| timezone | – | – | – |
No output schema declared.
No examples provided.
validate_automation Check an automation ~129
Checks an automation document (ir) with Cosend’s compiler and returns its full report: every error with a JSON pointer into the document and, where one exists, a fix that can be applied. Nothing is written and nothing is deployed. id is the automation the draft belongs to; a brand-new automation gets its id when it is first saved, and saving checks the document the same way. It needs the automations:write permission because it is the authoring tool, though it changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id in the resource path. |
| ir | object | yes | – |
No output schema declared.
No examples provided.
whatsapp_link Make a WhatsApp chat link ~240
Makes a wa.me chat link and its QR code (an SVG image) for a WhatsApp number, with an opening message if one is given. country is the two-letter ISO code and number is the number exactly as it is typed in that country (as written at home, with +, with 00 or with the country code in front); a number of another country is refused. It sends nothing to anyone.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | The country the number belongs to, as its two-letter ISO code: "GB", "US", "DE". A number of another country is refused. |
| message | string | – | The message the chat starts with, at most 500 characters. Left out or blank, the link opens an empty chat. |
| number | string | yes | The WhatsApp number as people type it: as written at home (07700 900123), with + (+44 7700 900123), with 00 (0044 7700 900123) or with the country code in front (44 7700 900123). Spaces, dashes, brac… |
No output schema declared.
No examples provided.
whoami Who am I ~74
Returns the Cosend workspace, plan and connected WhatsApp numbers for the credential in use, and the permissions it was granted, which decide which tools the credential can call and show which WhatsApp business number an outbound message would come from. Read-only and cheap. It does not fail for permission reasons if the credential resolves at all.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Cosend MCP server?
Cosend is a hosted endpoint at https://mcp.cosend.app/mcp, 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.cosend.app
claude mcp add --transport http app-cosend-mcp 'https://mcp.cosend.app/mcp'
What is the Cosend MCP server?
Cosend is an MCP server listed in the public MCP registry as app.cosend/mcp. WhatsApp Business inbox for AI apps: read and answer chats, run campaigns, deploy automations. This page covers its hosted endpoint (https://mcp.cosend.app/mcp).
Is the Cosend MCP server safe to use?
Cosend scores 84 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 Cosend MCP server expose?
Cosend exposes 125 tools: whoami, list_conversations, search_conversations, read_conversation, send_message, and 120 more. Their descriptions and schemas cost roughly 29,877 tokens of context every time the server is loaded.
Does the Cosend MCP server require authentication?
Yes. Cosend 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 Cosend MCP server still maintained?
Cosend 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 Cosend MCP server?
VerifyMCP ran 13 checks on Cosend, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.