Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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

+3 this week 60 Trust /100

Last scanned (18 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security60
Transport & Reachability100
Schema Quality & AI Usability46
  • AI-judged instruction clarity (poor).Fail
  • Tool/resource definitions use about 646 tokens (~40/item across 16 items; 16 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage54
  • 81% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +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.

  • 10 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 54

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://japan-places.local-connect-design.trade/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=local-connect-design.trade CN=WE1,O=Google Trust Services,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA256 879658bc92f6842213bfbcfe8b0a6375
SANs: local-connect-design.trade, japan-places.local-connect-design.trade, *.japan-places.local-connect-design.trade
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of japan-places.local-connect-design.trade. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
trade. DS published 64969 8 Verified
local-connect-design.trade. DS published 2371 13 Verified
japan-places.local-connect-design.trade. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://japan-places.local-connect-design.trade/mcp Verified 200
http (plaintext) http://japan-places.local-connect-design.trade/mcp HTTPS enforced 301 https://japan-places.local-connect-design.trade/mcp
MCP tools · 16 exposed · ~646 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
jp_aliveness ~33

街の活気スコア

NameTypeReqDescription
limitstring––
min_scorestring––

No output schema declared.

No examples provided.

jp_boj_statistics ~34

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

NameTypeReqDescription
seriesstringyes–

No output schema declared.

No examples provided.

jp_catchment ~29

駅周辺の人口・施設密度

NameTypeReqDescription
limitstring––

No output schema declared.

No examples provided.

jp_chains ~34

チェーン店の出店密度

NameTypeReqDescription
limitstring––
min_countstring––

No output schema declared.

No examples provided.

jp_crime_statistics ~55

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

NameTypeReqDescription
prefecturestringyes–

No output schema declared.

No examples provided.

jp_density ~35

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

NameTypeReqDescription
categorystring––
prefecturestring––

No output schema declared.

No examples provided.

jp_energy_price ~33

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

NameTypeReqDescription
areastringyes–

No output schema declared.

No examples provided.

jp_facility_signal ~43

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

NameTypeReqDescription
prefecturestringyes–

No output schema declared.

No examples provided.

jp_gbizinfo_search ~53

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

NameTypeReqDescription
limitstring––
prefecturestring––
qstring––

No output schema declared.

No examples provided.

jp_grant_deadline_alert ~54

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

NameTypeReqDescription
industrystring––
limitstring––
prefecturestring––
statusstring––

No output schema declared.

No examples provided.

jp_jma_weather ~44

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

NameTypeReqDescription
prefecturestringyes–

No output schema declared.

No examples provided.

jp_land_price ~37

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

NameTypeReqDescription
prefecture_codestringyes–

No output schema declared.

No examples provided.

jp_municipality ~37

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

NameTypeReqDescription
prefecturestringyes–

No output schema declared.

No examples provided.

jp_quality ~27

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

NameTypeReqDescription
min_scorestring––

No output schema declared.

No examples provided.

jp_subsidy_award_rate ~41

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

NameTypeReqDescription
industrystringyes–
prefecturestringyes–

No output schema declared.

No examples provided.

jp_tourism_signal ~57

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

NameTypeReqDescription
prefecturestringyes–

No output schema declared.

No examples provided.

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.

remote · japan-places.local-connect-design.trade

# add to Claude Code
claude mcp add --transport http lexusdev7-japan-foundry 'https://japan-places.local-connect-design.trade/mcp'
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.