病み期の読み物
REMOTE · YAMI.SHIRYU.WORK
Read-only MCP for public mental-health workflows and Evidence from 病み期の読み物.
Available components
Last scanned (38 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 21 Sep 2026.
Category Health and Science
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: even once the server responds again it stays dead until it is manually reinstated.
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. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 −14
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 26 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 25 Sept 26 −13
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.47 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 21 Sept 26 +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.
- 19 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://yami.shiryu.work/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of yami.shiryu.work. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| yami.shiryu.work. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://yami.shiryu.work/mcp | Unreachable | ||
| http (plaintext) | http://yami.shiryu.work/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_evidence ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Stable public Evidence ID from workflow evidence_refs or /evidence/, for example NICE-DEPRESSION-NG222. Do not put personal health information here. |
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | yes | – |
| doi | string | – | – |
| id | string | yes | – |
| limitations | array | yes | – |
| organization | string | yes | – |
| pmcid | string | – | – |
| pmid | string|number | – | – |
| referenced_by | array | yes | – |
| source_type | string | yes | – |
| supports | object | yes | – |
| title | string | yes | – |
| url | string|null | yes | – |
| workflow_referenced_by | array | yes | – |
| year | string|number | yes | – |
No examples provided.
get_workflow_bundle ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Stable public workflow ID returned by list_workflows, for example behavioral_activation. Do not put symptoms or conversation text here. |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_refs | array | yes | – |
| evidence_scope | string|null | yes | – |
| execution | object | yes | – |
| id | string | yes | – |
| name | string | yes | – |
| review_markdown | string | yes | – |
| role | string|null | yes | – |
| session_max_minutes | string|number|null | yes | – |
| version | string|number|null | yes | – |
No examples provided.
list_workflows ~76
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| policy | object | yes | – |
| workflows | array | yes | – |
No examples provided.
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.
remote · yami.shiryu.work
claude mcp add --transport http shiryu-go-mentalhealth 'https://yami.shiryu.work/mcp'
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.