Japan External Execution MCP server
online · 100% uptimeio.github.furoito/japan-physical-capability·v0.4.3Manual-review external execution in Japan for AI agents: human tasks, logistics, and verification.
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Japan External Execution yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Japan External Execution tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Japan External Execution compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 81/100
- higher than 62% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 561 ms
- faster than 26% of 30,031 servers
Release history: 4 versions in the registry since 2026-10-01, latest 2026-10-02, typically several a day.
Install Japan External Execution in Claude Code, Cursor or VS Code
claude mcp add --transport http japan-physical-capability https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp
What the publisher says
From the Japan External Execution repository's README, as published. We do not edit it. Read it on GitHub
Japan Physical Capability Probe
AI-discoverable pilot capability for physical-world verification in Japan.
This is not a worker marketplace. The service is defined by outcomes: an AI agent or operator specifies what must be verified at a real-world public business location in Japan and receives structured evidence.
Examples:
- check whether a product is actually in stock at a Japanese store
- check the current displayed shelf price
- verify whether a store exists or is open
- obtain recent permitted photos of a storefront or retail display
- resolve a physical-world fact that web search or APIs cannot establish
Pilot scope:
- store presence / opening check
- product stock check
- displayed price check
- requested permitted photos
- simple visual verification
Status: discovery probe / manual pilot. No automatic payment or fulfillment commitment is created by submitting a request.
Machine-readable entry points:
- /llms.txt
- /capability.json
Discovery measurement:
- /discovery-queries.md contains a 60-query benchmark for testing whether an AI can find this capability without being given its name or URL.
Requests: agents should call createverificationrequest through MCP; GitHub Issues remain a manual fallback.
Remote MCP:
- 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
- Tools: checkservicefit, prepareverificationrequest, createverificationrequest, getverificationstatus, cancelverificationrequest
Execution core (live pilot)
The bounded execution core is live on a dedicated Supabase project, separate from Affiliate Factory production. It supports retry-safe request creation, manual review, one-worker claim/completion, private evidence storage, structured result return, and MCP create/status/cancel. No automatic payment or fulfillment commitment is created. See EXECUTION_CORE.md and OPERATIONS.md.
Nothing above is checked by us. What we check is on the safety report.
Japan External Execution: common questions
- Is Japan External Execution MCP server safe?
- Mostly: it is graded B (81/100). Read the Japan External Execution safety report
- How do I install Japan External Execution?
- It runs remotely at bqgfqedetmxrfpvmdfmc.supabase.co. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Japan External Execution need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Japan External Execution maintained?
- The last commit was 34 days ago (2026-10-01). The latest release is v0.4.3.
- Is Japan External Execution up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Japan External Execution compare with other MCP servers?
- safety score 81/100 (higher than 62% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 561 ms (faster than 26% of 30,031 servers). Full comparison.