Jeikin

com.jeikinPublished by jeikin.comOfficial publisherv0.3.1Updated Oct 24, 2026

Accessibility compliance for AI coding tools. WCAG 2.2 reviews with shared evidence.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint from Jeikin that gives AI coding tools WCAG 2.2 accessibility compliance reviews with shared evidence.

What you can do
  • Run WCAG 2.2 accessibility compliance reviews on web work from an AI coding tool.
  • Share review evidence so findings can be referenced and discussed.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to check web pages or UI work against WCAG 2.2 and keep the resulting evidence in one shared place, for example during accessibility remediation or review handoffs.
Requirements
A remote streamable HTTP endpoint at jeikin.com; no local package or runtime is needed. A Jeikin project and a bearer token issued from the project settings, sent in the Authorization header.
Before you install
The Authorization header carries a secret bearer token; keep it private and revoke it if exposed. Reviews are tied to a Jeikin project account, and page content submitted for review is sent to Jeikin's service.

Installation

In SourceWeft

  1. Open Jeikin in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.jeikin%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "jeikin": {
      "type": "http",
      "url": "https://jeikin.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.3.1LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.