NoCrash

io.nocrashPublished by nocrash.ioOfficial publisherv1.0.1Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowSecurity & Monitoring

Overview

AI-generated overview

NoCrash is a remote MCP endpoint that lets an assistant check on n8n workflows, URLs and AI apps so failures are caught before customers notice.

What you can do
  • The manifest lists no tools, so capabilities come from the provider's description only.
  • The server is positioned around monitoring n8n workflows, web URLs and AI apps for breakage.
  • It is meant to surface failures early, before customers encounter them.
  • No further tool-level detail is published in the supplied material.
When to use it
Consider it if you run n8n automations, public URLs or AI apps and want an assistant to help you stay aware of outages or breakage before users report them.
Requirements
A remote MCP endpoint at nocrash.io over streamable HTTP; no local package or runtime is needed. Authentication is required: a NoCrash API key sent as a Bearer token in the Authorization header, created on the provider's API keys page.
Before you install
The connection requires a NoCrash API key in the Authorization header, so treat it as a secret and avoid exposing it in shared logs or configs. The published material does not describe which monitoring data is read or whether any actions change state, so review the provider's terms before connecting.

Installation

In SourceWeft

  1. Open NoCrash in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.nocrash%2Fnocrash/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "nocrash": {
      "type": "http",
      "url": "https://nocrash.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.