Skip to content

KIKARET

Gives AI clients facts on Japanese nurseries and kindergartens, with source links and confidence metadata, via a public MCP endpoint.

HealthAPIFor developers
kikaret.ai ↗
At a glanceswept 2026-10-12

not read yet

Use

For
Developers and AI clients needing source-backed facts about Japanese childcare facilities, reached through a public MCP server.
Price
Price not read
Activity
Activity not read yet
Company
Domain since 2026domain registered
Runs as
API
AlternativesSet it up for my teamIs KIKARET yours? Claim the card →
What people do with it
  • look up capacity and opening hours for Japanese kindergartens
  • retrieve accepted ages and contact details for nurseries
  • query childcare facility facts through a public MCP server
The companyeach fact with its source · read 2026-10-13
  • Domain since2026domain registered
How a program reaches itfound, not claimed · read 2026-10-13
  • MCP serverai.kikaret/mcpverified in the MCP registry
  • Stateanswers, 4 toolschecked 2026-10-13
  • Address to connectmcp.kikaret.ai/mcp

MCP server details →

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.

Alternatives in Healthby use, among tools still maintained

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

All Health tools →

Questions this page answers
  • What is KIKARET?

    Gives AI clients facts on Japanese nurseries and kindergartens, with source links and confidence metadata, via a public MCP endpoint. It is listed in the Atlas under Health.

  • Who is KIKARET for?

    Developers and AI clients needing source-backed facts about Japanese childcare facilities, reached through a public MCP server.

  • Do people use KIKARET?

    Little sign of use.

  • What are alternatives to KIKARET?

    In Health, by use: Agentlookups, Thrive Team AI, Heidi Health, AI DiagMe, Freed, Patient Notes AI.

Not quite it? Describe the job

beta

Five 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.