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.

ALGO BIZ: Japan towns, jobs and industries

REMOTE · YY-ALGO.COM

Japanese statistics: 1,889 towns, job-openings ratios, 62 industries and a town x industry sheet.

Available components

+4 this week 67 Trust /100

Last scanned (1 hour ago)

Scores higher than 53% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Data and Analytics

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 Security57
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1209 tokens (~201/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 30 Oct 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.

  • 28 Oct 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.

  • 26 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 150 → 201 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 0.1.1 → 0.2.0 functional
    • New tool “town_industry” functional
  • 25 Oct 26 62

    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 5 Nov 2026 · Probed https://yy-algo.com/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=yy-algo.com CN=YR1,O=Let's Encrypt,C=US 18 Sept 2026 17 Dec 2026 RSA 2048 SHA256-RSA 58d6a4003fba22c5ab1abe6e843d19c7fa6
SANs: www.yy-algo.com, yy-algo.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of yy-algo.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
yy-algo.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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://yy-algo.com/mcp/ Verified 200
http (plaintext) http://yy-algo.com/mcp/ HTTPS enforced 302 https://yy-algo.com/mcp/
MCP tools · 6 exposed · ~993 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
about_data ~33

このデータの出どころ(国の統計の名前)・範囲・読み方の注意。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_industry ~148

業種ごとの数(全国):主な仕事の求人倍率(2023〜2025 年度)・主な職種の賃金(令和 7 年 賃金構造基本統計調査)・都道府県ごとの倍率と賃金と最低賃金との比べ・会社の大きさごとの売上に占める人件費と利益率(財務省 法人企業統計 2025 年度)。

NameTypeReqDescription
querystringyes業種の名前や呼び名(例:運送・介護・飲食店・建設・美容室)

No output schema declared.

No examples provided.

get_town ~225

日本の市区町村(全国 1,889・政令市は区ごと)の数を返す:人口(住民基本台帳 2026 年 1 月 1 日)・5 年の増減・65 歳以上の割合・2050 年の推計人口(社人研)・商売の分類の数(経済センサス 令和 3 年の産業小分類)・その人口なら半分以上の町にあるのにこの町に無い分類・この町に 1 か所だけある分類。名前が同じ町が複数あれば候補を返す。

NameTypeReqDescription
prefecturestring–都道府県(同じ名前の町を分けるとき。例:北海道・福島)
querystringyes市区町村の名前か 5 桁の市区町村コード(例:釧路市・札幌市中央区・01206)

No output schema declared.

No examples provided.

job_openings ~171

ハローワークの有効求人倍率(2025 年度・厚生労働省「一般職業紹介状況」)。暮らしに身近な 23 の仕事 × 47 都道府県。都道府県だけ書けばその県の 23 の仕事、仕事だけ書けば 47 都道府県の高い順、両方なら一つの数と全国の中の順位。

NameTypeReqDescription
jobstring–仕事(介護・看護など・調理・接客・販売・運転・建築の技術・IT・一般事務 など。省くと一覧)
prefecturestring–都道府県(例:北海道・東京都・新潟)

No output schema declared.

No examples provided.

list_industries ~33

ALGO BIZ の業種のページ 62 の一覧(名前・副題・ページの住所)。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

town_industry ~383

町 × 業種の一枚:市区町村を一つと業種を一つ渡すと、一度に返す。①町の人口と 2050 年の推計 ②その業種に当たる産業小分類が町にあるか(無い・1 か所だけ・2 か所以上)と 50% 到達人口(その人口の町の半分にその分類がある境)・この人口なら半分以上の町にあるのに無い分類・2050 年に境を下回る分類 ③その県の求人倍率・賃金と最低賃金の比・15〜64 歳の減り ④全国のその業種の会社の、人件費を何 % 上げると経常利益がゼロになるか ⑤読み上げにそのまま使える文 reading_ja。業種は ALGO BIZ の 61 業種(運送・飲食店・介護の施設・美容室 など)か、経済センサスの産業小分類の名前か 3 桁の番号。

NameTypeReqDescription
industrystringyes業種(例:運送・飲食店・介護・美容室・建設)か産業小分類の名前・3 桁の番号(例:喫茶店・767)
prefecturestring–都道府県(同じ名前の町を分けるとき。例:北海道・福島)
townstringyes市区町村の名前か 5 桁の市区町村コード(例:釧路市・札幌市中央区・01206)

No output schema declared.

No examples provided.

Install

How do I install the ALGO BIZ: Japan towns, jobs and industries MCP server?

ALGO BIZ: Japan towns, jobs and industries is a hosted endpoint at https://yy-algo.com/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 · yy-algo.com

# add to Claude Code
claude mcp add --transport http com-yy-algo-japan-data 'https://yy-algo.com/mcp/'
Common questions

What is the ALGO BIZ: Japan towns, jobs and industries MCP server?

ALGO BIZ: Japan towns, jobs and industries is an MCP server listed in the public MCP registry as com.yy-algo/japan-data. Japanese statistics: 1,889 towns, job-openings ratios, 62 industries and a town x industry sheet. This page covers its hosted endpoint (https://yy-algo.com/mcp/).

Is the ALGO BIZ: Japan towns, jobs and industries MCP server safe to use?

ALGO BIZ: Japan towns, jobs and industries scores 67 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 ALGO BIZ: Japan towns, jobs and industries MCP server expose?

ALGO BIZ: Japan towns, jobs and industries exposes 6 tools: get_town, town_industry, job_openings, list_industries, get_industry, about_data. Their descriptions and schemas cost roughly 993 tokens of context every time the server is loaded.

Does the ALGO BIZ: Japan towns, jobs and industries MCP server require authentication?

No. We connected to ALGO BIZ: Japan towns, jobs and industries without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ALGO BIZ: Japan towns, jobs and industries MCP server still maintained?

ALGO BIZ: Japan towns, jobs and industries is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.