Skip to content

Yamagishi Sync Lab: wages and business risks MCP server

jp.aluzza/wages-riskaluzza.jpstreamable-httpv0.1.1Scanned

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

6 tools: 5 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 5 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Yamagishi Sync Lab: wages and business risks MCP server can do

The Yamagishi Sync Lab: wages and business risks MCP server is published by aluzza.jp, a domain the MCP Registry verified. It has 6 tools. It can create or change data (5 tools: wages_ranking, france_groups, risk_categories, risk_overview and 1 more), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 9, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 5Claude Code: ask
  • about_dataこのデータの範囲と、二つの読みもののページ。No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    このデータの範囲と、二つの読みもののページ。
  • france_groupsフランス(Insee の職業の大くくり 9 区分)と、日本でそれに当たる職業をまとめた時給の倍率の比べ。No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    フランス(Insee の職業の大くくり 9 区分)と、日本でそれに当たる職業をまとめた時給の倍率の比べ。
  • risk_categories日本 3,766 社と米国 3,808 社の上場企業が「事業のリスク」の見出しに書いた心配ごとの 31 の種類。日米の順位・割合・順位の差。query で種類の名前を絞れる。sort_by は JP(日本の順位)・US(米国の順位)・gap(順位の差が大きい順)。No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    日本 3,766 社と米国 3,808 社の上場企業が「事業のリスク」の見出しに書いた心配ごとの 31 の種類。日米の順位・割合・順位の差。query で種類の名前を絞れる。sort_by は JP(日本の順位)・US(米国の順位)・gap(順位の差が大きい順)。
  • risk_overview日米の事業のリスクのまとめ:社数・1 社あたりの見出しの数・米国で AI・生成 AI・関税・Google と書いた会社の数と割合・米国の業種ごとの AI と Google の割合・小売の会社の 8 つの軸(日米)。No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    日米の事業のリスクのまとめ:社数・1 社あたりの見出しの数・米国で AI・生成 AI・関税・Google と書いた会社の数と割合・米国の業種ごとの AI と Google の割合・小売の会社の 8 つの軸(日米)。
  • wages_ranking一つの国の中で、仕事全体の平均に対する倍率(ratio)の高い順か低い順に並べる。No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    一つの国の中で、仕事全体の平均に対する倍率(ratio)の高い順か低い順に並べる。
Only reads 1Show 1 read-only tool
  • compare_wages同じ仕事の時給を、日本・米国・英国・ドイツで比べる(56 の仕事)。円に直さず、その国の仕事全体の平均の時給の何倍か(ratio)で返す。query は日本語の仕事の名前か、英語の職業名(例:薬剤師・保育士・software・nurse)。field で分野だけに絞れる。どちらも省くと仕事の一覧。No findings

    Why it is in this group

    • The name "compare_wages" says "compare": a word for reading.
    Description, as the server wrote it
    同じ仕事の時給を、日本・米国・英国・ドイツで比べる(56 の仕事)。円に直さず、その国の仕事全体の平均の時給の何倍か(ratio)で返す。query は日本語の仕事の名前か、英語の職業名(例:薬剤師・保育士・software・nurse)。field で分野だけに絞れる。どちらも省くと仕事の一覧。

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:24 UTC, unchanged since Oct 26, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.aluzza.jp/mcp/: tools/list returned 6 tools to an anonymous client, including wages_ranking (write), france_groups (write), risk_categories (write), risk_overview (write), about_data (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http wages-risk https://www.aluzza.jp/mcp/
claude mcp add --transport http wages-risk https://www.aluzza.jp/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__wages-risk__compare_wages"
    ],
    "ask": [
      "mcp__wages-risk__wages_ranking",
      "mcp__wages-risk__france_groups",
      "mcp__wages-risk__risk_categories",
      "mcp__wages-risk__risk_overview",
      "mcp__wages-risk__about_data"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wages-risk. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/jp.aluzza/wages-risk/verify?hash=7de36fc99b6e9f9f43a8f79f897ef49d39301e5ddb67651115c83114d0d56b9a" | jq -e '.changed == false'

Pinned hash 7de36fc99b6e, from Nov 9, 2026, 07:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/jp.aluzza/wages-risk/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for jp.aluzza/wages-risk
[![Anlyon Radar](https://radar.anlyon.com/badge/jp.aluzza/wages-risk.svg)](https://radar.anlyon.com/servers/jp.aluzza/wages-risk)

Source: MCP Registry. Synced Oct 25, 2026, 21:18 UTC.

Yamagishi Sync Lab: wages and business risks MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Yamagishi Sync Lab: wages and business risks MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Yamagishi Sync Lab: wages and business risks MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Yamagishi Sync Lab: wages and business risks MCP server have?

6 tools: 5 write, 1 read. wages_ranking, france_groups, risk_categories, risk_overview, about_data and compare_wages.

Does the Yamagishi Sync Lab: wages and business risks MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Yamagishi Sync Lab: wages and business risks MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Yamagishi Sync Lab: wages and business risks MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.