Tomebound
Tracks your Magic: The Gathering card collection, its prices, decks and storage, and exposes it to AI assistants through an MCP server.
not read yet
Use
- For
- Magic: The Gathering collectors who want to track the cards they own, their value, and their decks
- Price
- Price not read
- Activity
- Activity not read yet
- Company
- Domain since 2026domain registered
- Runs as
- API
- import a collection from a CSV or JSON backup
- scan cards with a phone to add them
- organize decks and storage locations
- Domain since2026domain registered
- Trains on your dataNoprivacy policy ↗
“Tomebound does not sell your data or use it to train AI models.”
privacy policy ↗
These are Tomebound's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
- MCP serverapp.tomebound/tomeboundverified in the MCP registry
- Stateanswers, requires sign-inchecked 2026-10-14
- Address to connectapi.tomebound.app/mcp
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
What is Tomebound?
Tracks your Magic: The Gathering card collection, its prices, decks and storage, and exposes it to AI assistants through an MCP server.
Who is Tomebound for?
Magic: The Gathering collectors who want to track the cards they own, their value, and their decks
Do people use Tomebound?
Little sign of use.
Does Tomebound train AI on your data?
No, per its privacy policy (2026-10-14): “Tomebound does not sell your data or use it to train AI models.”
Is Tomebound safe?
We do not audit vendors. What Tomebound publishes, read 2026-10-14: on training with your data, “Tomebound does not sell your data or use it to train AI models.”.
Not quite it? Describe the job
betaFive tools from the Atlas that fit it, each judged against what you wrote.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.