Skip to content
Jeikin logo

Jeikin

Connects to AI coding tools to find, track and verify accessibility issues in source code, logging evidence on a dashboard.

Actively maintained

At a glanceswept Oct 23, 2026

not read yet

Use

For
Developers and teams using AI coding tools who need accessibility issues found, fixed, and documented
Activity
Actively maintainedsite updated 3 weeks ago
Runs as
CLI
Used for
  • find accessibility issues in source code through an AI coding tool
  • fix flagged WCAG issues and verify each fix passes
  • share compliance evidence with clients, managers, or auditors
Worth knowingcomputed from what we read · each with its source
Your datawhat they publish, each line with its page · read Oct 24, 2026

These are Jeikin'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.

How a program reaches itfound, not claimed · read Oct 24, 2026
  • MCP servercom.jeikin/mcpverified in the MCP registry
  • Stateanswers, requires sign-inchecked 2026-10-24
  • Address to connectjeikin.com/api/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.

Alternatives in Developer toolsby use, among tools still maintained

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

Compare Jeikin with

Pick up to two.

All 10 alternatives to Jeikin →

All Developer tools 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 Jeikin for?

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

    Connects to AI coding tools to find, track and verify accessibility issues in source code, logging evidence on a dashboard. It is listed in the Atlas under Developer tools.

  • Who is Jeikin for?

    Developers and teams using AI coding tools who need accessibility issues found, fixed, and documented

  • Do people use Jeikin?

    Little sign of use.

  • Is Jeikin still maintained?

    Actively maintained: site updated 3 weeks ago.

  • Is Jeikin safe?

    We do not audit vendors. What Jeikin publishes, read 2026-10-24: GDPR, CCPA stated on its privacy policy.

  • What are alternatives to Jeikin?

    In Developer tools, by use: GitLab, Replit, Warp, Blink, Pipedream, Noloco.

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