CLUSTER MIFARE-CLASSIC-NFC · 5 ENTRIES · EARLIEST ENTRY 2013-12-09
MIFARE Classic RFID tools
This cluster consists of tools for reading, writing, analyzing, and cloning MIFARE Classic RFID cards, including key recovery and balance checking. The dated history before the index start is too thin to read a shape from—only three dated entries exist, so the cluster predates the index or its members are undated. Traction leaders are nfcx, MTools BLE RFID Reader, and MFC Balance, each with 0 stars.
Entry timeline
ENTRY TIMELINE
Each bar is the month a member carries, which is a creation date where the source published one and a crawl date otherwise. Nothing in the index was found before 11 August 2026, and coverage broadened sharply on 14–15 August, so a bar from then on reports how much we found that month, not how much was built; an earlier bar reports how far back a member's own source dated it — not how long we have been watching.
Members by activity
Activity signals, not revenue.
Build origin · 5 unlabelled
Operator · 3 open source · 2 unlabelled
Two labels per entry, never collapsed into one: how it was built, and who stands behind it. Counted over the 5 listed below. Unlabelled means nothing has decided yet — not that the answer is small.
- 01nfcx0★1 moliveopen sourceNFC workbench tool for reading and analyzing MIFARE Classic cards, including key recovery.
- 02EmuGrooveTag0★19 days—NFC tag emulator that mimics Mifare Classic and ISO15693 tags from common card dump files for security testing and access control.
- 03MTools BLE RFID Reader0★1 moliveMobile app for RFID and NFC enthusiasts that reads, writes, and manages Mifare and other tags through Bluetooth hardware devices.
- 04MIFARE Classic Tool0★8 mostaleliveopen sourceAndroid app for reading, writing, analyzing, and cloning MIFARE Classic RFID tags with key management and formatting.
- 05MFC Balance0★1 yrabandonedliveopen sourceNFC reader app that checks the balance on MIFARE Classic cards.
Ranked by traction, highest first, and paged 20 at a time — this is a window on the cluster, never the whole of it. Ties are broken by a stable id so a product cannot appear on two pages or fall between them. Browse every cluster.