Japan External Execution
Manual-review external execution in Japan for AI agents: human tasks, logistics, and verification.
One address for any MCP client. No sign-in needed on this server.
What it does
3 read4 act1 other
Grouped by tool name.
What it costs
FreeOdel charges nothing per call. The publisher may charge for its own service.
Tools
8 · grouped by tool name · checked 2 Oct 2026Read · 3Look things up
- check_service_fit
- get_verification_status
- get_external_execution_status
Act · 4Change something
- prepare_verification_request
- create_verification_request
- cancel_verification_request
- cancel_external_execution_request
Other · 1Neither hinted nor named
- request_external_execution
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_executionget_external_execution_statuscancel_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
- Registry name:
io.github.furoito/japan-physical-capability - Transport: Streamable HTTP
- Endpoint:
https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp - Official MCP Registry: https://registry.modelcontextprotocol.io/?q=io.github.furoito%2Fjapan-physical-capability
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.
