NoCrash Monitor

Name: NoCrash Monitor
Author: nocrash

Know when your n8n workflows, URLs, and AI apps break, before your customers do

OCR

该来源不提供完整文件导出（国内平台多为平台内托管），仅存元数据与原链

模型生成摘要（rules/v1 · 2026-10-01 13:05）：Know when your n8n workflows, URLs, and AI apps break, before your customers do
这是模型对公开材料的总结，不是官方声明，请以原链内容为准。

接入信息

传输形态: http
鉴权方式: 需 API Key（探测：需要鉴权（HTTP 401））
端点: https://monitor--nocrash.run.tools

该服务需要凭证，请按官方文档申请后替换占位符

{
  "mcpServers": {
    "NoCrash Monitor": {
      "headers": {
        "Authorization": "Bearer \u003cYOUR_KEY\u003e"
      },
      "url": "https://monitor--nocrash.run.tools"
    }
  }
}

能力清单

工具	说明
nocrash_list_watches	List every watched item with its current status (green/yellow/red), optionally filtered by status. Also returns an overall health summary using the same display buckets (needs_help, needs_a_look, fine, waiting) the dashboard and nocrash_get_health show, so totals never contradict across tools. Each watch includes `last_error_message` (most recent error seen, regardless of current status) and `last_error_state` ("current" or "resolved"); both are nil when the watch has never errored.
nocrash_get_health	Get overall health across every watched item — total count, counts by dashboard bucket (needs_help, needs_a_look, fine, waiting), overall status, last check time, and a plain-language one-liner. Counts use the same display-status precedence as the dashboard, so `needs_help` excludes never-pinged or unreachable items that still carry stale raw-red status.
nocrash_get_watch	Get full details for one watched item: schedule, recent activity, error history, and next expected run. `last_error_message` is the most recent error string seen, regardless of current status; use `last_error_state` ("current" or "resolved") to tell whether it's the current problem or already cleared. Both are nil when the watch has never errored.
nocrash_list_events	List event history across your watched items — filter by watch, by event type, or pass `event_id` to fetch a single event in full detail. Event types span the full range NoCrash watches for: routine check-ins, failures, recoveries, missed runs, silent step-level breakage, workflow on/off changes upstream, and browser-side errors from vibe-coded apps (script crashes, unhandled promise rejections, failed network calls, page loads).
nocrash_get_brief	Get the latest daily brief — the most recently generated plain-language summary of what happened overnight across your watched items. Read-only; never triggers fresh AI generation.
nocrash_search_errors	Search every error event by keyword. Matches against error messages, failing node names, plain-language error context, and AI-suggested fixes across all your watched items.
nocrash_send_ping	Send a heartbeat for a watched item to confirm the workflow is running. This is a write — it resets the failure count and updates status to green.
nocrash_report_failure	Report that a workflow failed. Records the error and updates the watched item's status. Include as much detail as possible — error message, failing step, and any context an agent or human will need to debug.
nocrash_refresh_watch	Force a fresh check of a watched item now instead of waiting for the next scheduled poll. Shares the dashboard refresh cooldown — 60-second wait between refreshes and a 10-per-hour ceiling per connection. Push-based watches (JS snippet) update on their own when data arrives and can't be refreshed on demand. The refresh runs asynchronously, so the new status appears on the item a few seconds later.

NoCrash Monitor

接入信息

能力清单

相关资产

SaSame Research

extend

OCR Text Extraction — Image to Text, Multi-Language

Contendeo

GoCreative Agent API

PennyOCR