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.

Runearc

REMOTE · MCP.RUNEARC.COM

Email inboxes for AI agents: create an inbox, wait for the verification code, send and reply.

Available components

78 Trust /100

Last scanned (20 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Communication

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security86
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 11699 tokens (~129/item across 90 items; 90 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 Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 91% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 91 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

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 →

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 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.

  • 17 Nov 26 +2
    • Tool “add_contact” rewrote its description, which is the text the model reads security
    • Tool “create_list” rewrote its description, which is the text the model reads security
    • Tool “delete_segment” rewrote its description, which is the text the model reads security
    • Tool “delete_sync_rule” rewrote its description, which is the text the model reads security
    • Tool “goal_stats” rewrote its description, which is the text the model reads security
    • Tool “list_event_definitions” rewrote its description, which is the text the model reads security
    • Tool “list_lists” rewrote its description, which is the text the model reads security
    • Tool “popup_stats” rewrote its description, which is the text the model reads security
    • Tool “bulk_contacts” is now declared destructive security
    • Tool “cancel_campaign” is now declared destructive security
    • Tool “delete_inbox” is now declared destructive security
    • Tool “delete_page” is now declared destructive security
    • Tool “delete_segment” is now declared destructive security
    • Tool “delete_sync_rule” is now declared destructive security
    • Tool “remove_billing_integration” is now declared destructive security
    • Tool “unpublish_page” is now declared destructive security
    • Tool “unsubscribe_contact” is now declared destructive security
    • Tool “unsubscribe_contacts” is now declared destructive security
    • Stability: unverified → 0.03 ▲ functional
    • Destructive annotations: All 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • Tool “activate_sequence” changed its title: Activate sequence cosmetic
    • Tool “add_contact” changed its title: Add contact cosmetic
    • Tool “add_domain” changed its title: Add sending domain cosmetic
    • Tool “add_to_list” changed its title: Add contacts to list cosmetic
    • Tool “bulk_contacts” changed its title: Bulk update contacts cosmetic
    • Tool “cancel_campaign” changed its title: Cancel campaign cosmetic
    • Tool “connect_billing_integration” changed its title: Connect billing integration cosmetic
    • Tool “create_campaign” changed its title: Create campaign cosmetic
    • Tool “create_event_definition” changed its title: Create event definition cosmetic
    • Tool “create_form” changed its title: Create signup form cosmetic
    • Tool “create_goal” changed its title: Create goal cosmetic
    • Tool “create_inbox” changed its title: Create inbox cosmetic
    • Tool “create_list” changed its title: Create contact list cosmetic
    • Tool “create_page” changed its title: Create page cosmetic
    • Tool “create_popup” changed its title: Create popup cosmetic
    • Tool “create_segment” changed its title: Create segment cosmetic
    • Tool “create_sequence” changed its title: Create sequence cosmetic
    • Tool “create_sync_rule” changed its title: Create sync rule cosmetic
    • Tool “create_template” changed its title: Create template cosmetic
    • Tool “create_webhook” changed its title: Create webhook cosmetic
    • Tool “delete_inbox” changed its title: Delete inbox cosmetic
    • Tool “delete_page” changed its title: Delete page cosmetic
    • Tool “delete_segment” changed its title: Delete segment cosmetic
    • Tool “delete_sync_rule” changed its title: Delete sync rule cosmetic
    • Tool “draft_welcome_sequence” changed its title: Draft welcome sequence cosmetic
    • Tool “enroll_contact_in_sequence” changed its title: Enroll contact in sequence cosmetic
    • Tool “generate_email” changed its title: Generate email with AI cosmetic
    • Tool “generate_sequence” changed its title: Generate sequence with AI cosmetic
    • Tool “get_ai_context” changed its title: Get AI context cosmetic
    • Tool “get_analytics” changed its title: Get email analytics cosmetic
    • Tool “get_email_design” changed its title: Get email design cosmetic
    • Tool “get_email_tracking” changed its title: Get email tracking cosmetic
    • Tool “get_import” changed its title: Get import status cosmetic
    • Tool “get_inbox” changed its title: Get inbox cosmetic
    • Tool “get_message” changed its title: Get message cosmetic
    • Tool “get_page” changed its title: Get page cosmetic
    • Tool “get_sequence” changed its title: Get sequence cosmetic
    • Tool “get_thread” changed its title: Get thread cosmetic
    • Tool “get_tracking_settings” changed its title: Get tracking settings cosmetic
    • Tool “goal_stats” changed its title: Get goal stats cosmetic
    • Tool “import_contacts” changed its title: Import contacts from CSV cosmetic
    • Tool “import_site” changed its title: Import brand from website cosmetic
    • Tool “install_starter_sequence” changed its title: Install starter sequence cosmetic
    • Tool “list_billing_integrations” changed its title: List billing integrations cosmetic
    • Tool “list_campaign_designs” changed its title: List campaign designs cosmetic
    • Tool “list_campaigns” changed its title: List campaigns cosmetic
    • Tool “list_contact_events” changed its title: List contact events cosmetic
    • Tool “list_contacts” changed its title: List contacts cosmetic
    • Tool “list_domains” changed its title: List domains cosmetic
    • Tool “list_event_definitions” changed its title: List event definitions cosmetic
    • Tool “list_form_submissions” changed its title: List form submissions cosmetic
    • Tool “list_forms” changed its title: List signup forms cosmetic
    • Tool “list_goals” changed its title: List goals cosmetic
    • Tool “list_inboxes” changed its title: List inboxes cosmetic
    • Tool “list_lists” changed its title: List contact lists cosmetic
    • Tool “list_messages” changed its title: List messages cosmetic
    • Tool “list_pages” changed its title: List pages cosmetic
    • Tool “list_segments” changed its title: List segments cosmetic
    • Tool “list_sequences” changed its title: List sequences cosmetic
    • Tool “list_suppressions” changed its title: List suppressions cosmetic
    • Tool “list_sync_rules” changed its title: List sync rules cosmetic
    • Tool “list_templates” changed its title: List templates cosmetic
    • Tool “list_threads” changed its title: List threads cosmetic
    • Tool “pause_campaign” changed its title: Pause campaign cosmetic
    • Tool “pause_sequence” changed its title: Pause sequence cosmetic
    • Tool “popup_stats” changed its title: Get popup stats cosmetic
    • Tool “preview_segment” changed its title: Preview segment cosmetic
    • Tool “publish_page” changed its title: Publish page cosmetic
    • Tool “remove_billing_integration” changed its title: Remove billing integration cosmetic
    • Tool “render_email_preview” changed its title: Render email preview cosmetic
    • Tool “reply” changed its title: Reply to message cosmetic
    • Tool “resume_campaign” changed its title: Resume campaign cosmetic
    • Tool “send_campaign” changed its title: Send campaign cosmetic
    • Tool “send_campaign_test” changed its title: Send campaign test cosmetic
    • Tool “send_email” changed its title: Send email cosmetic
    • Tool “send_template” changed its title: Send template email cosmetic
    • Tool “set_email_design” changed its title: Set email design cosmetic
    • Tool “set_sequence_steps” changed its title: Set sequence steps cosmetic
    • Tool “tag_contacts” changed its title: Tag contacts cosmetic
    • Tool “track_event” changed its title: Track contact event cosmetic
    • Tool “turn_on_welcome_sequence” changed its title: Turn on welcome sequence cosmetic
    • Tool “unpublish_page” changed its title: Unpublish page cosmetic
    • Tool “unsubscribe_contact” changed its title: Unsubscribe contact cosmetic
    • Tool “unsubscribe_contacts” changed its title: Unsubscribe contacts cosmetic
    • Tool “update_campaign” changed its title: Update campaign cosmetic
    • Tool “update_contact” changed its title: Update contact cosmetic
    • Tool “update_page” changed its title: Update page cosmetic
    • Tool “update_tracking_settings” changed its title: Update tracking settings cosmetic
    • Tool “verify_domain” changed its title: Verify domain DNS cosmetic
    • Tool “wait_for_email” changed its title: Wait for email cosmetic
  • 16 Nov 26 +40
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 91 functional
    • First check of Destructive annotations: 0 functional
  • 15 Nov 26 34

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

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.runearc.com CN=YE2,O=Let's Encrypt,C=US 9 Nov 2026 7 Feb 2027 ECDSA 256 ECDSA-SHA384 60b306b70c684c46db3c28b5b3b04b7f106
SANs: mcp.runearc.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 secure

Validation of mcp.runearc.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
runearc.com. DS published 56919 13 Verified
mcp.runearc.com. Verified address RRset verified with the apex keys
Authentication Challenged, unverified

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

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="runearc"

Bearer realm="runearc"

Protected resource metadata

Retrieved No
Problem No resource metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.runearc.com/mcp Verified 200
http (plaintext) http://mcp.runearc.com/mcp HTTPS enforced 308 https://mcp.runearc.com/mcp
MCP tools · 90 exposed · ~11,591 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
activate_sequence ~102

Activate a draft or paused sequence so triggers enrol contacts and due steps run. Returns the sequence with status "active". Errors: sequence_empty, from_required (set a From address with a sender on a verified domain), invalid_branch, sequence_not_found. Next: enroll_contact_in_sequence to start one contact now, or wait for the trigger.

NameTypeReqDescription
sequence_idstringyesSequence id, such as "seq_01j9...", from list_sequences or create_sequence.

No output schema declared.

No examples provided.

add_contact ~206

Add ONE new contact (a person to email) to the workspace's audience; tags and list_ids given here are applied at once (missing tags are created). Use update_contact to change an existing contact, import_contacts or bulk_contacts for many. Returns the contact {id, email, status, tags, list_ids, ...}. Errors: invalid_email, contact_exists (use update_contact instead), unknown_field, not_found (list). Next: track_event for this contact, or enroll_contact_in_sequence.

NameTypeReqDescription
emailstringyesThe contact's email address.
first_namestring|null––
last_namestring|null––
list_idsarray–Ids (lst_...) of lists to join.
revenue_centsinteger|null–Lifetime revenue in cents.
sourcestring|null–Where they came from, such as "signup" or "import".
tagsarray–Tags to attach; created when missing.

No output schema declared.

No examples provided.

add_domain ~169

Add a custom domain to send and receive mail on, such as acme.com. Returns {id, name, status, provider, can_auto_configure, records: [{type, name, value, priority, required, status, fix}], next_step, existing_mx?}. Publish every required record at the DNS host. existing_mx means the domain already gets mail elsewhere: adding our MX moves it, so prefer a subdomain such as mail.acme.com. Errors: invalid_domain, reserved_domain, domain_exists, domain_taken, insufficient_scope. Next: publish the records, then call verify_domain; then create_inbox with domain set to it.

NameTypeReqDescription
namestringyesDomain name to send and receive on, such as "acme.com" or "mail.acme.com".

No output schema declared.

No examples provided.

add_to_list ~78

Add contacts to a list. Returns {added: n} for newly added contacts. Errors: not_found (list or contact). Next: list_contacts with list_id to see members.

NameTypeReqDescription
emailsarrayyesEmails or ids (ctc_...) of existing contacts.
list_idstringyesList id (lst_...).

No output schema declared.

No examples provided.

bulk_contacts ~217

Tag, add to a list, unsubscribe or delete many contacts at once. Give exactly one of contact_ids, emails or all_matching. Returns the operation {id, status, total, ...}; it runs in the background. Errors: invalid_body, too_many_targets, invalid_tags, empty_selection, not_found (list). Next: unsubscribe_contacts for plain unsubscribes; list_suppressions to review who is blocked.

NameTypeReqDescription
actionstringyes"tag", "add_to_list", "unsubscribe" or "delete".
all_matching––Act on every contact matching this filter {q, status, tag, list_id}; {} means all contacts.
contact_idsarray|null–Contact ids (ctc_...). Give exactly one of contact_ids, emails or all_matching.
emailsarray|null–Email addresses of contacts.
list_idstring|null–For "add_to_list": the list id (lst_...).
tagsarray–For "tag": the tags to add.

No output schema declared.

No examples provided.

cancel_campaign ~55

Cancel a campaign that has not finished. Pending recipients are dropped; mail already sent is not recalled. Errors: campaign_not_cancelable. Next: list_campaigns.

NameTypeReqDescription
idstringyesThe campaign id (cmp_...).

No output schema declared.

No examples provided.

connect_billing_integration ~145

Connect a billing provider so purchases, renewals, cancellations and refunds become events and contact revenue. Returns webhook_path (prefix with the API origin) to paste into the provider; `secret` is returned only if Runearc generated it (shown once). Errors: unknown_billing_provider, billing_already_connected. Next: send a test event from the provider, then list_billing_integrations to see last_event_at.

NameTypeReqDescription
providerstringyesstripe, paddle, lemonsqueezy, polar, revenuecat, adapty or shopify.
secretstring|null–The provider's webhook signing secret. Omit to have Runearc generate one.

No output schema declared.

No examples provided.

create_campaign ~120

Create a draft campaign, blank, from a design, or as a copy of another campaign. Returns the campaign {id, status:"draft", ...}. Errors: invalid_name, unknown_design, not_found. Next: update_campaign to set subject, from_address, document and audience, then send_campaign_test.

NameTypeReqDescription
copy_ofstring|null–Optional campaign id (cmp_...) to copy.
designstring|null–Optional design slug from list_campaign_designs.
namestringyesCampaign name, for example "November product update".

No output schema declared.

No examples provided.

create_event_definition ~105

Document a custom event so teammates know what it means. Returns the definition. Errors: event_definition_exists, invalid_event_name, reserved_event_name. Next: track_event to send it, or create_sync_rule.

NameTypeReqDescription
descriptionstring|null–What the event means.
namestringyesThe event name, such as "plan_upgraded".
properties––Documentation of the properties: [{"name": "plan", "type": "string"}]. Not enforced.

No output schema declared.

No examples provided.

create_form ~207

Create an embeddable signup form from a template (newsletter, waitlist or product-updates). Returns the form with its id. Errors: unknown_template, invalid_form_config, unknown_form_field, invalid_origin, list_not_found. Next: put <div data-runearc-form="ID"></div> and the runearc-embed.js script on your site, or create_popup to show the form on a trigger.

NameTypeReqDescription
allowed_originsarray–Websites allowed to submit, such as ["https://example.com"]. Empty means any.
double_opt_inboolean–Send a confirmation email first (double opt-in).
list_idsarray–Add new contacts to these lists (list ids).
namestringyesA name for the form, such as "Footer signup".
tagsarray–Tag new contacts with these tags.
templatestring|null–Starting template: newsletter, waitlist or product-updates. Default newsletter.

No output schema declared.

No examples provided.

create_goal ~167

Create a conversion goal. Each matching event records a conversion credited to the last email sent or clicked within window_days. Returns the goal. Errors: goal_exists, invalid_window (1 to 90), invalid_event_name. Next: track_event to convert, then goal_stats.

NameTypeReqDescription
conditions––Optional property conditions, same shape as for sync rules.
event_namestringyesThe event that counts as a conversion.
namestringyesA unique name, such as "Upgraded to pro".
value_propertystring|null–Property holding the revenue of the event, such as "amount".
window_daysinteger|null–Attribution window in days, 1 to 90 (default 7): an email sent or clicked this long before gets the credit.

No output schema declared.

No examples provided.

create_inbox ~246

Create a new email inbox that can receive (and send) mail right away. Returns {id, address, display_name, created_at}. Errors: inbox_limit_reached (plan limit; delete an inbox or upgrade), inbox_exists (pick another name), invalid_local_part, domain_not_found (custom domain not added), insufficient_scope (key limited to one inbox). Next: give `address` to the service you are signing up for, then call wait_for_email with `id` (pass after = created_at so an email that arrives early is not missed).

NameTypeReqDescription
display_namestring|null–Name shown in the From header of mail sent from this inbox, such as "Acme Bot".
domainstring|null–A custom domain this org added with add_domain, such as "acme.com". Leave out to use the free shared domain (<code>.runearc.email).
namestring|null–The part before the @, such as "signup-bot". 1 to 64 letters, digits, dots, hyphens or underscores. Leave out for a random name like "inbox-k3x9q2".

No output schema declared.

No examples provided.

create_list ~94

Create an empty, named contact list (a static group you add people to by hand; for rule-based groups use create_segment). Names are unique per workspace. Returns {id, name, description, member_count: 0}. Errors: list_exists (call list_lists and reuse it), invalid_name. Next: add_to_list with the returned id.

NameTypeReqDescription
descriptionstring|null––
namestringyes–

No output schema declared.

No examples provided.

create_page ~154

Create a draft landing page from a template (blank, waitlist, product-launch, newsletter). Returns the page with its blocks. Errors: page_slug_taken, unknown_page_template, invalid_page_form. Next: update_page to edit blocks and pick a form, then publish_page.

NameTypeReqDescription
form_idstring|null–The signup form (frm_...) the signup block uses.
namestringyesA name for the page, such as "Spring launch".
slugstring|null–URL slug (3 to 40 lowercase letters, digits, hyphens). Default: from the name.
templatestring|null–Starting template: blank, waitlist, product-launch or newsletter. Default blank.

No output schema declared.

No examples provided.

create_popup ~225

Create a popup that shows a form on a trigger (time, scroll or exit_intent), optionally only on some paths. Errors: invalid_popup_config, not_found (form), invalid_status. Next: set status live, then add the runearc-embed.js script with data-popup="ID" to your site; popup_stats shows conversions.

NameTypeReqDescription
days_betweeninteger|null–Days before showing again to the same visitor. Default 7.
form_idstringyesThe form to show (frm_...).
headingstringyesThe popup headline.
namestringyesA name for the popup, such as "Blog exit offer".
only_pathsarray–Only on URLs starting with these paths, such as ["/blog"]. Empty means every page.
statusstring|null–draft or live. Default draft.
triggerstring|null–time, scroll or exit_intent. Default time.
trigger_valueinteger|null–Seconds for time, percent for scroll. Default 5 and 50.

No output schema declared.

No examples provided.

create_segment ~268

Save a segment (a named audience filter over contacts). Returns the segment. Errors: invalid_filter (read the fix), segment_name_taken, segment_limit. Next: preview_segment, then use the id as the audience of a campaign.

NameTypeReqDescription
descriptionstring–What it is for.
filter–yesThe filter: {"type":"group","op":"and"|"or","children":[...]}. Conditions: {"type":"tag","tag":"vip","has":true}, {"type":"status","is":["active"]}, {"type":"list","list_id":"lst_..","member":true},…
namestringyesSegment name, unique in the workspace.

No output schema declared.

No examples provided.

create_sequence ~191

Create an empty draft sequence. Nothing sends until it has steps, a From address and is activated. Returns the sequence. Errors: invalid_name, invalid_trigger (use manual, tag:<tag>, list:<id> or event:<name>). Next: set_sequence_steps, then activate_sequence. install_starter_sequence is faster for common flows.

NameTypeReqDescription
fromstring|null–The From address, such as "Acme <hello@acme.com>", on a verified domain. Needed before activating a sequence that sends email.
goal_eventstring|null–Contacts who track this event leave the sequence, such as "upgraded".
namestringyesSequence name, 1 to 120 characters, such as "Welcome".
triggerstringyesWhat enrols a contact: "manual", "tag:<tag>", "list:<list id>" or "event:<event name>".

No output schema declared.

No examples provided.

create_sync_rule ~249

Create a sync rule: when event_name happens and all conditions match, apply the action to the contact. Returns the rule. Errors: invalid_argument, invalid_event_name, list_not_found, field_not_found (create the contact field first), invalid_tag. Next: track_event to try it, then get_contact or list_contact_events to see the result.

NameTypeReqDescription
action–yesWhat to do: {"type": "add_tag", "tag": "customer"}, {"type": "remove_tag", "tag": "trial"}, {"type": "set_field", "key": "plan", "value": "pro"} or {"type": "add_to_list", "list_id": "lst_..."}.
conditions––All must match: [{"path": "plan", "op": "eq", "value": "pro"}]. Ops: eq, neq, gt, gte, lt, lte, contains, exists.
event_namestringyesThe event that triggers it, custom or built-in (for example "plan_upgraded" or "tag.added").
namestringyesA name for the rule, such as "Tag pro customers".

No output schema declared.

No examples provided.

create_template ~178

Create a transactional template from one of 18 starters (password-reset, magic-link, email-verification, verification-code, welcome, receipt, invoice, order-confirmation, shipping-notification, subscription-renewal, payment-failed, trial-ending, team-invite, login-alert, account-deleted, refund-issued, feedback-request, waitlist-confirmation) or a blank one, and publish it so it can be sent. Errors: template_slug_taken, unknown_starter, invalid_template_slug. Next: send_template.

NameTypeReqDescription
from_starterstring|null–A built-in starter slug such as "password-reset" or "welcome".
namestring|null–Template name. Defaults to the starter name.
slugstring|null–URL-safe slug used in code. Defaults to the starter slug or the slugified name.

No output schema declared.

No examples provided.

create_webhook ~217

Register a webhook: Runearc POSTs signed JSON events (Standard Webhooks) to the URL, retrying on failure. Returns {id, url, event_types, inbox_id, secret, created_at}; the secret is shown only once. Errors: invalid_webhook_url (https only, http allowed for localhost), invalid_event_type, not_found (inbox). Next: store the secret and verify each delivery's webhook-signature header with it. For a single expected email, wait_for_email is simpler than a webhook.

NameTypeReqDescription
event_typesarray–Event types to deliver, such as ["message.received"]. Leave out for every event. Types: message.received, message.queued, message.delivered, message.deferred, message.bounced, message.complained, mes…
inbox_idstring|null–Only deliver events for this inbox. Leave out for every inbox in the org.
urlstringyesWhere to POST events: an https:// URL (http:// only for localhost).

No output schema declared.

No examples provided.

delete_inbox ~88

Delete an inbox and all of its messages. Mail to its address is rejected afterwards. This cannot be undone. Returns {deleted: true, id}. Errors: not_found, insufficient_scope. Next: create_inbox if you need a fresh address.

NameTypeReqDescription
inbox_idstringyesInbox id, such as "ibx_01j9...", from create_inbox or list_inboxes.

No output schema declared.

No examples provided.

delete_page ~48

Delete a landing page with its view counts and lead links (the contacts stay). Errors: not_found. Next: list_pages.

NameTypeReqDescription
idstringyesThe page id (pg_...).

No output schema declared.

No examples provided.

delete_segment ~65

Permanently delete a saved segment (the saved filter only; the contacts in it are not touched). Built-in quick filters cannot be deleted. Returns {deleted: true}. Errors: not_found, builtin_segment_readonly. Next: list_segments.

NameTypeReqDescription
segment_idstringyes–

No output schema declared.

No examples provided.

delete_sync_rule ~79

Delete a sync rule so future events no longer trigger it. Changes it already made to contacts (tags, fields, lists) stay. Returns {deleted: id}. Errors: not_found (already deleted or wrong id; list_sync_rules shows the current ones). Next: list_sync_rules.

NameTypeReqDescription
idstringyesThe id of the rule.

No output schema declared.

No examples provided.

draft_welcome_sequence ~177

Draft a 4 email welcome sequence (immediately, day 1, day 3, day 5) from an imported site. It is saved as a DRAFT: nothing is sent and nobody is enrolled. Returns {sequence_id, steps:[{position, delay_seconds, subject}], address_required}. Errors: import_not_found, welcome_draft_shape. Next: if address_required is true, set the business mailing address (PUT /v1/workspace/postal-address), then call turn_on_welcome_sequence with `sequence_id` once the user agrees.

NameTypeReqDescription
import_idstringyesThe import id from import_site, such as "sim_01j9...".
stylestring|null–"designed" (branded layout, default) or "plain" (looks like a personal email).

No output schema declared.

No examples provided.

enroll_contact_in_sequence ~176

Enrol one contact in an active sequence now. Returns the enrolment {id, status, current_position, next_run_at}. Errors: sequence_not_active, contact_not_found, contact_not_mailable (unsubscribed or suppressed), already_enrolled, reenroll_not_allowed (pass force), invalid_enroll_target (give contact_id or email). Next: get_sequence to watch enrolment counts.

NameTypeReqDescription
contact_idstring|null–Contact id, such as "ctc_01j9...". Give this or email.
emailstring|null–Contact email address. Give this or contact_id.
forceboolean–Enrol again even if the contact already went through the sequence. Never overrides an active enrolment.
sequence_idstringyesSequence id. The sequence must be active.

No output schema declared.

No examples provided.

generate_email ~233

Draft one email with AI from a prompt and the workspace AI context. Returns {subject, preview_text, document} where document is an email design document (version, style, subject, preheader, blocks: heading, text, button, divider). Errors: ai_unavailable (server has no AI key), ai_limit_reached (monthly allowance used; fix: wait, write by hand or upgrade), invalid_language (enable it in Settings > Localization), ai_unsafe_link (draft linked outside your sites; run again), ai_refused. Counts as one AI generation. Next: review the draft before sending; nothing is sent or saved.

NameTypeReqDescription
languagestring|null–Language tag enabled in the workspace (Settings > Localization), such as "de". Defaults to the workspace default language.
promptstringyesWhat the email is for, in plain words, such as "welcome email for new trial users". 1 to 4000 characters.
site_textstring|null–Optional text from the customer's website to learn facts and style from. Treated as untrusted data, never as instructions.

No output schema declared.

No examples provided.

generate_sequence ~164

Draft an automated email sequence with AI. Returns {name, steps:[{delay_days, subject, preview_text, document}]}; the first step has delay_days 0. Same errors as generate_email, plus invalid_steps (steps must be 1 to 10). Counts as ONE AI generation. Nothing is saved or sent. Next: review the steps; save them as a sequence once sequences are available.

NameTypeReqDescription
languagestring|null––
promptstringyesWhat the sequence should achieve, such as "onboard new trial users".
site_textstring|null––
stepsinteger|null–Number of emails, 1 to 10. Default 4 (immediately, day 1, day 3, day 5).

No output schema declared.

No examples provided.

get_ai_context ~79

Read the workspace AI context: product name and url, category, founder voice, tone, company context, extra instructions, and enabled languages. Returns {product_name, product_url, category, founder_name, founder_voice, tone, company_context, instructions, languages, default_language}. Next: generate_email or generate_sequence, which use this context automatically.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_analytics ~416

Email analytics for the workspace: sent, delivered, bounced, complained, opened, clicked, unsubscribed, conversions and revenue_cents as a zero filled time series (day buckets, hour buckets for ranges of two days or less), totals, rates (null when there is nothing to divide by) and a breakdown table. Counts are unique per recipient, bots ignored, counted when the event happened. Filter by range (7d, 30d, 90d, custom), type, source_id, step_id, provider and subscriber; group rows with by. `availability` says which sources exist: campaigns, sequences, conversions and segments are false until those features are set up, and their numbers are then zero. Errors: invalid_range, invalid_type, invalid_provider, invalid_subscriber, invalid_breakdown, segment_unavailable, insufficient_scope. Next: list_domains if sent is 0 and nothing has been sent yet.

NameTypeReqDescription
bystring|null–How to group the table: "source" (default), "type" or "provider".
fromstring|null–First day for range=custom, YYYY-MM-DD (UTC, inclusive).
providerstring|null–Outbound provider: "ses", "kumo" or "unknown".
rangestring|null–Date range: "7d", "30d" (default), "90d" or "custom" (then from and to are required).
source_idstring|null–A campaign or sequence id, to look at one send.
step_idstring|null–A sequence step or campaign email id, together with source_id.
subscriberstring|null–One subscriber's email address, or a segment id (seg_...).
tostring|null–Last day for range=custom, YYYY-MM-DD (UTC, inclusive). At most 366 days in total.
typestring|null–Send type: "transactional", "campaign" or "sequence".

No output schema declared.

No examples provided.

get_email_design ~72

Get the workspace email design: brand color, font, alignment, logo, header, footer and postal address. Returns {brand, design_md}; design_md is a markdown file you can edit and send back with set_email_design. Next: set_email_design, or render_email_preview to see how a document looks.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_email_tracking ~120

Counted opens, unique opens, clicks, unique clickers and unsubscribes of one email, plus how many opens and clicks the bot filter flagged. Returns {opens, unique_opens, clicks, unique_clickers, unsubscribes, flagged_opens, flagged_clicks}. Errors: forbidden. Next: list the email's events with GET /v1/tracking/events?message_id=..., or change what is tracked with update_tracking_settings.

NameTypeReqDescription
email_idstringyesEmail id such as "eml_01j9...".

No output schema declared.

No examples provided.

get_import ~109

Progress of a contact import. Returns {import: {status, total_rows, processed_rows, created_count, updated_count, skipped_count, error_count}, errors: [{row_number, email, code, message}]} (first 50 errors). Errors: not_found. Next: call again while status is queued or running; fix the rows in `errors` and import them again.

NameTypeReqDescription
import_idstringyesImport id, such as "imp_01j9...", from import_contacts.

No output schema declared.

No examples provided.

get_inbox ~70

Get one inbox by id. Returns {id, address, display_name, created_at}. Errors: not_found. Next: list_messages or wait_for_email.

NameTypeReqDescription
inbox_idstringyesInbox id, such as "ibx_01j9...", from create_inbox or list_inboxes.

No output schema declared.

No examples provided.

get_message ~150

Get one message with its text body and the one time codes and links found in it. Returns {id, inbox_id, thread_id, direction, status, from, to, cc, subject, text, codes, links, attachments, spam, created_at}; html only when include_html is true. Errors: not_found. Next: use codes[0] or a link from links to finish a sign up, or call reply to answer.

NameTypeReqDescription
include_htmlboolean–Also return the HTML body. Off by default because the text body, codes and links are usually all an agent needs.
message_idstringyesMessage id, such as "msg_01j9...".

No output schema declared.

No examples provided.

get_page ~54

Read one landing page: draft blocks, status, form and public url. Errors: not_found. Next: update_page to edit it, or publish_page.

NameTypeReqDescription
idstringyesThe page id (pg_...).

No output schema declared.

No examples provided.

get_sequence ~77

Get one sequence with its trigger, goal, From address, ordered steps and enrolment counts. Returns the sequence. Errors: sequence_not_found. Next: set_sequence_steps to edit, activate_sequence to start it.

NameTypeReqDescription
sequence_idstringyesSequence id, such as "seq_01j9...", from list_sequences or create_sequence.

No output schema declared.

No examples provided.

get_thread ~97

Get a conversation with all of its messages, oldest first, each with text, codes and links. Returns {id, inbox_id, subject, message_count, last_message_at, messages: [...]}. Errors: not_found. Next: reply with the id of the last message to continue the conversation.

NameTypeReqDescription
thread_idstringyesThread id, such as "thr_01j9...", from list_threads or a message's thread_id.

No output schema declared.

No examples provided.

get_tracking_settings ~66

Show the workspace's tracking settings: opens, clicks, unsubscribe, strict bot filter and the per-address frequency cap. Returns {track_opens, track_clicks, unsubscribe_enabled, strict_bot_filter, frequency_cap_count, frequency_cap_hours}. Next: update_tracking_settings to change them.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

goal_stats ~106

Read-only results of one goal over the last `days` (default 30, 1 to 365): conversions, unique contacts, how many were credited to an email, revenue_cents and the top emails. Errors: not_found. Next: list_goals, or create_goal for another outcome.

NameTypeReqDescription
daysinteger|null–Look back this many days (1 to 365, default 30).
idstringyesThe goal id (gol_...).

No output schema declared.

No examples provided.

import_contacts ~223

Import contacts from CSV text and start the import. Detects the email, first name and last name columns from the header. Returns {import, mapping_used}; the import runs in the background. Errors: empty_csv, invalid_csv, csv_too_large, too_many_rows, unknown_column, not_found (list). Next: get_import with import.id until import.status is done; rows that failed or were skipped are in `errors`.

NameTypeReqDescription
csvstringyesThe whole CSV file as text. First row is the header. Up to 25 MB.
email_columnstring|null–Header of the email column. Leave out to detect it ("email", "e-mail", ...).
filenamestring|null–File name for the record, such as "customers.csv".
list_idsarray–List ids (lst_...) every imported contact is added to.
tagsarray–Tags to add to every imported contact.
update_existingboolean–Merge into contacts that already exist instead of skipping them. Default false.

No output schema declared.

No examples provided.

import_site ~125

Read a website and save its name, logo, brand colour and description as the workspace's brand and company context. Fetches only public web pages (private and internal addresses are refused). Returns {id, name, description, logo_url, color}. Errors: site_blocked, invalid_site_url, site_unreachable, site_not_html, too_many_redirects, site_import_rate_limited. Next: call draft_welcome_sequence with `id`.

NameTypeReqDescription
urlstringyesPublic address of the website, such as "acme.com" or "https://acme.com".

No output schema declared.

No examples provided.

install_starter_sequence ~97

Create a draft sequence from a ready made one: welcome, onboarding, trial-ending, win-back, churn-save or review-request, with real email copy. Returns the sequence. Errors: starter_not_found. Next: update the From address and button links, then activate_sequence.

NameTypeReqDescription
keystringyesOne of "welcome", "onboarding", "trial-ending", "win-back", "churn-save", "review-request".

No output schema declared.

No examples provided.

list_billing_integrations ~63

List connected billing providers (Stripe, Paddle, Lemon Squeezy, Polar, ...). Returns {integrations: [...]} with each webhook_path (prefix with the API origin) and last_event_at. Next: connect_billing_integration to add one.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_campaign_designs ~39

List the 8 starting designs for a campaign (slug, name, subject, document). Next: create_campaign with design set to a slug.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_campaigns ~91

List broadcast campaigns, newest first, optionally only one status (draft, scheduled, sending, paused, sent, canceled). Each has counters: recipients_total, sent_count, suppressed_count, deferred_count, unsubscribed_count, failed_count. Next: create_campaign, or send_campaign for a draft.

NameTypeReqDescription
statusstring|null–Only this status: draft, scheduled, sending, paused, sent or canceled.

No output schema declared.

No examples provided.

list_contact_events ~118

List a contact's events, newest first. Returns {data: [...], next_cursor}. Errors: not_found (contact). Next: track_event to add one, or pass next_cursor back as cursor for the next page.

NameTypeReqDescription
contact_idstringyesThe contact id (ctc_...).
cursorstring|null–The next_cursor of the previous page.
limitinteger|null–How many events (1 to 100, default 20).
namestring|null–Only events with this name.

No output schema declared.

No examples provided.

list_contacts ~140

Find contacts, newest first. Filter by q, status, tag or list_id. Returns {contacts: [...], next_cursor}. Pass next_cursor back as cursor for the next page. Next: update_contact, tag_contacts or unsubscribe_contact on a result.

NameTypeReqDescription
cursorstring|null–next_cursor from the previous page.
limitinteger|null–1 to 200, default 50.
list_idstring|null––
qstring|null–Substring of email, first or last name.
statusstring|null–active, unsubscribed, bounced or complained.
tagstring|null––

No output schema declared.

No examples provided.

list_domains ~42

List the org's custom domains with their status and DNS records. Returns {domains: [...]}. Next: verify_domain for any that are not verified, or add_domain.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_event_definitions ~76

List the custom event names this workspace has documented (name, description, property hints), so you use the same names in track_event and create_sync_rule. Read-only; events can be tracked without a definition. Returns {events: [...]}. Next: create_event_definition to document another, or create_sync_rule to act on one.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Runearc MCP server?

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

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

What is the Runearc MCP server?

Runearc is an MCP server listed in the public MCP registry as io.github.runearc-labs/runearc. Email inboxes for AI agents: create an inbox, wait for the verification code, send and reply. This page covers its hosted endpoint (https://mcp.runearc.com/mcp).

Is the Runearc MCP server safe to use?

Runearc scores 78 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 Runearc MCP server expose?

Runearc exposes 90 tools: activate_sequence, add_contact, add_domain, add_to_list, bulk_contacts, and 85 more. Their descriptions and schemas cost roughly 11,591 tokens of context every time the server is loaded.

Does the Runearc MCP server require authentication?

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

Runearc 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 Runearc MCP server?

VerifyMCP ran 13 checks on Runearc, 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.