Japan Food Delivery MCP

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

Japan food delivery da Apify:apify.com/fruitful_quintessence | Gumroad:atushi5.gumroad.com/l/kutuxe

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

A local MCP server for Japan food delivery, packaged as an MCPB bundle; the supplied description and README give no tool list or usage details.

What you can do
The manifest lists no tools, and the description and README do not explain any operations, so what an assistant can actually do with it is not documented here. The README mostly lists the provider's other Apify actors (market, auction and price scrapers) and links to an Apify store and a Gumroad dataset page. The name suggests a Japan food delivery purpose, but no ordering, search or menu capabilities are described.
When to use it
Only consider it if you specifically want a Japan food delivery integration and are willing to inspect the package yourself, since the available material does not show what it does.
Requirements
Runs as a local process on the user's machine via a desktop MCPB package; no authentication, environment variables or headers are declared.
Before you install
The description and README are largely promotional, pointing to Apify and Gumroad pages, and no tools or data handling are documented. Review the package before installing and do not assume any ordering or payment behavior is safe.

Installation

In SourceWeft

  1. Open Japan Food Delivery MCP 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-food-delivery-mcp

MCP Registry

This server is registered on the official MCP Registry. Find it via search: japan-food-delivery-mcp

Apify Store


Data & Store

Source: README.md at commit c5cffb4

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

4
  1. v0.3.6LatestOct 24, 2026
  2. v0.3.5Oct 23, 2026
  3. v0.3.3Oct 22, 2026
  4. v0.1.0Oct 10, 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.