Is the Runearc MCP server down?

mcp-registry/io.github.runearc-labs/runearc · registry v1.0.0 · server reports v0.1.0

Also listed as github/runearc-labs/runearc-mcp

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 19:03 UTC · handshake 310ms

As of 2026-11-22 19:03 UTC, the Runearc MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
725
outages (90d)
0
tools
90

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

Point your MCP client at this streamable-http endpoint: https://mcp.runearc.com/mcp

Agent-readiness: B (80/100)

B (80/100): 0 error(s), 4 warning(s) across 90 tool(s); ~18,231 tokens of tool definitions.
Scores higher than 24% of 27,664 MCP servers Glimind has audited.
Its tool list costs an agent ~18,231 tokens per session — more than 90% of servers.
80 → 80 since 2026-11-17
no tool-poisoning patterns
Descriptions82
Safety hints100
Schemas84
Protocol100
Stability100
Token cost35
Reliability100
Client compatibility70

What to fix (5)

90 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

10 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: bulk_contacts, create_event_definition, create_goal, create_segment, create_sync_rule and 5 more

19 parameter(s) across 10 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: add_contact, create_list, delete_segment, generate_sequence, list_contacts and 5 more

Loading this server's tool list costs an agent ~18,231 tokens before any work — more than 90% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 10 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 10 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.runearc-labs%2Frunearc/fixes

bulk_contacts 1 change
{
  "name": "bulk_contacts",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "action"
    ],
    "properties": {
      "tags": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "default": [],
        "description": "For \"tag\": the tags to add."
      },
      "action": {
        "type": "string",
        "description": "\"tag\", \"add_to_list\", \"unsubscribe\" or \"delete\"."
      },
      "emails": {
        "type": [
          "array",
          "null"
        ],
        "items": {
          "type": "string"
        },
        "default": null,
        "description": "Email addresses of contacts."
      },
      "list_id": {
        "type": [
          "string",
          "null"
        ],
        "default": null,
        "description": "For \"add_to_list\": the list id (lst_...)."
      },
      "contact_ids": {
        "type": [
          "array",
          "null"
        ],
        "items": {
          "type": "string"
        },
        "default": null,
        "description": "Contact ids (ctc_...). Give exactly one of contact_ids, emails or all_matching."
      },
      "all_matching": {
        "default": null,
        "description": "Act on every contact matching this filter {q, status, tag, list_id}; {} means all contacts.",
        "type": "string"
      }
    }
  },
  "annotations": {
    "title": "Bulk update contacts",
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": true
  },
  "title": "Bulk update contacts"
}
create_event_definition 1 change
{
  "name": "create_event_definition",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "The event name, such as \"plan_upgraded\"."
      },
      "properties": {
        "default": null,
        "description": "Documentation of the properties: [{\"name\": \"plan\", \"type\": \"string\"}]. Not enforced.",
        "type": "string"
      },
      "description": {
        "type": [
          "string",
          "null"
        ],
        "default": null,
        "description": "What the event means."
      }
    }
  },
  "annotations": {
    "title": "Create event definition",
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": false,
    "destructiveHint": false
  },
  "title": "Create event definition"
}
create_goal 1 change
{
  "name": "create_goal",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "name",
      "event_name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "A unique name, such as \"Upgraded to pro\"."
      },
      "conditions": {
        "default": null,
        "description": "Optional property conditions, same shape as for sync rules.",
        "type": "string"
      },
      "event_name": {
        "type": "string",
        "description": "The event that counts as a conversion."
      },
      "window_days": {
        "type": [
          "integer",
          "null"
        ],
        "format": "int32",
        "default": null,
        "description": "Attribution window in days, 1 to 90 (default 7): an email sent or clicked this long before gets the credit."
      },
      "value_property": {
        "type": [
          "string",
          "null"
        ],
        "default": null,
        "description": "Property holding the revenue of the event, such as \"amount\"."
      }
    }
  },
  "annotations": {
    "title": "Create goal",
    "readOnlyHint": false,
    "openWorldHint": false,
    "idempotentHint": false,
    "destructiveHint": false
  },
  "title": "Create goal"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.runearc-labs/runearc"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.runearc-labs/runearc"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.github.runearc-labs%2Frunearc.svg)](https://glimind.com/server/mcp-registry%2Fio.github.runearc-labs%2Frunearc?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.runearc-labs%2Frunearc?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.runearc-labs%2Frunearc.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:eb442a309906de2c…, first seen 2026-11-17, included at leaf 312445 of 384,944. Version history · verify what your client received.

Tools (90)

Compare: most reliable communication servers · most reliable email servers · most reliable other servers · most reliable marketing servers · most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Runearc MCP server down right now?

As of 2026-11-22 19:03 UTC, the Runearc MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Runearc MCP server provide?

Runearc MCP server advertises 90 tools, including activate_sequence, add_contact, add_domain, add_to_list, bulk_contacts.

How do I install Runearc MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.runearc.com/mcp

Is the Runearc MCP server safe to connect to an AI agent?

Glimind scanned all 90 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Runearc MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve