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.

Send16

REMOTE · MCP.SEND16.COM

Email, SMS and marketing automation: campaigns, contacts, automations and stats from Claude.

Available components

−39 this week 34 Trust /100

Last scanned (13 hours ago)

Scores higher than 18% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Marketing and SEO

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 Security86
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 (4)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC

Checks we could not complete (7)

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.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.
  • 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.

  • 30 Oct 26 −39
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Stability: 0.03 → unverified ▼ security
    • Authorization: fail → pass ▲ security
    • First check of Authorization: pass security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 29 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 28 Oct 26 73

    First indexed and scored.

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

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.send16.com CN=YE2,O=Let's Encrypt,C=US 25 Oct 2026 23 Jan 2027 ECDSA 256 ECDSA-SHA384 66467fe7214230765fea95f18390e976505
SANs: *.send16.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.send16.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
send16.com. 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 connection
HTTP status 401

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.send16.com/.well-known/oauth-protected-resource", scope="read write"

Bearer resource_metadata="https://mcp.send16.com/.well-known/oauth-protected-resource", scope="read write"
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
www-authenticate Bearer resource_metadata="https://mcp.send16.com/.well-known/oauth-protected-resource", scope="read write"

Protected resource metadata

Document https://mcp.send16.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.send16.com
Authorisation server https://api.send16.com

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.send16.com Auth required 401
http (plaintext) http://mcp.send16.com Inconclusive 401
MCP tools · 87 exposed · ~9,019 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
list_messages ~153

List messages from the unified send log (transactional + campaign). Filter by recipient, sender, status, date range, or source.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
created_afterstring–ISO-8601 timestamp lower bound
created_beforestring–ISO-8601 timestamp upper bound
from_emailstring–Sender email filter
limitinteger–Page size (default 50)
offsetinteger–Page offset
sourcestring–Restrict to one message source
statusstring–Delivery status filter
to_emailstring–Recipient email filter

No output schema declared.

No examples provided.

list_segments ~46

List dynamic segments. Segments compute their members from a filter expression at send time.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)

No output schema declared.

No examples provided.

list_suppressions ~68

List suppressed email addresses (bounces, complaints, unsubscribes, manual).

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
limitinteger––
offsetinteger––
reasonstring––

No output schema declared.

No examples provided.

list_templates ~39

List starter-gallery email templates available to every workspace.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)

No output schema declared.

No examples provided.

list_topics ~70

List subscription topics. Topics are granular categories contacts can subscribe to (e.g. 'product-updates', 'weekly-digest'). Campaigns and automations can be gated to subscribers of a specific topic.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)

No output schema declared.

No examples provided.

list_webhooks ~56

List configured outgoing webhooks (your endpoints that Send16 POSTs delivery events to). Outgoing webhooks are a plan feature.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)

No output schema declared.

No examples provided.

list_workspace_templates ~62

List the templates saved in the user's own Send16 workspace (their template library, including ones saved with save_template). For the shared starter gallery use list_templates.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)

No output schema declared.

No examples provided.

list_workspaces ~44

List workspaces the authenticated user has access to (owner or member).

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)

No output schema declared.

No examples provided.

mark_convo_read ~51

Mark a conversation as read for the current viewer.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
convoIdstringyesConversation ID

No output schema declared.

No examples provided.

pause_automation ~56

Pause an automation. Existing enrollments freeze in place; no new contacts enroll.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
automationIdstringyesAutomation ID

No output schema declared.

No examples provided.

pause_campaign ~55

Pause a sending campaign. Already-sent messages are unaffected; remaining sends halt.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
campaignIdstringyesCampaign ID

No output schema declared.

No examples provided.

pre_send_review ~101

Run an AI pre-send review on an email's HTML before sending. Surfaces tone issues, broken links, missing alt text, spam triggers, and accessibility problems.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
audiencestring–Short description of the audience (helps tone analysis)
htmlstringyesFull HTML body to review
subjectstringyesEmail subject line

No output schema declared.

No examples provided.

preview_campaign_recipients ~58

Preview the recipient set for a campaign before sending. Returns count + sample list.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
campaignIdstringyesCampaign ID

No output schema declared.

No examples provided.

preview_segment ~49

Preview the contacts that match a segment without sending.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
segmentIdstringyesSegment ID

No output schema declared.

No examples provided.

regenerate_webhook_secret ~60

Rotate the HMAC signing secret for an outgoing webhook endpoint. Returns the new secret once.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
webhookIdstringyesWebhook ID

No output schema declared.

No examples provided.

register_for_event ~153

Register someone for an event. They get the event's confirmation email with their QR ticket unless the organiser switched it off, so confirm the person and the event with the user first. Registering doesn't subscribe them to marketing unless marketingOptIn is true because they asked.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
citystring––
companystring––
emailstringyes–
eventIdstringyesEvent ID (see list_events)
firstNamestring––
lastNamestring––
marketingOptInboolean–Only when the person asked to hear about future events

No output schema declared.

No examples provided.

remove_contact_from_audience ~59

Remove a contact from an audience.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
audienceIdstringyesAudience ID
contactIdstringyesContact ID

No output schema declared.

No examples provided.

remove_suppression ~59

Remove an email from the suppression list. Use only when you've confirmed the recipient wants to receive mail again.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
emailstringyes–

No output schema declared.

No examples provided.

render_email_content ~108

Compile an EmailContent JSON object (the shape used by the Send16 builder + templates) into HTML using the platform's authoritative renderer. Returns the exact HTML the API would send. Useful for previews and post-processing.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
contentobjectyesEmailContent JSON (from get_template or the builder)
variablesobject–Variable replacements (e.g. {firstName:'Alice'})

No output schema declared.

No examples provided.

resume_campaign ~72

Resume a paused campaign. Confirm with the user first: the remaining recipients start receiving the campaign straight away. The sending limits and pauses described on schedule_campaign still apply.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
campaignIdstringyesCampaign ID

No output schema declared.

No examples provided.

save_template ~359

Save an email design as a reusable template in the user's Send16 workspace. Use this when the user has designed an email (for example in a Claude artifact) and wants it in Send16. Pass the complete email HTML. Send16 hosts every image (remote URLs and inline data: images), converts merge tags like {{first_name}} to Send16's format, and stores the HTML exactly as designed. For best results across Gmail, Outlook and Apple Mail the HTML should be email-safe: table-based layout around 600px wide, inline styles, PNG/JPG/GIF images in <img> tags (not SVG or CSS backgrounds), web-safe font fallbacks, and alt text on images. Returns the template id; follow up with send_template_test to send a preview.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
categorystring–Library category, e.g. newsletter, onboarding, announcement, ecommerce, transactional. Defaults to custom.
convertMergeTagsboolean–Convert common merge tags ({{first_name}}, *|FNAME|*) to Send16 tags (default true)
descriptionstring–Short description shown in the template library
hostImagesboolean–Copy every image onto Send16 hosting so it can't break later (default true)
htmlstringyesThe complete email HTML (a full <html> document or a body fragment)
modestring–hybrid (default): keep the exact HTML, convertible to editable blocks later. html: exact HTML only. blocks: convert to editable builder blocks now (lossy for complex designs).
namestringyesTemplate name, e.g. 'October newsletter'

No output schema declared.

No examples provided.

schedule_campaign ~326

Schedule (or send immediately) an existing draft campaign to an audience/segment/topic. Before calling, confirm with the user: show them the recipients (or the recipient count), the sender and the subject, and wait for a clear yes. Send16 can refuse a send. 429 SEND_RAMP_LIMIT: new and free workspaces have hourly and daily sending limits while they build reputation; the error details give the window, the limit and how many remain. Tell the user how many can go now and that the rest can go once the window resets (or after upgrading), and do not split the send or retry in a loop to get around it. 403 SENDING_PAUSED: sending from the workspace is paused while the Send16 team reviews it. Nothing was sent. Tell the user to check the workspace owner's email or contact support, and do not retry. 422 MESSAGE_NEEDS_REVIEW: the content looked like it might be impersonating a government agency, bank, toll operator or delivery company, so it was held and not sent. Tell the user it is held for review and they can contact support if it is legitimate. Do not reword it and try again; repeated flags pause the workspace.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
audienceIdstring––
campaignIdstringyesCampaign ID
scheduleAtstring–ISO-8601 future datetime; omit to send immediately
segmentIdstring––
topicIdstring––

No output schema declared.

No examples provided.

screener_decide ~83

Decide a pending screener conversation (first-time sender). 'allow' lets future emails through, 'reject' blocks, 'cold' marks as cold outreach.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
convoIdstringyesConversation ID
decisionstringyesScreener decision

No output schema declared.

No examples provided.

search_contacts ~90

Search contacts by email address or name. Returns matching contacts with their tags and subscription status.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
pageinteger–Page number
pageSizeinteger–Results per page (max 100)
querystringyesSearch query (matches against email, first name, last name)

No output schema declared.

No examples provided.

send_broadcast ~447

One-shot broadcast: create a campaign and immediately schedule it to send, in a single call. Pass either an audienceId, segmentId, topicId, or fully-qualified filter. Provide html OR templateSlug. Before calling, confirm with the user: show them the recipients (or the recipient count), the sender and the subject, and wait for a clear yes. Send16 can refuse a send. 429 SEND_RAMP_LIMIT: new and free workspaces have hourly and daily sending limits while they build reputation; the error details give the window, the limit and how many remain. Tell the user how many can go now and that the rest can go once the window resets (or after upgrading), and do not split the send or retry in a loop to get around it. 403 SENDING_PAUSED: sending from the workspace is paused while the Send16 team reviews it. Nothing was sent. Tell the user to check the workspace owner's email or contact support, and do not retry. 422 MESSAGE_NEEDS_REVIEW: the content looked like it might be impersonating a government agency, bank, toll operator or delivery company, so it was held and not sent. Tell the user it is held for review and they can contact support if it is legitimate. Do not reword it and try again; repeated flags pause the workspace.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
audienceIdstring–Send to all contacts in this audience
fromEmailstringyesMust be a verified domain
fromNamestringyes–
htmlstring–Full HTML body (one of html/templateSlug required)
namestringyesInternal campaign name
previewTextstring––
replyTostring––
scheduleAtstring–ISO-8601 future datetime; omit to send immediately
segmentIdstring–Send to all contacts matching this segment
subjectstringyes–
templateSlugstring–Workspace template slug to use
topicIdstring–Send to all subscribers of this topic

No output schema declared.

No examples provided.

send_campaign_test ~114

Send a test email for an existing campaign to preview how it will look in recipients' inboxes. Confirm the test address with the user first. Can be refused with 403 SENDING_PAUSED (workspace under review, nothing was sent, tell the user to contact support).

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
campaignIdstringyesCampaign ID to send test for
testEmailstringyesEmail address to send the test to

No output schema declared.

No examples provided.

send_email ~501

Send a transactional email through Send16. Provide `html`, `text`, or both (text-only is fine for OTPs/receipts/alerts). `from_email` must belong to a domain that is verified in the workspace; call `whoami` for the account and `list_domains` to see which senders are allowed; a send from an unverified domain returns a clear error, not a silent failure. For a zero-setup first send, use from_email `onboarding@send16.com`; the sandbox sender delivers with no DNS, but only to your own account email. Before calling, confirm with the user: show them the recipients (or the recipient count), the sender and the subject, and wait for a clear yes. Send16 can refuse a send. 429 SEND_RAMP_LIMIT: new and free workspaces have hourly and daily sending limits while they build reputation; the error details give the window, the limit and how many remain. Tell the user how many can go now and that the rest can go once the window resets (or after upgrading), and do not split the send or retry in a loop to get around it. 403 SENDING_PAUSED: sending from the workspace is paused while the Send16 team reviews it. Nothing was sent. Tell the user to check the workspace owner's email or contact support, and do not retry. 422 MESSAGE_NEEDS_REVIEW: the content looked like it might be impersonating a government agency, bank, toll operator or delivery company, so it was held and not sent. Tell the user it is held for review and they can contact support if it is legitimate. Do not reword it and try again; repeated flags pause the workspace.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
from_emailstring–Sender email address (must be from a verified domain)
from_namestring–Sender display name (e.g. "Acme Co")
htmlstring–HTML body content
reply_tostring–Reply-to email address
subjectstringyesEmail subject line
templatestring–Transactional template slug to use instead of inline content
textstring–Plain text body content
to–yesRecipient email address or array of addresses (max 50)
variablesobject–Template variables for merge tags

No output schema declared.

No examples provided.

send_event ~180

Fire a custom event for a contact. Automations whose trigger is `{type:'custom_event', eventName:'<name>'}` will enroll the contact and start running. Payload is exposed to condition steps as `event.<key>`. Confirm with the user first if the event could start an automation that emails the contact.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
contactEmailstring–Contact email (provide either this or contactId)
contactIdstring–Contact UUID (provide either this or contactEmail)
namestringyesEvent name (e.g. 'trial_started', 'order.placed')
occurredAtstring–ISO-8601 timestamp; defaults to now
payloadobject–Arbitrary JSON metadata available to automation conditions

No output schema declared.

No examples provided.

send_reply ~145

Reply to an inbox conversation. The reply is sent from the original recipient address (the alias the convo arrived on) and threaded back to the contact. Show the user the reply text and get a clear yes first: it goes to a real person and cannot be unsent. Can be refused with 403 SENDING_PAUSED (workspace under review, nothing was sent, tell the user to contact support).

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
convoIdstringyesConversation ID
htmlstring–HTML body of the reply
textstring–Plain text body of the reply

No output schema declared.

No examples provided.

send_template_test ~159

Send a preview of a saved workspace template to one email address, so the user can see it in a real inbox. It arrives from noreply@send16.com with a small 'Template test preview' banner and uses sample merge values (first name 'Test'). Only send to the user's own address unless they ask otherwise. Confirm the test address with the user first. Can be refused with 403 SENDING_PAUSED (workspace under review, nothing was sent, tell the user to contact support).

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
emailstringyesWhere to send the preview
templateIdstringyesTemplate id from save_template or list_workspace_templates

No output schema declared.

No examples provided.

update_action ~99

Update an Action (toggle enabled, change template, change event name).

NameTypeReqDescription
actionIdstringyesAction ID
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
delaySecondsinteger––
enabledboolean––
eventNamestring––
namestring––
sendOnceboolean––
templateSlugstring––

No output schema declared.

No examples provided.

update_brand ~212

Update workspace brand settings. The designSpec field is a Markdown DESIGN.md document fed into AI generation system prompts; use it to encode voice, do/don't lists, and visual rules. companyName/websiteUrl/companyAddress also fill the matching merge tags in templates.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
companyAddressstring–Physical postal address. Fills {{companyAddress}} and is appended to the unsubscribe footer on campaigns lacking one; required by anti-spam law in several markets.
companyNamestring–Fills {{companyName}}
designSpecstring–Markdown DESIGN.md spec for AI generation
fontFamilystring–Body font family
logoUrlstring––
primaryColorstring–Hex color (e.g. '#4F46E5')
secondaryColorstring–Hex color
websiteUrlstring–Fills {{websiteUrl}}

No output schema declared.

No examples provided.

update_campaign ~250

Update a draft campaign: name, subject, preview text, sender info, HTML content, and/or recipients. Retarget with exactly ONE of audienceIds / segmentId / contactIds / tagIds / sendToAll, then verify with preview_campaign_recipients before sending. Only drafts can be edited.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
audienceIdsarray–Retarget to these audience IDs (see list_audiences). Sets recipient type 'lists'.
campaignIdstringyesCampaign ID
contactIdsarray–Retarget to these specific contact IDs
fromEmailstring––
fromNamestring––
htmlstring––
namestring–Campaign name (internal label)
previewTextstring––
replyTostring––
segmentIdstring–Retarget to this segment (see list_segments)
sendToAllboolean–Retarget to all subscribed contacts in the workspace
subjectstring––
tagIdsarray–Retarget to contacts with these tag IDs

No output schema declared.

No examples provided.

update_contact ~84

Update a contact's profile fields, custom fields, or subscription state.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
contactIdstringyesContact ID
customFieldsobject––
firstNamestring––
lastNamestring––
subscribedboolean––

No output schema declared.

No examples provided.

update_convo ~88

Update conversation status (open/closed/archived/snoozed) or assignee.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
assigneeIdstring|null–Workspace member user ID, or null to unassign
convoIdstringyesConversation ID
statestring–New status

No output schema declared.

No examples provided.

update_topic ~72

Update a subscription topic (name, description, default).

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)
descriptionstring––
isDefaultboolean––
namestring––
topicIdstringyesTopic ID

No output schema declared.

No examples provided.

whoami ~78

Verify the API key and return the authenticated workspace: name, plan, email quota (used/limit), and owner. Call this first to confirm the key works before sending. Pair with list_domains to see which `from` addresses are allowed.

NameTypeReqDescription
apiKeystring–Send16 API key (overrides SEND16_API_KEY env var)

No output schema declared.

No examples provided.

Install

How do I install the Send16 MCP server?

Send16 is a hosted endpoint at https://mcp.send16.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.send16.com

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

What is the Send16 MCP server?

Send16 is an MCP server listed in the public MCP registry as com.send16/send16. Email, SMS and marketing automation: campaigns, contacts, automations and stats from Claude. This page covers its hosted endpoint (https://mcp.send16.com).

Is the Send16 MCP server safe to use?

Send16 scores 34 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 Send16 MCP server expose?

Send16 exposes 87 tools: whoami, send_email, send_campaign_test, create_campaign, design_email_template, and 82 more. Their descriptions and schemas cost roughly 9,019 tokens of context every time the server is loaded.

Does the Send16 MCP server require authentication?

Yes. Send16 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 Send16 MCP server still maintained?

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

VerifyMCP ran 4 checks on Send16, covering TLS certificate, Authorization, HSTS header and DNSSEC. 7 items could not be completed, a gap on our side rather than a finding about Send16: HTTPS, Transport, Schema quality, Stability and 3 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.