Skip to content

Japan External Execution MCP server

io.github.furoito/japan-physical-capabilityfuroitostreamable-httpv0.4.3Scanned

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

8 tools: 2 can delete or cancel things, 4 change things and 2 only read.

Tools: 2 delete, 0 irreversible, 4 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

6 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Japan External Execution MCP server can do

The Japan External Execution MCP server is published by the GitHub account furoito. It has 8 tools. It can delete or cancel things (2 tools: cancel_verification_request and cancel_external_execution_request) and create or change data (4 tools: check_service_fit, prepare_verification_request, create_verification_request and request_external_execution). 2 tools only read.

1 tool brings in text other people can write (get_external_execution_status).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Last scanned Nov 5, 2026, version 0.4.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Deletes or cancels 2Claude Code: deny
  • cancel_external_execution_requestCancel an external execution request while it is still pending manual review or open.No findings

    Why it is in this group

    • The name "cancel_external_execution_request" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Cancel an external execution request while it is still pending manual review or open. Claimed or completed work cannot be cancelled through this tool.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • cancel_verification_requestCancel a request only while it is pending manual review or open.No findings

    Why it is in this group

    • The name "cancel_verification_request" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Cancel a request only while it is pending manual review or open. Claimed or completed work cannot be cancelled through this tool.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 4Claude Code: ask
  • check_service_fitUse 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 researc…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • create_verification_requestCreate a retry-safe manual-review physical verification request in Japan.No findings

    Why it is in this group

    • The name "create_verification_request" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • prepare_verification_requestPrepare a Japan on-site verification request for a human-executed store check.1 finding

    Why it is in this group

    • The name "prepare_verification_request" says "request": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "prepare_verification_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "prepare_verification_request" says "request": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • request_external_executionUse when an AI cannot complete a task itself and needs a human or provider in Japan, or for a Japan-related real-world task.No findings

    Why it is in this group

    • The name "request_external_execution" says "request": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • get_external_execution_statusRead a manual-review external execution request and, when completed, receive the structured result and temporary evidence URLs.Reads text others writeNo findings

    Why it is in this group

    • The name "get_external_execution_status" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "read" and "review": it reads comments, which other people can write.
    Description, as the server wrote it
    Read a manual-review external execution request and, when completed, receive the structured result and temporary evidence URLs.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_verification_statusRead the current request state and, when completed, receive structured observations and temporary signed evidence URLs.No findings

    Why it is in this group

    • The name "get_verification_status" says "get": a word for reading.
    Description, as the server wrote it
    Read the current request state and, when completed, receive structured observations and temporary signed evidence URLs.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:05 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
402
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 402.

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 200 to 402
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "prepare_verification_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "prepare_verification_request" says "request": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 402; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 6 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 402
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 0.4.3. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__japan-physical-capability__get_verification_status",
      "mcp__japan-physical-capability__get_external_execution_status"
    ],
    "ask": [
      "mcp__japan-physical-capability__check_service_fit",
      "mcp__japan-physical-capability__prepare_verification_request",
      "mcp__japan-physical-capability__create_verification_request",
      "mcp__japan-physical-capability__request_external_execution"
    ],
    "deny": [
      "mcp__japan-physical-capability__cancel_verification_request",
      "mcp__japan-physical-capability__cancel_external_execution_request"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as japan-physical-capability. Review it before you use it.

Capability tags behind 1 rule
  • mcp__japan-physical-capability__get_external_execution_status untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.furoito/japan-physical-capability/verify?hash=4f8b4c3e25031b1c54b4d79d156c37440e34f12684a0251569085ed4390c1758" | jq -e '.changed == false'

Pinned hash 4f8b4c3e2503, from Nov 5, 2026, 20:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.furoito/japan-physical-capability/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.furoito/japan-physical-capability
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.furoito/japan-physical-capability.svg)](https://radar.anlyon.com/servers/io.github.furoito/japan-physical-capability)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:34 UTC.

Japan External Execution MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Japan External Execution MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Japan External Execution MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: cancel_verification_request and cancel_external_execution_request.

Can the Japan External Execution MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Japan External Execution MCP server have?

8 tools: 2 destructive, 4 write, 2 read. cancel_verification_request, cancel_external_execution_request, check_service_fit, prepare_verification_request, create_verification_request, request_external_execution, get_verification_status and get_external_execution_status.

Does the Japan External Execution MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Japan External Execution MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Japan External Execution MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 5, 2026.