Home / MCP registry index / io.github.furoito/japan-physical-capability
Japan External Execution
io.github.furoito/japan-physical-capability in the official MCP registry.
Endpoint https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp. Source: github.com/furoito/japan-physical-capability.
The registry describes it as: Manual-review external execution in Japan for AI agents: human tasks, logistics, and verification.
We read its 8 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
check_service_fit prepare_verification_request create_verification_request get_verification_status cancel_verification_request request_external_execution get_external_execution_status cancel_external_execution_request
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-furoito-japan-physical-capability)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.