MCP servers observed by Lowdown
io.github.runearc-labs/runearc MCP server: daily status and tool changes
Answered initialize and tools/list on the only check recorded in the last 30 days (2026-11-18) (Lowdown checks this server every 3 days); 90 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-18; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.runearc-labs/runearc
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.runearc-labs/runearc?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 1
- Answered initialize and tools/list: 1
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 1 observed days. Lowdown checks without credentials.
Did its tools change recently?
Fewer than two days with a complete tools/list observation from the same remote, so nothing was compared.
What tools does it list?
90 tools on 2026-11-18:
activate_sequenceadd_contactadd_domainadd_to_listbulk_contactscancel_campaignconnect_billing_integrationcreate_campaigncreate_event_definitioncreate_formcreate_goalcreate_inboxcreate_listcreate_pagecreate_popupcreate_segmentcreate_sequencecreate_sync_rulecreate_templatecreate_webhookdelete_inboxdelete_pagedelete_segmentdelete_sync_ruledraft_welcome_sequenceenroll_contact_in_sequencegenerate_emailgenerate_sequenceget_ai_contextget_analyticsget_email_designget_email_trackingget_importget_inboxget_messageget_pageget_sequenceget_threadget_tracking_settingsgoal_statsimport_contactsimport_siteinstall_starter_sequencelist_billing_integrationslist_campaign_designslist_campaignslist_contact_eventslist_contactslist_domainslist_event_definitionslist_form_submissionslist_formslist_goalslist_inboxeslist_listslist_messageslist_pageslist_segmentslist_sequenceslist_suppressionslist_sync_ruleslist_templateslist_threadspause_campaignpause_sequencepopup_statspreview_segmentpublish_pageremove_billing_integrationrender_email_previewreplyresume_campaignsend_campaignsend_campaign_testsend_emailsend_templateset_email_designset_sequence_stepstag_contactstrack_eventturn_on_welcome_sequenceunpublish_pageunsubscribe_contactunsubscribe_contactsupdate_campaignupdate_contactupdate_pageupdate_tracking_settingsverify_domainwait_for_email
MCP Registry declaration
- Registry name:
io.github.runearc-labs/runearc - Declared version: 1.0.0
- Status: active
- Declared hosts:
mcp.runearc.com
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.runearc-labs/runearc", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.runearc-labs/runearc?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).