Japan Company Check

io.github.JusticeUAPublished by GitHub account JusticeUAv0.1.0Updated Nov 7, 2026

Japan company checks by corporate number: status, closure cause, successor, LEI and sanctions.

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that looks up Japanese companies by corporate number, returning status, closure cause, successor, LEI and sanctions data.

What you can do
  • Look up a Japanese company by its corporate number.
  • Retrieve registration status and, where applicable, the cause of closure and any successor entity.
  • Return LEI identifiers and sanctions screening results for the company.
When to use it
Useful when an assistant needs to verify a Japanese counterparty, check whether a company is still active, or screen a supplier or customer against sanctions before onboarding or contracting.
Requirements
Remote streamable HTTP endpoint hosted on Apify. Requires a bearer token in the Authorization header: an Apify API token from the account settings. No local runtime or packages needed.
Before you install
Each check is billed per company to your Apify account, so repeated lookups cost money. The Apify API token is a secret sent in the Authorization header and should be scoped and kept private. Company identifiers and queries are sent to the Apify-hosted service.

Installation

In SourceWeft

  1. Open Japan Company Check 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/io.github.JusticeUA%2Fjapan-company-check/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": {
    "japan-company-check": {
      "type": "http",
      "url": "https://kyb-data--japan-company-check.apify.actor/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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.1.0LatestNov 7, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Check integrations