io.github.ogasurfproject-jpg/jhnrd
REMOTE · JHNRD-MCP.OGA-SURF-PROJECT.WORKERS.DEV · SCANNED SEP 20
Japan home-visit nursing reimbursement rules, each with its source and that source's standing.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1158 tokens (~105/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.ogasurfproject-jpg/jhnrd MCP server?
io.github.ogasurfproject-jpg/jhnrd is a hosted endpoint at https://jhnrd-mcp.oga-surf-project.workers.dev/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 · jhnrd-mcp.oga-surf-project.workers.dev
claude mcp add --transport http ogasurfproject-jpg-jhnrd 'https://jhnrd-mcp.oga-surf-project.workers.dev/mcp'
{
"mcpServers": {
"ogasurfproject-jpg-jhnrd": {
"url": "https://jhnrd-mcp.oga-surf-project.workers.dev/mcp"
}
}
} {
"servers": {
"ogasurfproject-jpg-jhnrd": {
"type": "http",
"url": "https://jhnrd-mcp.oga-surf-project.workers.dev/mcp"
}
}
} [mcp_servers.ogasurfproject-jpg-jhnrd] url = "https://jhnrd-mcp.oga-surf-project.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ogasurfproject-jpg-jhnrd": {
"type": "remote",
"url": "https://jhnrd-mcp.oga-surf-project.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add ogasurfproject-jpg-jhnrd --url 'https://jhnrd-mcp.oga-surf-project.workers.dev/mcp' --transport streamable-http
mcp_servers:
ogasurfproject-jpg-jhnrd:
url: "https://jhnrd-mcp.oga-surf-project.workers.dev/mcp" {
"McpServers": {
"ogasurfproject-jpg-jhnrd": {
"Transport": "http",
"Url": "https://jhnrd-mcp.oga-surf-project.workers.dev/mcp"
}
}
} assistant mcp add ogasurfproject-jpg-jhnrd -t streamable-http -u 'https://jhnrd-mcp.oga-surf-project.workers.dev/mcp'
{
"mcpServers": {
"ogasurfproject-jpg-jhnrd": {
"type": "http",
"url": "https://jhnrd-mcp.oga-surf-project.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 20 Sept 2026 · Probed https://jhnrd-mcp.oga-surf-project.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=oga-surf-project.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5140e60afc17e828e8296332eb36047a5a7 |
| SANs: *.oga-surf-project.workers.dev, oga-surf-project.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jhnrd-mcp.oga-surf-project.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jhnrd-mcp.oga-surf-project.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://jhnrd-mcp.oga-surf-project.workers.dev/mcp | Inconclusive | 405 |
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 →
jhnrd_conflicts ~67
出典どうし、あるいは同じ出典の読み取りどうしが食い違った記録。解決済みも残す。どちらかを選んで黙る、ということをしていない証拠でもある。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jhnrd_disclosure ~62
誰がこれを作り、誰に養われているか。利益相反の開示。出典の素性を名乗ることを規律にしている以上、この口自身の素性も名乗る。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jhnrd_gaps ~83
埋まっていないもの(known_gaps)、取りに行って取れなかった記録(attempts)、途中まで分かったこと(findings)。何が無いかを、無いと言えるようにするための口。
| Name | Type | Req | Description |
|---|---|---|---|
| include_resolved | boolean | – | 解決済みの gap も含める |
No output schema declared.
No examples provided.
jhnrd_get_item ~76
項目1件の全部。要件・効果・期限に加えて、参照している出典を素性(tier)と現行かどうかつきで解決して返す。
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 項目の id。例: genzan-bcp |
No output schema declared.
No examples provided.
jhnrd_get_source ~64
出典1件の素性。tier(statute/agency/secondary)と、現行版かどうか(current)を必ず返す。
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 出典の id。例: mhlw-001195261 |
No output schema declared.
No examples provided.
jhnrd_how_to_cite ~64
引用の仕方。版(seed 番号)を添えること。訂正しても元の記述を消さない方針のため、版が分からないと後から突き合わせられない。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jhnrd_list_items ~169
収録している項目の一覧(要約)。insurance(介護/医療/介護・医療)と kind(加算/減算/単位数/療養費/期限・交付ルール/振り分けルール)で絞れる。詳細は jhnrd_get_item。
| Name | Type | Req | Description |
|---|---|---|---|
| insurance | string | – | 介護 / 医療 / 介護・医療 のいずれか(部分一致) |
| kind | string | – | 加算 / 減算 / 単位数 / 療養費 / 期限・交付ルール / 振り分けルール |
| only_unconfirmed | boolean | – | true なら、確認できていないものだけ |
No output schema declared.
No examples provided.
jhnrd_list_sources ~100
出典の一覧。素性ごと、現行かどうかごとに数えたものも返す。statute が何件あるかだけを言うと実態より良く見えるので、現行版の数を分けて出す。
| Name | Type | Req | Description |
|---|---|---|---|
| only_current | boolean | – | true なら現行版の出典だけ |
| tier | string | – | statute / agency / secondary |
No output schema declared.
No examples provided.
jhnrd_search ~97
項目名・要件の本文・効果の文言を横断して探す。見つからなければ、見つからないと返す(推測しない)。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | 最大件数(既定 20) |
| q | string | yes | 探したい語。例: 特別管理加算 / ターミナル / 指示書 |
No output schema declared.
No examples provided.
jhnrd_status ~81
このデータベースのいまの状態。版・項目数・出典の素性の内訳・未確認の要件の数・未解決の食い違いの数。項目数は訪問看護の算定要件を網羅した数ではない。まずここを見ること。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jhnrd_unconfirmed ~64
原文で確認できていない要件の一覧と、なぜ確認できていないかの理由。空欄にせず残してあるもの。このデータベースの弱いところを、先に見るための口。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.ogasurfproject-jpg/jhnrd MCP server?
io.github.ogasurfproject-jpg/jhnrd is an MCP server listed in the public MCP registry as io.github.ogasurfproject-jpg/jhnrd. Japan home-visit nursing reimbursement rules, each with its source and that source's standing. This page covers its hosted endpoint (https://jhnrd-mcp.oga-surf-project.workers.dev/mcp).
Is the io.github.ogasurfproject-jpg/jhnrd MCP server safe to use?
io.github.ogasurfproject-jpg/jhnrd scores 72 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.ogasurfproject-jpg/jhnrd MCP server expose?
io.github.ogasurfproject-jpg/jhnrd exposes 11 tools: jhnrd_status, jhnrd_list_items, jhnrd_get_item, jhnrd_search, jhnrd_unconfirmed, and 6 more. Their descriptions and schemas cost roughly 927 tokens of context every time the server is loaded.
Does the io.github.ogasurfproject-jpg/jhnrd MCP server require authentication?
No. We connected to io.github.ogasurfproject-jpg/jhnrd without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.ogasurfproject-jpg/jhnrd MCP server still maintained?
io.github.ogasurfproject-jpg/jhnrd is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.