English Français العربية

Japan E-Commerce Apify MCP (x402 Pay-Per-Call)

Official registry E-commerce

Japan EC Apify MCP. Apify:apify.com/fruitful_quintessence | Gumroad:atushi5.gumroad.com/l/kutuxe

Source code Documentation

What can you do with Japan E-Commerce Apify MCP (x402 Pay-Per-Call)?

  • x402 Micropayments Protocol Support: HTTP 402 / EIP-712 payment authorization for AI agents
  • Apify Actor Integration: Directly connects with fruitful_quintessence/mercari-japan-search-scraper
  • Multi-Transport: Runs over stdio, HTTP / SSE
  • Official MCP Registry Compatible: Registered on modelcontextprotocol.io registry

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

MCPB package https://github.com/atushi1841/japan-ec-apify-mcp/releases/download/v0.2.2/server.mcpb

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. japan-ec-apify-mcp
  2. Features
  3. Installation & Usage
  4. Verification
  5. Related Links
  6. Data & Store

japan-ec-apify-mcp

An x402-enabled Model Context Protocol (MCP) server wrapping Apify Actors for Japanese e-commerce marketplaces (Mercari Japan, Yahoo! Auctions, Rakuten, SUUMO, Kakaku.com).

Enables AI agents (Claude Desktop, Cursor, AutoGPT) to execute paid API searches on-demand using the x402 protocol ($0.001 USDC / call).

Features

  • x402 Micropayments Protocol Support: HTTP 402 / EIP-712 payment authorization for AI agents
  • Apify Actor Integration: Directly connects with fruitful_quintessence/mercari-japan-search-scraper
  • Multi-Transport: Runs over stdio, HTTP / SSE
  • Official MCP Registry Compatible: Registered on modelcontextprotocol.io registry

Installation & Usage

1. FastMCP stdio / Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "japan-ec-apify-mcp": {
      "command": "python3",
      "args": ["/path/to/scripts/mcp_x402_server.py"]
    }
  }
}
2. x402 Payment Flow Example

When calling search_mercari_japan(keyword="CBR250RR"):

  1. Server returns isError: true with x402 PaymentRequired payload ($0.001 USDC required).
  2. Agent signs EIP-712 payment authorization and re-sends request with _meta["x402/payment"].
  3. Server validates payment signature, retrieves Mercari listings, and returns data with _meta["x402/payment-response"].

Verification

python3 -m py_compile scripts/mcp_x402_server.py

Data & Store

Frequently asked questions

What is Japan E-Commerce Apify MCP (x402 Pay-Per-Call)?

Japan EC Apify MCP. Apify:apify.com/fruitful_quintessence | Gumroad:atushi5.gumroad.com/l/kutuxe

How do I install Japan E-Commerce Apify MCP (x402 Pay-Per-Call)?

Follow the installation steps in its documentation, shown on this page and in its repository.

Does Japan E-Commerce Apify MCP (x402 Pay-Per-Call) need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Japan E-Commerce Apify MCP (x402 Pay-Per-Call) open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Japan E-Commerce Apify MCP (x402 Pay-Per-Call)?

It is published by atushi1841. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.