
Crashdx
io.github.r00tifyPublished by GitHub account r00tifyv0.1.0Updated Oct 24, 2026
Diagnoses Apple .ips crash reports: ranks likely causes with cited evidence, not just a stack trace.
Overview
Diagnoses Apple .ips crash reports, symbolicating them against dSYMs and returning ranked, evidence-cited hypotheses about the likely cause.
- What you can do
- Crashdx parses Apple .ips crash reports, symbolicates them against dSYMs, and runs a deterministic rule-based engine that ranks competing hypotheses about the cause, each citing the specific facts that support it. It exposes the same pipeline over stdio as the crashdx_analyze and crashdx_symbolicate tools, returning a structured AnalysisReport. Verdicts are traceable to JSON paths in the original report, and the engine reports "inconclusive" when no hypothesis is clearly ahead.
- When to use it
- Useful when triaging Apple platform crashes and you want a ranked, checkable diagnosis rather than a raw symbolicated stack trace. Suited to macOS development workflows, CI parsing of crash reports, and agent-assisted crash triage where the reasoning should be auditable.
- Requirements
- macOS 14 or later, a Swift 6.2+ toolchain, and Xcode (not just Command Line Tools) for full symbolication via CrashSymbolicator.py; without Xcode it falls back to atos. Also needs /usr/bin/python3 and /usr/bin/dwarfdump. Runs locally over stdio; no accounts, API keys, or network access.
Installation
In SourceWeft
- Open Crashdx in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
35% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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.
- License10 pts