Skip to content
KurodaLab logo

KurodaLab

Tools for App Store month-end close, CSV release coverage checks, and Wix Bookings slot recovery.
At a glanceswept Oct 16, 2026

≈ 1visits/mo

Little sign of use · estimate, read Oct 16, 2026

For
developers handling App Store month-end and release work, and operators running Wix Bookings sites
Used for
  • run App Store month end close
  • check release coverage from a CSV file
  • recover open slots in Wix Bookings
Worth knowingcomputed from what we read · each with its source
  • Has an MCP server (1 in the registry)public registry →
How a program reaches itfound, not claimed · read Oct 21, 2026
  • MCP servercom.kurodalab/quote-proof-approvalverified in the MCP registry
  • Stateanswers, 13 toolschecked 2026-10-21
  • Address to connectapproval-link-account.kurodalab.com/mcp

MCP server details →

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.

Most used in Financeby use, among tools still maintained — this tool shares no tags yet

Figure and bar: visits/mo, estimate · year: online since

Compare KurodaLab with

Pick up to two.

All 10 alternatives to KurodaLab →

All Finance tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use KurodaLab for?

Sign in to leave a note
Questions this page answers
  • What is KurodaLab?

    Tools for App Store month-end close, CSV release coverage checks, and Wix Bookings slot recovery. It is listed in the Atlas under Finance.

  • Who is KurodaLab for?

    developers handling App Store month-end and release work, and operators running Wix Bookings sites

  • Do people use KurodaLab?

    Little sign of use: ≈ 1 visits/mo · estimate, 2026-10.

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