# Japan Places (npm · @pipeworx/mcp-japan-places)

Japan Places — stores, stations and other facilities near a point or a named Japanese station, for…

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `gateway.pipeworx.io`: 78/100, [markdown](https://verifymcp.io/servers/pipeworx-io-japan-places/japan-places-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-japan-places/japan-places-mcp)
- npm · `@pipeworx/mcp-japan-places`: 71/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-japan-places/pipeworx-mcp-japan-places.md), [page](https://verifymcp.io/servers/pipeworx-io-japan-places/pipeworx-mcp-japan-places)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-japan-places`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 595 tokens (~297/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Japan Places MCP server?

Japan Places runs locally as an npm package, launched with npx -y @pipeworx/mcp-japan-places. 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 pipeworx-io-japan-places -- npx -y @pipeworx/mcp-japan-places
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-japan-places": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-japan-places"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-japan-places": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-japan-places"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-japan-places -- npx -y @pipeworx/mcp-japan-places
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-japan-places": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-japan-places"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-japan-places --command npx --arg -y --arg @pipeworx/mcp-japan-places
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-japan-places:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-japan-places"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-japan-places": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-japan-places"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-japan-places -t stdio -c npx -a -y @pipeworx/mcp-japan-places
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-japan-places": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-japan-places"
      ]
    }
  }
}
```

## 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-11-21 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 69, +1)

- [functional improvement] Stability: unverified → 0.10

### 2026-11-16 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-15 (score 53)

First indexed and scored.

## MCP tools (2)

### `places_near_station` (~306 tokens)

Find facilities in Japan near a named train or subway station — convenience stores (konbini: 7-Eleven, Lawson, FamilyMart), restaurants, pharmacies, hospitals, ATMs, banks, hotels, supermarkets near a Shinkansen, JR, subway or private-railway station. Answers "convenience stores within 500m of Shibuya station", "pharmacies near Shinjuku station", "hospitals near Namba station". Geocodes the station name within Japan, then searches OpenStreetMap around it. Returns each place's name, category, distance in metres and coordinates.

Input parameters:

- `category` (string, required): What to find: "convenience_store", "station" (another station nearby), "hospital", "pharmacy", "restaurant", "cafe", "supermarket", "bank", "atm", "hotel", "post_office", "toilet", "parking", "temple…
- `limit` (number): Max results (1-200, default 20).
- `radius_m` (number): Search radius in metres (1-5000, default 500).
- `station` (string, required): Station or place name, e.g. "Shibuya Station", "Shinjuku Station, Tokyo", "Namba Station, Osaka". Adding the city helps disambiguate common names.

### `places_near_point` (~234 tokens)

Find facilities in Japan near a latitude/longitude — convenience stores, stations, hospitals, pharmacies, restaurants, ATMs and other POIs. Use when you already have coordinates rather than a station name. Answers "what's within 300m of 35.6595,139.7005 in Tokyo" style questions. Returns each place's name, category, distance in metres and coordinates, sourced from OpenStreetMap.

Input parameters:

- `category` (string, required): What to find: "convenience_store", "station", "hospital", "pharmacy", "restaurant", "cafe", "supermarket", "bank", "atm", "hotel", "post_office", "toilet", "parking", "temple", "shrine", "park" — or…
- `latitude` (number, required): Center latitude.
- `limit` (number): Max results (1-200, default 20).
- `longitude` (number, required): Center longitude.
- `radius_m` (number): Search radius in metres (1-5000, default 500).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-japan-places/pipeworx-mcp-japan-places#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 70
- 2026-11-19: 70
- 2026-11-18: 69
- 2026-11-17: 68
- 2026-11-16: 68
- 2026-11-15: 53

## Common questions

### What is the Japan Places MCP server?

Japan Places is an MCP server listed in the public MCP registry as io.github.pipeworx-io/japan-places. Japan Places, stores, stations and other facilities near a point or a named Japanese station, for… This page covers its npm package (@pipeworx/mcp-japan-places).

### Is the Japan Places MCP server safe to use?

Japan Places scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Places MCP server expose?

Japan Places exposes 2 tools: places_near_station, places_near_point. Their descriptions and schemas cost roughly 540 tokens of context every time the server is loaded.

### Is the Japan Places MCP server still maintained?

Japan Places is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Japan Places MCP server under?

Japan Places declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Japan Places MCP server?

VerifyMCP ran 16 checks on Japan Places, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-japan-places
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-japan-places
- Repository: https://github.com/pipeworx-io/mcp-japan-places
- Website: https://pipeworx.io/packs/japan-places
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-japan-places/pipeworx-mcp-japan-places.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-japan-places/pipeworx-mcp-japan-places/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-japan-places/pipeworx-mcp-japan-places.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-japan-places/pipeworx-mcp-japan-places
