📡 MCP Radar

r00tify/crashdx

A deterministic crash diagnosis engine for .ips reports (CLI + MCP server)

7 stars
0 forks
Swift
momentum ▲ 14.0
created 2026-07-23
on radar since 2026-07-24
star trend 5 → 7 since 2026-07-24
clicrash-reportingdebuggerdebuggingdebugging-toolipsmcpmcp-servermcp-toolsswiftswift-packagesymbolicatecrashsymbolication
View on GitHub ↗

About crashdx

A crash diagnosis engine for Apple platforms: parses .ips crash reports, symbolicates them against dSYMs, and produces an evidence-cited, ranked diagnosis, not just a symbolicated stack trace.

Ships as a dependency-free Swift library (CrashDXCore imports only Foundation), a CLI (crashdx), and an MCP server (crashdx-mcp), so agents and humans use the same engine.

A symbolicated stack trace tells you where a process died, not why. crashdx adds a second stage on top of symbolication: deterministic, rule-based evidence extraction (watchdog budgets, jetsam tables, register and memory state, lastExceptionBacktrace/asi) feeding a ranked set of competing hypotheses, each citing the specific facts that support it and pointing back into the raw report.

Two properties it holds onto deliberately:

- Every claim is traceable. Facts carry a JSON path into the original report, so any verdict can be checked rather than trusted. - It says "inconclusive" when it is. A verdict requires the leading hypothesis to be strongly supported and clearly ahead of the runner-up; otherwise you get the ranked candidates and what would settle it.

There are no LLM calls in the engine: it produces verifiable facts and ranked interpretations, and leaves the narrative to whatever consumes them. See docs/DESIGN.md for the full architecture.

- macOS 14+ - Swift 6.2+ toolchain. The manifest itself is swift-tools-version:6.0, but the MCP server's pinned dependencies declare up to 6.2, and SwiftPM resolves the whole package graph, so 6.2 is the real floor for every target, including CrashDXCore. - Xcode (not j

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/r00tify--crashdx.html)

Related MCP servers

priyansh-narang2308/TheBlacklisted-NitroStack

Protocol-0 is an MCP (Model Context Protocol) server that gives AI assistants, Claude, Cursor, ChatGPT, NitroChat, or any MCP-compatible client, real authority to act as your Site Reliability Engineer

⭐ 4TypeScript
vshulcz/deja-vu

Your agents already solved this. deja finds it — retroactive search and MCP recall over the session logs your coding agents already wrote. Cross-agent, SSH-portable, one zero-dep binary, fully local.

⭐ 391Go
taurus42119-stack/godkiller-mcp

Your coding agent gaslights you. GODKILLER doesn't. Disk gates > vibes. claim_done only after verify.

⭐ 14Python
anshupriyan/cli-bridge

MCP server for Claude Desktop and other Model Context Protocol clients — sandboxed filesystem access (read/write/edit/search) plus Dev Mode-gated shell command execution, scoped to a single workspace

⭐ 12TypeScript
12122J/mcpvet

MCP security scanner — vet a Model Context Protocol server before you add it to Claude Code, Cursor, or Windsurf. Grades it A–F, catching credential theft, tool-poisoning, and install-script payloads

⭐ 10JavaScript
Dragkob/MCPhantom

MCPhantom is a local web dashboard for MCP endpoint recon. Discover resources, templates, tools, and prompts, then interact with them from a security console.

⭐ 6Python

📬 Get the weekly radar in your inbox

The top new MCP servers of the week, every Monday. No spam, unsubscribe anytime.