Japan External Execution
REMOTE · BQGFQEDETMXRFPVMDFMC.SUPABASE.CO
Manual-review external execution in Japan for AI agents: human tasks, logistics, and verification.
Available components
Last scanned (12 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category IoT and Hardware
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_verification_request). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 750 tokens (~93/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 45% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d2b50611cd88e9c50e4e2231f4d3f059 |
| SANs: supabase.co, *.supabase.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bqgfqedetmxrfpvmdfmc.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| supabase.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp | Verified | 200 | |
| http (plaintext) | http://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp | HTTPS enforced | 301 | https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_external_execution_request Cancel external execution request ~53
Cancel an external execution request while it is still pending manual review or open. Claimed or completed work cannot be cancelled through this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
| status_token | string | yes | – |
No output schema declared.
No examples provided.
cancel_verification_request Cancel Japan physical verification request ~51
Cancel a request only while it is pending manual review or open. Claimed or completed work cannot be cancelled through this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
| status_token | string | yes | – |
No output schema declared.
No examples provided.
check_service_fit Check Japan physical verification fit ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_requirements | array | – | Requested evidence such as photo, displayed price, stock observation, or timestamp. |
| location | string | yes | Public business or retail location in Japan. |
| objective | string | yes | The physical-world fact that must be verified. |
No output schema declared.
No examples provided.
create_verification_request Create Japan physical verification request ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | – | – |
| deadline | string | – | – |
| evidence_requirements | array | – | – |
| idempotency_key | string | yes | Stable key for this logical request. Reuse the same key when retrying create after a lost response. |
| location | string | yes | – |
| objective | string | yes | – |
No output schema declared.
No examples provided.
get_external_execution_status Get external execution status ~47
Read a manual-review external execution request and, when completed, receive the structured result and temporary evidence URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
| status_token | string | yes | – |
No output schema declared.
No examples provided.
get_verification_status Get Japan physical verification status ~45
Read the current request state and, when completed, receive structured observations and temporary signed evidence URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
| status_token | string | yes | – |
No output schema declared.
No examples provided.
prepare_verification_request Prepare Japan physical verification request ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | – | Constraints or actions the executor must not take. |
| deadline | string | – | Requested deadline in plain text or ISO 8601. |
| evidence_requirements | array | – | Evidence needed to consider the task complete. |
| location | string | yes | Public business or retail location in Japan. |
| objective | string | yes | What must be physically verified. |
No output schema declared.
No examples provided.
request_external_execution Request external execution in Japan ~210
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.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | – | – |
| deadline | string | – | – |
| evidence_requirements | array | – | – |
| idempotency_key | string | yes | Stable key for this logical request. Reuse on retry after a lost response. |
| location | string | – | Location if relevant. Omit for remote or not-yet-specified tasks. |
| max_budget_jpy | integer | – | Maximum budget the requester is willing to consider, in JPY. This is not a charge or authorization to spend. |
| objective | string | yes | The outcome the agent needs from external execution. |
No output schema declared.
No examples provided.
How do I install the Japan External Execution MCP server?
Japan External Execution is a hosted endpoint at https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bqgfqedetmxrfpvmdfmc.supabase.co
claude mcp add --transport http furoito-japan-physical-capability 'https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp'
What is the Japan External Execution MCP server?
Japan External Execution is an MCP server listed in the public MCP registry as io.github.furoito/japan-physical-capability. Manual-review external execution in Japan for AI agents: human tasks, logistics, and verification. This page covers its hosted endpoint (https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp).
Is the Japan External Execution MCP server safe to use?
Japan External Execution scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Japan External Execution MCP server expose?
Japan External Execution exposes 8 tools: check_service_fit, prepare_verification_request, create_verification_request, get_verification_status, cancel_verification_request, and 3 more. Their descriptions and schemas cost roughly 750 tokens of context every time the server is loaded.
Does the Japan External Execution MCP server require authentication?
No. We connected to Japan External Execution without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Japan External Execution MCP server still maintained?
Japan External Execution is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.