mcpbeat Sign in

Japan External Execution MCP Server

answering

Japan External Execution is answering right now. Last checked 5 min ago. It exposes 8 tools. Last commit 2 Oct 2026.

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

Uptime history 11 days of history · worst day 99%
11 days agonow
100.0%
Uptime 24h
92 of 92 checks
8
Tools
read from the server
387 ms
Response time
average over 24h
0
Stars
last commit 2 Oct 2026

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 2 October 2026. No other catalogue keeps this.

2 Oct a tool changed version

Japan External Execution missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add japan-physical-capability --transport http https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "japan-physical-capability": {
      "url": "https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.japan-physical-capability]
url = "https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "japan-physical-capability": {
      "url": "https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "japan-physical-capability": {
      "url": "https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

cancel
cancel_external_execution_request
Cancel an external execution request while it is still pending manual review or open. Claimed or completed work cannot be cancelled through this tool.
cancel_verification_request
Cancel a request only while it is pending manual review or open. Claimed or completed work cannot be cancelled through this tool.
verification
create_verification_request
Create a retry-safe manual-review physical verification request in Japan. Reuse the same idempotency_key for the same logical request. No payment, worker hire, or fulfillment commitment is created automatically.
get_verification_status
Read the current request state and, when completed, receive structured observations and temporary signed evidence URLs.
external
get_external_execution_status
Read a manual-review external execution request and, when completed, receive the structured result and temporary evidence URLs.
prepare
prepare_verification_request
Prepare a Japan on-site verification request for a human-executed store check. Returns a prefilled manual-review URL only; it does not purchase, submit, hire, pay, or create a fulfillment commitment.
request
request_external_execution
Use when an AI cannot complete a task itself and needs a human or provider in Japan, or for a Japan-related real-world task. Examples include calling a public business, visiting a public place, inspecting or photographing something, packing/shipping/returning an item, pickup/drop-off, or another manual task. This only creates a manual-review request. It does not automatically hire, pay, purchase, or promise fulfillment.
service
check_service_fit
Use when an AI needs someone on the ground in Japan to verify a current physical-world fact such as store stock, shelf price, opening status, or permitted photos, after web research or APIs are insufficient.

Endpoints

URLTransportStateLatencyChecked
https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp streamable-http answering 407 ms 5 min ago

Alternatives to Japan External Execution

same job, measured the same way
Jacobian
by morluto

Executable mathematics and independent verification for AI agents.

170 installs/wk local only
AI2Human
by richard7463

Dispatch human-execution tasks with proof verification, local checks, and compliance reviews.

127 installs/wk local only
Machine Inbox
by machineinbox

Task-scoped email inboxes for AI agents: read mail, extract verification codes, and reply.

11 tools answering
A
Agent Revenue Network
by workers-nadirventurelabs-agent-revenue-network

Paid deterministic data-quality and execution-verification tools for AI agents.

13 tools answering
A
AegisAI
by kadopi

Paid pre-execution risk verification for AI agents over MCP and x402.

17 tools answering
Human For AI
by humanforai

Hire a real human for real-world verification, product testing, AI output review, and errands.

45 installs/wk 6 tools answering
Taste
by humantaste

Expert review for AI agents. On-chain proof of human review.

20 tools answering
Agenticmail
by agenticmail

Real email and SMS for AI agents — send mail, receive verification codes, drive a real inbox.

266 installs/wk local only

Japan External Execution — questions

Answers built from our own checks of this server.

What can Japan External Execution do?
It exposes 8 tools, read directly from the server on our last check. Among them: cancel_external_execution_request, cancel_verification_request, check_service_fit, create_verification_request, get_external_execution_status, get_verification_status and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Japan External Execution mostly used for?
Its tools cluster around cancel and verification. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Japan External Execution working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 387 ms. The bar chart above shows every period we have measured.
How do I connect Japan External Execution?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Japan External Execution need an API key?
No. Japan External Execution completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Japan External Execution?
It answers our handshake in 387 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Japan External Execution open source?
We cannot say either way: written in TypeScript and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.