WIPE
not read yet
Use
- Runs as
- Mobile app
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantsiw.pe ↗
- MCP serverpe.iw.around/businessesverified in the MCP registry
- Stateanswers, 2 toolschecked 2026-10-26
- Address to connectaround.iw.pe/mcp
- OpenAPI spec1 pathsthe spec ↗
This card as JSON, for your agent →
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.
Figure and bar: visits/mo, estimate · year: online since
- #1
Expo
Build and deploy native iOS and Android apps from a single React codebase with cloud infrastructure and over-the-air updates.
146kActiveFrom $19/mo2015 - #2
ScanditMCP · sign-in
Scans barcodes, labels and ID documents through a phone or browser camera using on-device vision, feeding store inventory and self-checkout data.
106kActiveFree plan2009 - #3
GoodBarber
Builds native iOS and Android apps without coding, with hosting and app store publishing included.
39.2kActiveFrom ≈ $34/mo2011 - #4
Adalo
Builds native iOS, Android, and web apps visually without code, with AI assistance.
28.7kActiveFrom $36/mo - #5
Ably
Provides pub/sub messaging, presence and state sync APIs over WebSockets for building live features into apps.
20.3kActiveFrom $29/mo2016 - #6
Mem0MCP · sign-in
Stores and retrieves persistent memories of users and sessions for AI agents and applications through an API and open-source SDK.
16.8kActiveFrom $19/mo2023
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use WIPE for?
Sign in to leave a noteWhat is WIPE?
Mobile apps for beauty, care and art, distributed through the App Store and Google Play. It is listed in the Atlas under Developer tools.
Do people use WIPE?
Little sign of use.
What are alternatives to WIPE?
In Developer tools, by use: Expo, Scandit, GoodBarber, Adalo, Ably, Mem0.
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.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.