# Japan Places — Japan Data Foundry (remote · japan-places.local-connect-design.trade)

Japan POI tools for AI agents: 2.94M facilities, station catchments, chains, grants and signals

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

## Components

- remote · `japan-places.local-connect-design.trade`: 60/100 (this document), [markdown](https://verifymcp.io/servers/lexusdev7-japan-foundry/japan-places.md), [page](https://verifymcp.io/servers/lexusdev7-japan-foundry/japan-places)

## Channel facts

- Endpoint: `https://japan-places.local-connect-design.trade/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

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

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 46/100
  - AI-judged instruction clarity (poor).
  - Tool/resource definitions use about 646 tokens (~40/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 54/100
  - 81% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the Japan Places — Japan Data Foundry MCP server?

Japan Places — Japan Data Foundry is a hosted endpoint at https://japan-places.local-connect-design.trade/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 lexusdev7-japan-foundry 'https://japan-places.local-connect-design.trade/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "lexusdev7-japan-foundry": {
      "url": "https://japan-places.local-connect-design.trade/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lexusdev7-japan-foundry": {
      "type": "http",
      "url": "https://japan-places.local-connect-design.trade/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.lexusdev7-japan-foundry]
url = "https://japan-places.local-connect-design.trade/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lexusdev7-japan-foundry": {
      "type": "remote",
      "url": "https://japan-places.local-connect-design.trade/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lexusdev7-japan-foundry --url 'https://japan-places.local-connect-design.trade/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lexusdev7-japan-foundry:
    url: "https://japan-places.local-connect-design.trade/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "lexusdev7-japan-foundry": {
      "Transport": "http",
      "Url": "https://japan-places.local-connect-design.trade/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add lexusdev7-japan-foundry -t streamable-http -u 'https://japan-places.local-connect-design.trade/mcp'
```

### Other

```json
{
  "mcpServers": {
    "lexusdev7-japan-foundry": {
      "type": "http",
      "url": "https://japan-places.local-connect-design.trade/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-11-21 (score 60, +1)

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

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

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

### 2026-11-17 (score 58, +1)

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

### 2026-11-14 (score 57, +1)

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

### 2026-11-12 (score 56, +1)

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

### 2026-11-10 (score 55, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 54)

First indexed and scored.

## MCP tools (16)

### `jp_municipality` (~37 tokens)

市区町村別センサス（人口・法人数・POI件数）

Input parameters:

- `prefecture` (string, required)

### `jp_quality` (~27 tokens)

ジオコーディング品質の分布

Input parameters:

- `min_score` (string)

### `jp_catchment` (~29 tokens)

駅周辺の人口・施設密度

Input parameters:

- `limit` (string)

### `jp_chains` (~34 tokens)

チェーン店の出店密度

Input parameters:

- `limit` (string)
- `min_count` (string)

### `jp_aliveness` (~33 tokens)

街の活気スコア

Input parameters:

- `limit` (string)
- `min_score` (string)

### `jp_density` (~35 tokens)

都道府県×カテゴリのPOI密度

Input parameters:

- `category` (string)
- `prefecture` (string)

### `jp_energy_price` (~33 tokens)

JEPX電力需給×気象からの価格シグナル

Input parameters:

- `area` (string, required)

### `jp_land_price` (~37 tokens)

都道府県別平均地価（国土数値情報 地価公示）

Input parameters:

- `prefecture_code` (string, required)

### `jp_subsidy_award_rate` (~41 tokens)

補助金採択率推定インデックス

Input parameters:

- `industry` (string, required)
- `prefecture` (string, required)

### `jp_grant_deadline_alert` (~54 tokens)

補助金締切・要件アラート

Input parameters:

- `industry` (string)
- `limit` (string)
- `prefecture` (string)
- `status` (string)

### `jp_gbizinfo_search` (~53 tokens)

gBizINFO法人登録データスナップショット（26,249法人）の検索

Input parameters:

- `limit` (string)
- `prefecture` (string)
- `q` (string)

### `jp_jma_weather` (~44 tokens)

気象庁・気温・降水量・日照時間の都道府県別シグナル

Input parameters:

- `prefecture` (string, required)

### `jp_boj_statistics` (~34 tokens)

日銀・金融統計・物価指数の時系列シグナル

Input parameters:

- `series` (string, required)

### `jp_tourism_signal` (~57 tokens)

総務省統計局 都道府県データ基礎データによる都道府県別の外国人延べ宿泊者数シグナル

Input parameters:

- `prefecture` (string, required)

### `jp_crime_statistics` (~55 tokens)

総務省統計局 都道府県データ基礎データによる都道府県別の刑法犯認知件数シグナル

Input parameters:

- `prefecture` (string, required)

### `jp_facility_signal` (~43 tokens)

OpenPOI公共施設カテゴリPOI集計による都道府県別の公共施設数シグナル

Input parameters:

- `prefecture` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lexusdev7-japan-foundry/japan-places#diagnostics

## Score history

- 2026-11-21: 60
- 2026-11-20: 59
- 2026-11-19: 59
- 2026-11-18: 58
- 2026-11-17: 58
- 2026-11-16: 57
- 2026-11-15: 57
- 2026-11-14: 57
- 2026-11-13: 56
- 2026-11-12: 56
- 2026-11-11: 55
- 2026-11-10: 55
- 2026-11-09: 54

## Common questions

### What is the Japan Places — Japan Data Foundry MCP server?

Japan Places — Japan Data Foundry is an MCP server listed in the public MCP registry as io.github.lexusdev7/japan-foundry. Japan POI tools for AI agents: 2.94M facilities, station catchments, chains, grants and signals. This page covers its hosted endpoint (https://japan-places.local-connect-design.trade/mcp).

### Is the Japan Places — Japan Data Foundry MCP server safe to use?

Japan Places — Japan Data Foundry scores 60 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 Places — Japan Data Foundry MCP server expose?

Japan Places — Japan Data Foundry exposes 16 tools: jp_municipality, jp_quality, jp_catchment, jp_chains, jp_aliveness, and 11 more. Their descriptions and schemas cost roughly 646 tokens of context every time the server is loaded.

### Does the Japan Places — Japan Data Foundry MCP server require authentication?

No. We connected to Japan Places — Japan Data Foundry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Japan Places — Japan Data Foundry MCP server still maintained?

Japan Places — Japan Data Foundry 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 did VerifyMCP test on the Japan Places — Japan Data Foundry MCP server?

VerifyMCP ran 12 checks on Japan Places — Japan Data Foundry, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Japan Places — Japan Data Foundry: Authorization. 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://japan-places.local-connect-design.trade/mcp
- Website: https://japan-places.local-connect-design.trade/
- Changelog RSS feed: https://verifymcp.io/servers/lexusdev7-japan-foundry/japan-places.xml
- Changelog JSON feed: https://verifymcp.io/servers/lexusdev7-japan-foundry/japan-places/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lexusdev7-japan-foundry/japan-places.json
- HTML version of this page: https://verifymcp.io/servers/lexusdev7-japan-foundry/japan-places
