# 病み期の読み物 (remote · yami.shiryu.work)

Read-only MCP for public mental-health workflows and Evidence from 病み期の読み物.

- Trust score: 0/100 (low)
- Change this week: −68
- Registry status: active
- Liveness: dead
- Owner verified: no
- Last scored: 2026-09-28

> **Dead**: every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically.

## Components

- remote · `yami.shiryu.work`: 0/100 (this document), [markdown](https://verifymcp.io/servers/shiryu-go-mentalhealth/yami.md), [page](https://verifymcp.io/servers/shiryu-go-mentalhealth/yami)

## Channel facts

- Endpoint: `https://yami.shiryu.work/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.17.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-09-28.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC not yet verified: we couldn't validate it against a resolver.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **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 not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 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 病み期の読み物 MCP server?

病み期の読み物 is a hosted endpoint at https://yami.shiryu.work/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 shiryu-go-mentalhealth 'https://yami.shiryu.work/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "shiryu-go-mentalhealth": {
      "url": "https://yami.shiryu.work/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "shiryu-go-mentalhealth": {
      "type": "http",
      "url": "https://yami.shiryu.work/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.shiryu-go-mentalhealth]
url = "https://yami.shiryu.work/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shiryu-go-mentalhealth": {
      "type": "remote",
      "url": "https://yami.shiryu.work/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shiryu-go-mentalhealth --url 'https://yami.shiryu.work/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  shiryu-go-mentalhealth:
    url: "https://yami.shiryu.work/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "shiryu-go-mentalhealth": {
      "Transport": "http",
      "Url": "https://yami.shiryu.work/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add shiryu-go-mentalhealth -t streamable-http -u 'https://yami.shiryu.work/mcp'
```

### Other

```json
{
  "mcpServers": {
    "shiryu-go-mentalhealth": {
      "type": "http",
      "url": "https://yami.shiryu.work/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-09-28 (score 0, −14)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 14, −13)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-26 (score 27, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-25 (score 41, −13)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 54, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-09-22 (score 68, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] DNSSEC: fail → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: 0.47 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [security improvement] HTTPS: unverified → pass
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-21 (score 68, +1)

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

### 2026-09-19 (score 67, +1)

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

## MCP tools (3)

### `list_workflows` (~76 tokens)

Use this when the user wants to explore which small self-help options from 病み期の読み物 may be relevant. Returns only generalized public options, Japanese display names, and repository-defined discovery conditions. Do not use it to diagnose, score suitability, select treatment on the user's behalf, or send personal health narrative to the server.

Output parameters:

- `policy` (object)
- `workflows` (array)

### `get_workflow_bundle` (~88 tokens)

Use this after the user has chosen or explicitly asked to try a candidate returned by list_workflows. Returns an allow-listed structured execution contract together with review and Evidence references. Pass only the public workflow ID; do not send personal health narrative.

Input parameters:

- `id` (string, required): Stable public workflow ID returned by list_workflows, for example behavioral_activation. Do not put symptoms or conversation text here.

Output parameters:

- `evidence_refs` (array)
- `evidence_scope` (string|null)
- `execution` (object)
- `id` (string)
- `name` (string)
- `review_markdown` (string)
- `role` (string|null)
- `session_max_minutes` (string|number|null)
- `version` (string|number|null)

### `get_evidence` (~102 tokens)

Use this when the user or model needs to verify provenance, support scope, or limitations behind a public workflow or claim. Returns one sanitized public Evidence record by stable ID. Do not use it to decide whether a treatment is appropriate for a person, and do not send personal health information.

Input parameters:

- `id` (string, required): Stable public Evidence ID from workflow evidence_refs or /evidence/, for example NICE-DEPRESSION-NG222. Do not put personal health information here.

Output parameters:

- `access` (string)
- `doi` (string)
- `id` (string)
- `limitations` (array)
- `organization` (string)
- `pmcid` (string)
- `pmid` (string|number)
- `referenced_by` (array)
- `source_type` (string)
- `supports` (object)
- `title` (string)
- `url` (string|null)
- `workflow_referenced_by` (array)
- `year` (string|number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/shiryu-go-mentalhealth/yami#diagnostics

## Score history

- 2026-09-28: 0
- 2026-09-27: 14
- 2026-09-26: 27
- 2026-09-25: 41
- 2026-09-24: 54
- 2026-09-23: 68
- 2026-09-22: 68
- 2026-09-21: 68
- 2026-09-20: 67
- 2026-09-19: 67
- 2026-09-18: 66
- 2026-09-17: 66
- 2026-09-16: 65
- 2026-09-15: 65
- 2026-09-14: 64
- 2026-09-13: 64
- 2026-09-12: 63
- 2026-09-11: 63
- 2026-09-10: 62
- 2026-09-09: 62
- 2026-09-08: 61
- 2026-09-07: 61

## Common questions

### What is the 病み期の読み物 MCP server?

病み期の読み物 is an MCP server listed in the public MCP registry as io.github.Shiryu-go/mentalhealth. Read-only MCP for public mental-health workflows and Evidence from 病み期の読み物. This page covers its hosted endpoint (https://yami.shiryu.work/mcp).

### Is the 病み期の読み物 MCP server safe to use?

病み期の読み物 scores 0 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 病み期の読み物 MCP server expose?

病み期の読み物 exposes 3 tools: list_workflows, get_workflow_bundle, get_evidence. Their descriptions and schemas cost roughly 266 tokens of context every time the server is loaded.

### Does the 病み期の読み物 MCP server require authentication?

Its publisher declares no required credentials for 病み期の読み物. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the 病み期の読み物 MCP server still maintained?

病み期の読み物 has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 21 September 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://yami.shiryu.work/mcp
- Changelog RSS feed: https://verifymcp.io/servers/shiryu-go-mentalhealth/yami.xml
- Changelog JSON feed: https://verifymcp.io/servers/shiryu-go-mentalhealth/yami.json
- HTML version of this page: https://verifymcp.io/servers/shiryu-go-mentalhealth/yami