EDHcheck started as a personal hobby build for Commander nights. I wanted something fast and practical that helps answer the most common table question: "What bracket/power is this deck actually in?"
Instead of relying only on vibes, EDHcheck gives a structured snapshot of a list. It tries to help with pre-game clarity, pod matching, and post-game tuning.
What EDHcheck can do right now
- Analyze decklists and return a bracket estimate plus power score.
- Surface notable signals like combo presence, tutors, fast mana, and salt profile.
- Show breakdowns that are easy to scan before a game.
- Import decklists from text and Archidekt URLs (Moxfield import is currently not working and will be revisited).
- Save and reopen your own analyzed decks when logged in.
How calculations work (high-level)
The exact formula is intentionally kept lightweight here, but the system combines multiple signals instead of depending on one number.
At a high level, it weighs deck speed, consistency indicators, combo potential, and card pattern signals to estimate where a list lands. It is not a replacement for Rule 0, but a support tool for better conversations.
Data and APIs used
EDHcheck relies on external sources to keep data current and practical:
- Scryfall: card data, oracle text, imagery, and related metadata.
- Commander Spellbook: combo references used during analysis.
- Archidekt import endpoint support for direct URL imports.
If one API is slow or unavailable, results can vary in detail level. Improving resilience around this is ongoing.
Logging in and account safety
If you log in, your saved deck data is handled through Firebase services. Authentication and storage are managed through Firebase infrastructure, and the app only stores what is needed for the feature set (saved deck content and associated analysis state).
In short: login exists to support deck saving and retrieval, not to collect unrelated personal data.
Feedback, critique, and suggestions
I am very open to critique and feature suggestions. If you notice weird edge cases, missing cards, wrong classifications, or UI problems, that feedback is genuinely useful and appreciated.
This project improves fastest when people share real pod scenarios and examples.
Please treat outputs as guidance (beta)
EDHcheck is still in beta. Always treat analysis results as directional and use your own pod context and judgement. Commander tables vary a lot, and no model is perfect.
Project intent
This is not intended to compete with or interfere with other deck analysis projects. It is primarily a personal project I use myself, made public in case it helps others.
Since this post, EDHcheck has grown a lot — there's now a full deck builder (read the launch update), Moxfield imports are working again, and there's a blog covering brackets, mulligans, ramp, and removal. Paste a list at edhcheck.com or browse community decks to see it in action.
If you enjoy using EDHcheck and want to support ongoing improvements, you can buy me a beer here.