# Japan External Execution (remote · bqgfqedetmxrfpvmdfmc.supabase.co)

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

- Trust score: 79/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `bqgfqedetmxrfpvmdfmc.supabase.co`: 79/100 (this document), [markdown](https://verifymcp.io/servers/furoito-japan-physical-capability/functions-v1-japan-physical-capability-mcp-2.md), [page](https://verifymcp.io/servers/furoito-japan-physical-capability/functions-v1-japan-physical-capability-mcp-2)

## Channel facts

- Endpoint: `https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_verification_request).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 750 tokens (~93/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http furoito-japan-physical-capability 'https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "furoito-japan-physical-capability": {
      "url": "https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "furoito-japan-physical-capability": {
      "type": "http",
      "url": "https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.furoito-japan-physical-capability]
url = "https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "furoito-japan-physical-capability": {
      "type": "remote",
      "url": "https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add furoito-japan-physical-capability --url 'https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  furoito-japan-physical-capability:
    url: "https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "furoito-japan-physical-capability": {
      "Transport": "http",
      "Url": "https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add furoito-japan-physical-capability -t streamable-http -u 'https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp'
```

### Other

```json
{
  "mcpServers": {
    "furoito-japan-physical-capability": {
      "type": "http",
      "url": "https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-31 (score 79, +1)

- [security] Stability: 0.97 → pass

### 2026-10-29 (score 78, +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.

### 2026-10-27 (score 77, +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.

### 2026-10-24 (score 76, +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.

### 2026-10-22 (score 75, +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.

### 2026-10-20 (score 74, +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.

### 2026-10-18 (score 73, +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.

### 2026-10-16 (score 72, +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.

## MCP tools (8)

### `check_service_fit` (~102 tokens)

Check Japan physical verification 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.

Input parameters:

- `evidence_requirements` (array): Requested evidence such as photo, displayed price, stock observation, or timestamp.
- `location` (string, required): Public business or retail location in Japan.
- `objective` (string, required): The physical-world fact that must be verified.

### `prepare_verification_request` (~126 tokens)

Prepare Japan physical 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.

Input parameters:

- `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, required): Public business or retail location in Japan.
- `objective` (string, required): What must be physically verified.

### `create_verification_request` (~116 tokens)

Create Japan physical 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.

Input parameters:

- `constraints` (array)
- `deadline` (string)
- `evidence_requirements` (array)
- `idempotency_key` (string, required): Stable key for this logical request. Reuse the same key when retrying create after a lost response.
- `location` (string, required)
- `objective` (string, required)

### `get_verification_status` (~45 tokens)

Get Japan physical verification status

Read the current request state and, when completed, receive structured observations and temporary signed evidence URLs.

Input parameters:

- `request_id` (string, required)
- `status_token` (string, required)

### `cancel_verification_request` (~51 tokens)

Cancel Japan physical verification request

Cancel a request only while it is pending manual review or open. Claimed or completed work cannot be cancelled through this tool.

Input parameters:

- `request_id` (string, required)
- `status_token` (string, required)

### `request_external_execution` (~210 tokens)

Request external execution in Japan

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.

Input parameters:

- `constraints` (array)
- `deadline` (string)
- `evidence_requirements` (array)
- `idempotency_key` (string, required): 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, required): The outcome the agent needs from external execution.

### `get_external_execution_status` (~47 tokens)

Get external execution status

Read a manual-review external execution request and, when completed, receive the structured result and temporary evidence URLs.

Input parameters:

- `request_id` (string, required)
- `status_token` (string, required)

### `cancel_external_execution_request` (~53 tokens)

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.

Input parameters:

- `request_id` (string, required)
- `status_token` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/furoito-japan-physical-capability/functions-v1-japan-physical-capability-mcp-2#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 78
- 2026-10-29: 78
- 2026-10-28: 77
- 2026-10-27: 77
- 2026-10-26: 76
- 2026-10-25: 76
- 2026-10-24: 76
- 2026-10-23: 75
- 2026-10-22: 75
- 2026-10-21: 74
- 2026-10-20: 74
- 2026-10-19: 73
- 2026-10-18: 73
- 2026-10-17: 72
- 2026-10-16: 72
- 2026-10-15: 71
- 2026-10-14: 71
- 2026-10-13: 70
- 2026-10-12: 70
- 2026-10-11: 69
- 2026-10-10: 69
- 2026-10-07: 68
- 2026-10-05: 67
- 2026-10-04: 66

## Common questions

### 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.

### What did VerifyMCP test on the Japan External Execution MCP server?

VerifyMCP ran 13 checks on Japan External Execution, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp
- Repository: https://github.com/furoito/japan-physical-capability
- Website: https://furoito.github.io/japan-physical-capability/
- Changelog RSS feed: https://verifymcp.io/servers/furoito-japan-physical-capability/functions-v1-japan-physical-capability-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/furoito-japan-physical-capability/functions-v1-japan-physical-capability-mcp-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/furoito-japan-physical-capability/functions-v1-japan-physical-capability-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/furoito-japan-physical-capability/functions-v1-japan-physical-capability-mcp-2