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

io.github.atushi1841Published by GitHub account atushi1841v0.2.7Updated Oct 24, 2026

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

The publisher's own server: Apify MCP Server

Overview

AI-generated overview

A local MCP server that lets an assistant run paid Apify searches on Japanese e-commerce marketplaces, charging per call via the x402 micropayment protocol.

What you can do
Run keyword searches on Japanese marketplace data through Apify Actors, such as Mercari Japan, Yahoo! Auctions, Rakuten, SUUMO and Kakaku.com, and return the listings to the assistant. Handle x402 payment: the first call returns a PaymentRequired payload, the agent signs an EIP-712 authorization, and the request is re-sent with the payment attached. Serve over stdio or HTTP/SSE.
When to use it
Useful when an assistant needs on-demand Japanese marketplace or e-commerce listing data and the user is willing to pay a small per-call fee in USDC rather than manage an Apify account directly.
Requirements
Runs as a local process, launched with python3 against the server script; the manifest ships an mcpb package. Needs network access to Apify and the x402 payment flow, and a wallet able to sign EIP-712 payment authorizations in USDC.
Before you install
Every search costs money: the README states $0.001 USDC per call, paid through x402 micropayments, so repeated calls spend funds. The agent must sign payment authorizations with a wallet, which is a sensitive credential. Search terms are sent to Apify Actors and third-party marketplace sources.

Installation

In SourceWeft

  1. Open Japan E-Commerce Apify MCP (x402 Pay-Per-Call) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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:

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

bash
python3 -m py_compile scripts/mcp_x402_server.py

Related Links


Data & Store

Source: README.md at commit 6bcc314

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

5
  1. v0.2.7LatestOct 24, 2026
  2. v0.2.6Oct 22, 2026
  3. v0.2.2Oct 18, 2026
  4. v0.2.0Oct 18, 2026
  5. v0.1.0Oct 17, 2026

Score

40% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Apify integrations