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
list_form_submissions ~104

Recent submissions of a form, newest first: {submissions:[{email,status,origin,page_url,created_at}]}. Status is accepted, pending_confirmation, confirmed, suppressed or spam. Errors: not_found (form). Next: list_contacts to see the people who joined, or create_popup to collect more signups.

NameTypeReqDescription
form_idstringyesThe form id (frm_...).
limitinteger|null–Max rows, default 50.

No output schema declared.

No examples provided.

list_forms ~58

List the workspace's signup forms. Returns {forms:[{id,name,status,config,...}]}. Errors: insufficient_scope (needs a full access key). Next: list_form_submissions for who signed up, or create_form for a new one.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_goals ~41

List conversion goals (an event plus conditions that counts as a win). Returns {goals: [...]}. Next: goal_stats for results, or create_goal.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_inboxes ~58

List the inboxes this API key can use. Returns {inboxes: [{id, address, display_name, created_at}]}. Next: list_messages or wait_for_email with an inbox id, or create_inbox if there is none.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_lists ~60

List every contact list in the workspace (static lists, not segments) with member counts. Read-only. Returns {lists: [{id, name, description, member_count}]}. Next: add_to_list, or list_contacts with list_id to see members.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_messages ~172

List messages in an inbox, newest first, received and sent. Returns {messages: [{id, thread_id, direction, from, to, subject, preview, attachments, created_at}], next_cursor}. Pass next_cursor back as cursor for older messages. Errors: not_found (inbox). Next: get_message for the full text, codes and links; reply to answer one. To wait for a message that has not arrived yet, use wait_for_email instead of polling this.

NameTypeReqDescription
cursorstring|null–The next_cursor from the previous page, to get older messages.
inbox_idstringyesInbox id, such as "ibx_01j9...".
limitinteger|null–How many messages to return, newest first. 1 to 100, default 20.

No output schema declared.

No examples provided.

list_pages ~54

List the workspace's landing pages with status, views, leads and conversion per view. Returns {pages: [...]}. Errors: insufficient_scope (needs a full access key). Next: create_page, or publish_page for a draft.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_segments ~50

List segments: six built-in quick filters (builtin_*) then saved ones, each with a filter and a cached last_count. Next: preview_segment for a live count, create_segment to save your own.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_sequences ~93

List sequences (lifecycle automations), newest first. Returns {sequences: [{id, name, status, trigger, steps, enrolled, active, completed, ...}]}. Next: get_sequence for one, install_starter_sequence for a ready made one, or create_sequence.

NameTypeReqDescription
statusstring|null–Only sequences with this status: "draft", "active" or "paused". Leave out for all.

No output schema declared.

No examples provided.

list_suppressions ~121

List addresses that will not be emailed: hard bounces, complaints, manual blocks and unsubscribed contacts. Returns {suppressions: [{address, reason, created_at}], next_cursor, counts}. Errors: invalid_reason, invalid_cursor. Next: pass next_cursor as cursor for more.

NameTypeReqDescription
cursorstring|null–next_cursor of the previous page.
qstring|null–Only addresses starting with this text.
reasonstring|null–"hard_bounce", "complaint", "manual" or "unsubscribed".

No output schema declared.

No examples provided.

list_sync_rules ~48

List sync rules: when an event matches, tag the contact, set a field or add it to a list. Returns {rules: [...]}. Next: create_sync_rule or delete_sync_rule.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_templates ~43

List this workspace's transactional templates. Returns {data:[{id, slug, name, published_version_id}]}. Next: send_template, or create_template to add one.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_threads ~93

List conversations (threads) in an inbox, most recently active first, up to 100. Returns {threads: [{id, inbox_id, subject, message_count, last_message_at}]}. Errors: not_found (inbox). Next: get_thread to read a conversation.

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

No output schema declared.

No examples provided.

pause_campaign ~48

Pause a sending campaign; pending recipients stay queued. Errors: campaign_not_pausable. Next: resume_campaign or cancel_campaign.

NameTypeReqDescription
idstringyesThe campaign id (cmp_...).

No output schema declared.

No examples provided.

pause_sequence ~86

Pause an active sequence: no new contacts enter and no step runs; enrolments keep their place and catch up on resume. Returns the sequence with status "paused". Errors: sequence_not_found. Next: set_sequence_steps to edit it, then activate_sequence.

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

No output schema declared.

No examples provided.

popup_stats ~107

Read-only performance of one popup made with create_popup: impressions, dismissals, conversions and conversion_rate (conversions / impressions, 0 when there are no impressions). Returns {impressions, dismissals, conversions, conversion_rate}. Errors: not_found (popup; use the id create_popup returned). Next: change the trigger or paths if the rate is low, or list_form_submissions to see who converted.

NameTypeReqDescription
popup_idstringyesThe popup id (pop_...).

No output schema declared.

No examples provided.

preview_segment ~126

Live count and a sample of contacts for a segment id or a draft filter, without saving. Returns {count, sample:[{id,email,first_name,last_name,status}]}. Engagement and event conditions match nobody until tracking data exists. Next: create_segment to save it.

NameTypeReqDescription
filter––A draft filter, same shape as create_segment.
limitinteger|null–Sample size, 1 to 100. Default 10.
segment_idstring|null–A saved or built-in segment id (seg_..., builtin_engaged). Give this or `filter`.

No output schema declared.

No examples provided.

publish_page ~73

Publish a landing page: freezes the draft as the live snapshot at /p/<workspace>/<slug>. Errors: page_needs_form (a signup block needs a form_id). Next: share the returned url, or list_pages to watch views and leads.

NameTypeReqDescription
idstringyesThe page id (pg_...).

No output schema declared.

No examples provided.

remove_billing_integration ~55

Disconnect a billing provider; its webhook URL stops working. Returns {deleted}. Errors: not_found. Next: list_billing_integrations to confirm.

NameTypeReqDescription
idstringyesThe connection id (bil_...).

No output schema declared.

No examples provided.

render_email_preview ~194

Render an email document with the workspace brand, without sending. Returns {subject, html, text}. Errors: invalid_document, unknown_variable (add a fallback like {{FIRST_NAME|Friend}} or pass vars), missing_address, invalid_variable. Next: send it, or fix the document and render again.

NameTypeReqDescription
document–yesThe email document: {version:1, style:"designed"|"plain", subject, preheader?, blocks:[{type:"heading",text,level}|{type:"text",text}|{type:"button",label,url}| {type:"image",src,alt,href?}|{type:"di…
varsobject|null–Values for {{NAME}} variables, such as {"FIRST_NAME":"Ana"}.

No output schema declared.

No examples provided.

reply ~189

Reply to a message in the same thread (sets In-Reply-To, References and a "Re:" subject). Replying to a message you sent follows up with its recipients. Returns {id, thread_id, status, from, to, cc, subject, created_at}. Errors: not_found (message), missing_body, no_reply_address, recipient_suppressed, daily_send_limit_reached, sending_paused, transport_unavailable. Next: wait_for_email on the inbox for their answer.

NameTypeReqDescription
htmlstring|null–HTML body. Give text, html or both.
message_idstringyesId of the message to reply to, such as "msg_01j9...".
reply_allboolean–Also copy everyone else who was on the original message. Default false.
textstring|null–Plain text body. Give text, html or both.

No output schema declared.

No examples provided.

resume_campaign ~52

Resume a paused campaign; sending continues with the pending recipients. Errors: campaign_not_resumable. Next: list_campaigns to watch the counters.

NameTypeReqDescription
idstringyesThe campaign id (cmp_...).

No output schema declared.

No examples provided.

send_campaign ~126

Send a draft campaign now, or schedule it with scheduled_at (RFC 3339, within 30 days). Runearc sends one personalised email per active contact, skipping unsubscribed and suppressed ones and spacing out contacts over the frequency cap. Errors: campaign_incomplete, campaign_not_sendable, invalid_schedule. Next: list_campaigns to watch the counters, pause_campaign or cancel_campaign to stop.

NameTypeReqDescription
idstringyesThe campaign id (cmp_...).
scheduled_atstring|null–RFC 3339 time to send at; leave out to send now.

No output schema declared.

No examples provided.

send_campaign_test ~86

Send a campaign test to 1 to 5 addresses (subject prefixed [Test], no tracking, no recipient rows). Errors: campaign_incomplete (read the fix), invalid_test_recipients, campaign_canceled. Next: send_campaign.

NameTypeReqDescription
idstringyesThe campaign id (cmp_...).
toarrayyes1 to 5 addresses.

No output schema declared.

No examples provided.

send_email ~238

Send a new email from an inbox. Starts a new thread. Returns {id, thread_id, status, from, to, cc, subject, created_at}; status is "queued" until delivery. Errors: missing_body (give text or html), missing_recipients, invalid_address, invalid_subject, too_many_recipients, recipient_suppressed (address bounced or complained before), daily_send_limit_reached, monthly_send_limit_reached, sending_paused, transport_unavailable (sending not enabled on this server), not_found (inbox). Next: wait_for_email on the same inbox to catch the answer, or create_webhook for message.delivered events.

NameTypeReqDescription
ccarray–Copied recipient addresses.
htmlstring|null–HTML body. Give text, html or both.
inbox_idstringyesInbox id to send from, such as "ibx_01j9...". The From address is the inbox address.
subjectstringyes–
textstring|null–Plain text body. Give text, html or both.
toarrayyesRecipient addresses.

No output schema declared.

No examples provided.

send_template ~161

Send an email from a published transactional template. Returns {id}. Errors: template_not_found, template_not_published, missing_variable (names the variable), invalid_variable, template_conflict, recipient_suppressed, daily_send_limit_reached, sending_paused. Next: wait_for_email or create_webhook for delivery events.

NameTypeReqDescription
fromstringyesSender on a verified domain, such as "Acme <noreply@acme.com>".
subjectstring|null–Overrides the template subject.
templatestringyesTemplate slug or tpl_ id. Must have a published version.
toarrayyes–
variables––Values for the template variables, for example {"RESET_URL": "https://..."}.

No output schema declared.

No examples provided.

set_email_design ~114

Replace the workspace email design from a design.md file. Returns {brand}. Errors: invalid_design_md, invalid_brand (each has a fix), forbidden (needs a full scope key). Marketing email needs the ## Address section (CAN-SPAM). Next: render_email_preview.

NameTypeReqDescription
design_mdstringyesThe whole design.md file: front matter (color, font, align, logo) then optional ## Header, ## Footer and ## Address sections. Get the current one with get_email_design and edit it.

No output schema declared.

No examples provided.

set_sequence_steps ~207

Replace all steps of a draft or paused sequence. Returns the sequence. Errors: sequence_active (pause it first), invalid_steps (the steps JSON does not parse), sequence_empty, too_many_steps, invalid_delay, invalid_email_step, invalid_branch (branches jump forward only). Next: activate_sequence.

NameTypeReqDescription
sequence_idstringyesSequence id. The sequence must be a draft or paused.
stepsarrayyesThe ordered steps. Each is {"kind":"email","subject":"..","preview":"..","doc":{"version":1,"style":"designed","subject":"..","blocks":[{"type":"text","text":"Hi {{FIRST_NAME|there}}"}]}}, {"kind":"d…

No output schema declared.

No examples provided.

tag_contacts ~84

Attach a tag to contacts (the tag is created if missing). Returns {tagged: n} for newly tagged contacts. Errors: not_found (contact), invalid_tag. Next: list_contacts with tag to see them.

NameTypeReqDescription
emailsarrayyesEmails or ids (ctc_...) of existing contacts.
tagstringyesTag name; created when missing.

No output schema declared.

No examples provided.

track_event ~227

Record that a contact did something, such as plan_upgraded. Runearc then applies sync rules (tags, fields, lists) and goals. Returns the event with duplicate=true when the idempotency_key was seen before. Errors: contact_not_found (create the contact first), reserved_event_name, invalid_event_name, invalid_properties, properties_too_large, idempotency_key_reused. Next: list_contact_events to confirm it, or create_sync_rule to react to it.

NameTypeReqDescription
emailstringyesEmail of an existing contact the event is about.
idempotency_keystring|null–Repeating the same key returns the first event instead of recording a second one.
namestringyesThe event name: lowercase letters, digits and _ . : - starting with a letter, such as "plan_upgraded". Built-in names (email.opened, tag.added, ...) are reserved.
properties––Event properties as a JSON object, up to 16 KB, such as {"plan": "pro", "amount": 49}.

No output schema declared.

No examples provided.

turn_on_welcome_sequence ~109

Turn on the welcome sequence: from now on contacts matching its audience are enrolled and emailed. Ask the user first, this is the step that sends mail. Returns {sequence_id, active: true}. Errors: postal_address_required (CAN-SPAM, add the address first), welcome_not_found. Next: add contacts, or watch the sequence's analytics.

NameTypeReqDescription
sequence_idstringyesThe welcome sequence id from draft_welcome_sequence, such as "seq_01j9...".

No output schema declared.

No examples provided.

unpublish_page ~55

Take a landing page offline; the address answers not found. Counts and leads are kept. Errors: not_found. Next: publish_page to bring it back.

NameTypeReqDescription
idstringyesThe page id (pg_...).

No output schema declared.

No examples provided.

unsubscribe_contact ~59

Unsubscribe a contact so broadcasts skip them. Returns the contact with status unsubscribed. Errors: not_found. Next: list_contacts with status unsubscribed to review.

NameTypeReqDescription
emailstringyesThe contact's email or id (ctc_...).

No output schema declared.

No examples provided.

unsubscribe_contacts ~93

Unsubscribe addresses from marketing mail. Unknown addresses become unsubscribed contacts, so a later import cannot resubscribe them. Transactional mail still sends. Returns the operation {id, status, total}. Errors: too_many_targets, empty_selection. Next: list_suppressions with reason "unsubscribed".

NameTypeReqDescription
emailsarrayyesAddresses to unsubscribe from marketing mail (max 10000). Unknown addresses are remembered.

No output schema declared.

No examples provided.

update_campaign ~223

Edit a draft campaign: name, subject, preheader, from_address (a verified sender), reply_to, document (email design JSON) and audience ({kind:list,id} | {kind:segment,id} | {kind:tag,name}). Only drafts can be edited. Errors: campaign_not_editable, invalid_address, invalid_document, invalid_field, not_found. Next: send_campaign_test, then send_campaign.

NameTypeReqDescription
audience––{kind:"list",id} | {kind:"segment",id} | {kind:"tag",name}.
document––Email design document: {version:1, style, subject, blocks:[...]}.
from_addressstring|null–Sender address on a verified domain, such as news@example.com.
idstringyesThe campaign id (cmp_...).
namestring|null––
preheaderstring|null––
reply_tostring|null––
subjectstring|null–Subject line; variables like {{FIRST_NAME|there}} are allowed.

No output schema declared.

No examples provided.

update_contact ~104

Change a contact's names, source or revenue. Pass an empty string to clear a name. Returns the contact. Errors: not_found, invalid_revenue. Next: list_contacts to confirm.

NameTypeReqDescription
emailstringyesThe contact's email or id (ctc_...).
first_namestring|null–Empty string clears.
last_namestring|null––
revenue_centsinteger|null––
sourcestring|null––

No output schema declared.

No examples provided.

update_page ~186

Change a landing page draft: name, slug, SEO title, description, signup form_id (null clears it) or the whole blocks array. A published page keeps serving its snapshot until publish_page. Errors: invalid_page_link, too_many_blocks, too_many_signup_blocks, page_slug_taken, invalid_page_form. Next: publish_page.

NameTypeReqDescription
blocksarray|null–The whole ordered blocks array. Types: hero, features, signup, cta, footer.
clear_formboolean–Set true to remove the signup form from the page.
descriptionstring|null–SEO description.
form_idstring|null–The signup form (frm_...).
idstringyesThe page id (pg_...).
namestring|null––
slugstring|null––
titlestring|null–SEO title.

No output schema declared.

No examples provided.

update_tracking_settings ~222

Change tracking settings; only the fields you pass change. Marketing mail is mail tagged category=marketing: only it gets unsubscribe links and the frequency cap. Errors: invalid_frequency_cap (1 to 1000 emails per 1 to 8760 hours), forbidden. Returns the new settings. Next: get_tracking_settings to confirm, then send_email with the category=marketing tag.

NameTypeReqDescription
clear_frequency_capboolean–Set true to remove the cap.
frequency_cap_countinteger|null–Max marketing emails per address per window; use with frequency_cap_hours.
frequency_cap_hoursinteger|null–Window of the cap in hours.
strict_bot_filterboolean|null–Flag opens and clicks from scanners, prefetchers and instant hits instead of counting them.
track_clicksboolean|null–Rewrite links to signed redirects that count clicks.
track_opensboolean|null–Track opens with a first-party pixel.
unsubscribe_enabledboolean|null–Add List-Unsubscribe headers and a footer link to marketing mail.

No output schema declared.

No examples provided.

verify_domain ~122

Check a domain's DNS records now and update its status. Returns the domain with status "verified", "pending" or "failing", and per record status ok, missing or wrong with a fix. DNS changes can take a few minutes to be visible. Errors: domain_not_found. Next: if not verified, apply each record's fix and call this again; once verified, create_inbox with domain set.

NameTypeReqDescription
domainstringyesDomain name, such as "acme.com", or its id, such as "dom_01j9...".

No output schema declared.

No examples provided.

wait_for_email ~397

Wait until an email arrives in an inbox, then return it with the one time codes and links extracted, so a sign up is two calls: create_inbox, then this. Blocks up to timeout_seconds (default 60, max 120). Returns {message: {id, from, subject, text, codes, links, ...}, codes, links}: codes are 4 to 8 digit OTPs, most likely first; links are https URLs such as verification links. Only messages received after `after` (default: now) match, so pass the inbox's created_at if the email may already be there. With the catch-all inbox (any address @{code}.runearc.email), pass `to` with the address you signed up with. Errors: wait_timeout (nothing matched in time: safe to call again, or loosen from/subject_contains), invalid_timeout, not_found (inbox). Next: enter codes[0] or open the verification link.

NameTypeReqDescription
afterstring|null–Only match messages received after this RFC 3339 time, such as the inbox's created_at. Default: when this call starts. Set it when the email may already have arrived.
fromstring|null–Only match senders whose address contains this, case insensitive, such as "github.com".
inbox_idstringyesInbox id to watch, such as "ibx_01j9...".
subject_containsstring|null–Only match subjects that contain this, case insensitive, such as "verify".
timeout_secondsinteger|null–Seconds to wait, 1 to 120. Default 60.
tostring|null–Only match mail sent to this exact address (envelope recipient, To or Cc), such as "signup-42@k7m3qz.runearc.email". Lets several waits share the catch-all inbox.

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.