# io.github.physics-star-cat/databutler-jp-living-costs (remote · databutler.dev)

Japan minimum wage by prefecture, 協会けんぽ rates, pensions, benefits, holidays, tax figures, sourced.

- Trust score: 33/100 (low)
- Change this week: −39
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `databutler.dev`: 33/100 (this document), [markdown](https://verifymcp.io/servers/physics-star-cat-databutler-jp-living-costs/api-mcp-jp-living-costs.md), [page](https://verifymcp.io/servers/physics-star-cat-databutler-jp-living-costs/api-mcp-jp-living-costs)

## Channel facts

- Endpoint: `https://databutler.dev/api/mcp/jp-living-costs`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.0`

## 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**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the io.github.physics-star-cat/databutler-jp-living-costs MCP server?

io.github.physics-star-cat/databutler-jp-living-costs is a hosted endpoint at https://databutler.dev/api/mcp/jp-living-costs, 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 physics-star-cat-databutler-jp-living-costs 'https://databutler.dev/api/mcp/jp-living-costs'
```

### Cursor

```json
{
  "mcpServers": {
    "physics-star-cat-databutler-jp-living-costs": {
      "url": "https://databutler.dev/api/mcp/jp-living-costs"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "physics-star-cat-databutler-jp-living-costs": {
      "type": "http",
      "url": "https://databutler.dev/api/mcp/jp-living-costs"
    }
  }
}
```

### Codex

```toml
[mcp_servers.physics-star-cat-databutler-jp-living-costs]
url = "https://databutler.dev/api/mcp/jp-living-costs"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "physics-star-cat-databutler-jp-living-costs": {
      "type": "remote",
      "url": "https://databutler.dev/api/mcp/jp-living-costs",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add physics-star-cat-databutler-jp-living-costs --url 'https://databutler.dev/api/mcp/jp-living-costs' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  physics-star-cat-databutler-jp-living-costs:
    url: "https://databutler.dev/api/mcp/jp-living-costs"
```

### Netclaw

```json
{
  "McpServers": {
    "physics-star-cat-databutler-jp-living-costs": {
      "Transport": "http",
      "Url": "https://databutler.dev/api/mcp/jp-living-costs"
    }
  }
}
```

### Vellum

```bash
assistant mcp add physics-star-cat-databutler-jp-living-costs -t streamable-http -u 'https://databutler.dev/api/mcp/jp-living-costs'
```

### Other

```json
{
  "mcpServers": {
    "physics-star-cat-databutler-jp-living-costs": {
      "type": "http",
      "url": "https://databutler.dev/api/mcp/jp-living-costs"
    }
  }
}
```

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-01 (score 33, −40)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security regression] Stability: 0.20 → unverified
- [security regression] Authorization: partial → fail
- [security regression] HSTS header: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-31 (score 73, +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-29 (score 72, +1)

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

### 2026-10-27 (score 71, +1)

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

### 2026-10-26 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (1)

### `jp_living_costs_lookup` (~496 tokens)

Japan daily-life official figures

Japan daily-life official figures, verified against the official pages, by category: minimum-wage (地域別最低賃金 FY2026, hourly, 47 prefectures by romanised key such as tokyo or osaka plus national-weighted-average, each with its own effectiveFrom between 2026-10-01 and 2026-12-02 and the FY2025 amount as previous), health-insurance (協会けんぽ 都道府県単位保険料率 FY2026 by prefecture, employer + employee combined, with the FY2025 rate as previous; long-term-care 介護保険料率 for ages 40–64; child-rearing-levy 子ども・子育て支援金率 from April 2026), pension (kosei-nenkin-rate 厚生年金保険料率, kokumin-nenkin-premium 国民年金保険料 FY2026 and FY2027, kiso-nenkin-full-monthly 老齢基礎年金 満額), employment-insurance (雇用保険料率 FY2026, employee / employer / total per 1,000, three business types), benefits (児童手当 monthly amounts, 出産育児一時金, 高額療養費 ceilings for under-70s before August 2026, August 2026 – July 2027 and from August 2027), holidays (国民の祝日 2027), consumption-tax (10% and 8%, national and local portions), income-tax (基礎控除 table for 2024 to 2028+, 給与所得控除 tables for 2025 and 2026) and resident-tax (均等割 and 森林環境税). Each figure carries its value, unit, the Japanese term, the quoted row from the page, its source URL and effectiveFrom (and effectiveTo where the source states an end); the answer carries verifiedDate, freshness and a citation permalink. No category returns the listing; an unknown category answers covered:false with the nearest keys.

Input parameters:

- `category` (string): one of: minimum-wage, health-insurance, pension, employment-insurance, benefits, holidays, consumption-tax, income-tax, resident-tax (omit to list all)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/physics-star-cat-databutler-jp-living-costs/api-mcp-jp-living-costs#diagnostics

## Score history

- 2026-11-05: 33
- 2026-11-04: 33
- 2026-11-03: 33
- 2026-11-02: 33
- 2026-11-01: 33
- 2026-10-31: 73
- 2026-10-30: 72
- 2026-10-29: 72
- 2026-10-28: 71
- 2026-10-27: 71
- 2026-10-26: 70
- 2026-10-25: 70

## Common questions

### What is the io.github.physics-star-cat/databutler-jp-living-costs MCP server?

io.github.physics-star-cat/databutler-jp-living-costs is an MCP server listed in the public MCP registry as io.github.physics-star-cat/databutler-jp-living-costs. Japan minimum wage by prefecture, 協会けんぽ rates, pensions, benefits, holidays, tax figures, sourced. This page covers its hosted endpoint (https://databutler.dev/api/mcp/jp-living-costs).

### Is the io.github.physics-star-cat/databutler-jp-living-costs MCP server safe to use?

io.github.physics-star-cat/databutler-jp-living-costs scores 33 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 io.github.physics-star-cat/databutler-jp-living-costs MCP server expose?

io.github.physics-star-cat/databutler-jp-living-costs exposes 1 tool: jp_living_costs_lookup. Their descriptions and schemas cost roughly 496 tokens of context every time the server is loaded.

### Does the io.github.physics-star-cat/databutler-jp-living-costs MCP server require authentication?

Yes. io.github.physics-star-cat/databutler-jp-living-costs asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.physics-star-cat/databutler-jp-living-costs MCP server still maintained?

io.github.physics-star-cat/databutler-jp-living-costs 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.

### What did VerifyMCP test on the io.github.physics-star-cat/databutler-jp-living-costs MCP server?

VerifyMCP ran 5 checks on io.github.physics-star-cat/databutler-jp-living-costs, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about io.github.physics-star-cat/databutler-jp-living-costs: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. 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.

## Links

- Remote endpoint: https://databutler.dev/api/mcp/jp-living-costs
- Repository: https://github.com/physics-star-cat/databutler
- Website: https://databutler.dev/api
- Changelog RSS feed: https://verifymcp.io/servers/physics-star-cat-databutler-jp-living-costs/api-mcp-jp-living-costs.xml
- Changelog JSON feed: https://verifymcp.io/servers/physics-star-cat-databutler-jp-living-costs/api-mcp-jp-living-costs/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/physics-star-cat-databutler-jp-living-costs/api-mcp-jp-living-costs.json
- HTML version of this page: https://verifymcp.io/servers/physics-star-cat-databutler-jp-living-costs/api-mcp-jp-living-costs