Japan External Execution

Registre officiel Sécurité

Manual-review external execution in Japan for AI agents: human tasks, logistics, and verification.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http japan-external-execution 'https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "japan-external-execution": {
            "type": "http",
            "url": "https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Japan External Execution Probe
  2. Generic intake
  3. Validated specialized path
  4. Distribution
  5. Execution core
  6. Generic external-execution probe

Japan External Execution Probe

AI-discoverable manual-review intake for external execution in Japan.

The current decision frontier is no longer “is store-stock checking frequent enough?” It is: what external work do AI agents naturally try to outsource when they cannot complete the next step digitally?

Generic intake

The public Remote MCP exposes:

  • request_external_execution
  • get_external_execution_status
  • cancel_external_execution_request

The create tool accepts a free-form objective, optional location, optional max_budget_jpy metadata, deadline, evidence requirements, constraints, and a retry-safe idempotency key.

Requests enter pending_review. No payment, purchase, worker hire, contract, or fulfillment commitment is created automatically.

Validated specialized path

Physical verification in Japan remains the first validated execution path:

  • store presence / opening checks
  • product stock checks
  • displayed price checks
  • permitted non-sensitive photos
  • simple visual verification

Existing verification tools remain available.

Distribution

Execution core

The bounded execution core runs on a dedicated Supabase project, separate from Affiliate Factory production. Requests are retry-safe, manually reviewed, capability-token mediated, and can return private signed evidence when completed.

Generic external-execution probe

The live MCP now exposes request_external_execution, get_external_execution_status, and cancel_external_execution_request.

The generic intake intentionally does not promise that every submitted category can be fulfilled. It exists to observe what external capabilities AI agents actually request. Every request enters manual review; no automatic payment, hiring, or fulfillment commitment occurs.

Physical verification remains the first execution path that has been verified end-to-end.

Questions fréquentes

Qu'est-ce que Japan External Execution ?

Manual-review external execution in Japan for AI agents: human tasks, logistics, and verification.

Comment installer Japan External Execution ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http japan-external-execution 'https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Japan External Execution ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Japan External Execution est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient Japan External Execution ?

Il est publié par furoito. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.