# Yamagishi Sync Lab: wages and business risks (remote · www.aluzza.jp)

Same-job hourly wages in Japan, US, UK, Germany, France; ranks of 31 business risks, Japan vs US.

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

## Components

- remote · `www.aluzza.jp`: 65/100 (this document), [markdown](https://verifymcp.io/servers/jp-aluzza-wages-risk/www.md), [page](https://verifymcp.io/servers/jp-aluzza-wages-risk/www)

## Channel facts

- Endpoint: `https://www.aluzza.jp/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

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

- **Endpoint Security**: 51/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 6 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 817 tokens (~136/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 Yamagishi Sync Lab: wages and business risks MCP server?

Yamagishi Sync Lab: wages and business risks is a hosted endpoint at https://www.aluzza.jp/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 jp-aluzza-wages-risk 'https://www.aluzza.jp/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "jp-aluzza-wages-risk": {
      "url": "https://www.aluzza.jp/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jp-aluzza-wages-risk": {
      "type": "http",
      "url": "https://www.aluzza.jp/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jp-aluzza-wages-risk]
url = "https://www.aluzza.jp/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jp-aluzza-wages-risk": {
      "type": "remote",
      "url": "https://www.aluzza.jp/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jp-aluzza-wages-risk --url 'https://www.aluzza.jp/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jp-aluzza-wages-risk:
    url: "https://www.aluzza.jp/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "jp-aluzza-wages-risk": {
      "Transport": "http",
      "Url": "https://www.aluzza.jp/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jp-aluzza-wages-risk -t streamable-http -u 'https://www.aluzza.jp/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "jp-aluzza-wages-risk": {
      "type": "http",
      "url": "https://www.aluzza.jp/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-04 (score 65, +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-02 (score 64, +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-10-31 (score 63, +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-10-28 (score 62, +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-10-26 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-25 (score 60)

First indexed and scored.

## MCP tools (6)

### `compare_wages` (~193 tokens)

同じ仕事の時給を、日本・米国・英国・ドイツで比べる（56 の仕事）。円に直さず、その国の仕事全体の平均の時給の何倍か（ratio）で返す。query は日本語の仕事の名前か、英語の職業名（例：薬剤師・保育士・software・nurse）。field で分野だけに絞れる。どちらも省くと仕事の一覧。

Input parameters:

- `field` (string): 分野（医療／介護・保育・教育／技術・専門／事務・販売／サービス／運転・運輸／建設・ものづくり）。一部だけでもよい
- `query` (string): 仕事の名前（日本語）か職業名（英語）の一部

### `wages_ranking` (~106 tokens)

一つの国の中で、仕事全体の平均に対する倍率（ratio）の高い順か低い順に並べる。

Input parameters:

- `country` (string, required): 国（JP 日本・US 米国・UK 英国・DE ドイツ）
- `limit` (integer): 何件まで（省くと 10）
- `order` (string): 高い順（high・省くとこちら）か低い順（low）

### `france_groups` (~49 tokens)

フランス（Insee の職業の大くくり 9 区分）と、日本でそれに当たる職業をまとめた時給の倍率の比べ。

### `risk_categories` (~149 tokens)

日本 3,766 社と米国 3,808 社の上場企業が「事業のリスク」の見出しに書いた心配ごとの 31 の種類。日米の順位・割合・順位の差。query で種類の名前を絞れる。sort_by は JP（日本の順位）・US（米国の順位）・gap（順位の差が大きい順）。

Input parameters:

- `query` (string): 種類の名前の一部（例：人手・災害・株主・AI・金利）
- `sort_by` (string): 並べ方（省くと JP）

### `risk_overview` (~83 tokens)

日米の事業のリスクのまとめ：社数・1 社あたりの見出しの数・米国で AI・生成 AI・関税・Google と書いた会社の数と割合・米国の業種ごとの AI と Google の割合・小売の会社の 8 つの軸（日米）。

### `about_data` (~25 tokens)

このデータの範囲と、二つの読みもののページ。

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/jp-aluzza-wages-risk/www#diagnostics

## Score history

- 2026-11-05: 65
- 2026-11-04: 65
- 2026-11-03: 64
- 2026-11-02: 64
- 2026-11-01: 63
- 2026-10-31: 63
- 2026-10-30: 62
- 2026-10-29: 62
- 2026-10-28: 62
- 2026-10-27: 61
- 2026-10-26: 61
- 2026-10-25: 60

## Common questions

### What is the Yamagishi Sync Lab: wages and business risks MCP server?

Yamagishi Sync Lab: wages and business risks is an MCP server listed in the public MCP registry as jp.aluzza/wages-risk. Same-job hourly wages in Japan, US, UK, Germany, France; ranks of 31 business risks, Japan vs US. This page covers its hosted endpoint (https://www.aluzza.jp/mcp/).

### Is the Yamagishi Sync Lab: wages and business risks MCP server safe to use?

Yamagishi Sync Lab: wages and business risks scores 65 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 Yamagishi Sync Lab: wages and business risks MCP server expose?

Yamagishi Sync Lab: wages and business risks exposes 6 tools: compare_wages, wages_ranking, france_groups, risk_categories, risk_overview, about_data. Their descriptions and schemas cost roughly 605 tokens of context every time the server is loaded.

### Does the Yamagishi Sync Lab: wages and business risks MCP server require authentication?

No. We connected to Yamagishi Sync Lab: wages and business risks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Yamagishi Sync Lab: wages and business risks MCP server still maintained?

Yamagishi Sync Lab: wages and business risks 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.

## Links

- Remote endpoint: https://www.aluzza.jp/mcp/
- Website: https://www.aluzza.jp/mcp-info/
- Changelog RSS feed: https://verifymcp.io/servers/jp-aluzza-wages-risk/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/jp-aluzza-wages-risk/www.json
- HTML version of this page: https://verifymcp.io/servers/jp-aluzza-wages-risk/www