NoCrash Monitor

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

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • 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_he
  • 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-langu
  • 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 curr

What data it sees

Do you need an account

No: the server works without sign-in

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

How to connect

How to connect NoCrash Monitor to Claude

The server address to paste into Claude settings:

https://monitor--nocrash.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect NoCrash Monitor to ChatGPT

The server address to paste into ChatGPT settings:

https://monitor--nocrash.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect NoCrash Monitor to Cursor

The server address to paste into Cursor settings:

https://monitor--nocrash.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (9)

Raw names from tools/list. Only developers need these.

nocrash_list_watchesList 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_healthGet 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_watchGet 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_eventsList 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_briefGet 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_errorsSearch 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_pingSend 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_failureReport 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_watchForce 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.