Home / MCP registry index / io.github.kishida-devil/jp-payroll-mcp

日本の給与・社会保険・労働法

io.github.kishida-devil/jp-payroll-mcp in the official MCP registry. Endpoint https://japan-payroll-api.tsumugi.workers.dev/mcp. Source: github.com/kishida-devil/jp-payroll-mcp.

The registry describes it as: Japan payroll & social insurance. 日本の給与計算・社会保険。47都道府県の料率、源泉所得税、割増賃金、有給、標準報酬月額の改定、最低賃金。根拠の条文つき。

We read its 30 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http jp-payroll-mcp https://japan-payroll-api.tsumugi.workers.dev/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "jp-payroll-mcp": {
      "url": "https://japan-payroll-api.tsumugi.workers.dev/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"jp-payroll-mcp","type":"http","url":"https://japan-payroll-api.tsumugi.workers.dev/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

calculate_payslip list_workers_compensation_rates calculate_bonus calculate_withholding_tax judge_monthly_revision decide_regular_remuneration judge_leave_end_revision calculate_payroll_batch decide_regular_remuneration_batch judge_annual_average lookup_standard_remuneration national_insurance calculate_annual_cost judge_annual_leave judge_worker_type check_insurance_eligibility check_leave_exemption get_age_milestones calculate_year_end_adjustment estimate_resident_tax get_insurance_rates get_minimum_wage business_days validate_invoice_numbers_batch validate_corporate_number consumption_tax get_statute_text calculate_overtime_pay commuting_allowance_exemption check_data_freshness

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-kishida-devil-jp-payroll-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-kishida-devil-jp-payroll-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.