Japan External Execution

Name: Japan External Execution
Author: furoito

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

by furoito(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from the official MCP registry - entry io.github.furoito/japan-physical-capability v0.4.1. Ratings and installs below are from this marketplace.

Japan External Execution

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

Remote endpoints

streamable-http https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp

Source: https://github.com/furoito/japan-physical-capability

Registry entry: io.github.furoito/japan-physical-capability

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# after Install: the listing is in your workspace's routing pool - nothing else to configure
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
# or pin it on the OpenAI-compatible endpoint: {"model": "mcp-io-github-furoito-japan-physical-capability", ...}

Installed into a catalogue, chosen by a router

Install Japan External Execution and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Photo: RDNE Stock project

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

mcp-io-github-furoito-japan-physical-capability.ocm.jsonjson

{
  "ocm": "1",
  "id": "mcp-io-github-furoito-japan-physical-capability",
  "kind": "tool",
  "name": "Japan External Execution",
  "description": "Manual-review external execution in Japan for AI agents: human tasks, logistics, and verification.",
  "publisher": "furoito",
  "version": "0.4.1",
  "capabilities": {
    "domains": [
      "math"
    ],
    "tags": [
      "mcp",
      "mcp-server",
      "mcp-registry"
    ],
    "languages": [
      "en"
    ],
    "supports_tools": true
  },
  "quality_prior": 0.6,
  "examples": [
    "Manual-review external execution in Japan for AI agents: human tasks, logistics, and verification."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "mcp-registry",
      "repository": "https://github.com/furoito/japan-physical-capability",
      "path": "server.json",
      "ref": "0.4.1",
      "url": "https://github.com/furoito/japan-physical-capability",
      "key": "io.github.furoito/japan-physical-capability",
      "registry": "https://registry.modelcontextprotocol.io"
    }
  },
  "endpoints": [
    {
      "protocol": "mcp",
      "url": "https://bqgfqedetmxrfpvmdfmc.supabase.co/functions/v1/japan-physical-capability-mcp"
    }
  ]
}

Fetch it by URL: GET /api/v1/registry/mcp-io-github-furoito-japan-physical-capability/manifest?version=0.4.1

About

Japan External Execution

Remote endpoints

Use it

Install Japan External Execution and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews