jhnrd
https://jhnrd-mcp.oga-surf-project.workers.dev
Registry code: 3ea7ad9ec1cfb6d0
訪問看護の算定要件データベース(JHNRD)。要件と、その要件がどの資料に基づくかを一つずつ持つ。
使うときの約束:
- endpoint
- https://jhnrd-mcp.oga-surf-project.workers.dev/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is jhnrd live?
- Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
- Is jhnrd free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does jhnrd have?
- 11 tools: jhnrd_how_to_cite, jhnrd_disclosure, jhnrd_unconfirmed, jhnrd_conflicts, jhnrd_gaps, jhnrd_list_items, jhnrd_status, jhnrd_list_sources, ….
- Is jhnrd safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.6%· all time 99.6%
last good check
of 11 tools
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- used for
- look up japanese home nursing billing requirements
- get source tier for a requirement
- list unconfirmed requirements
- search billing rules
- takes → gives
- text → data, text
- tools
- 11 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
jhnrd_list_items reads open 14h ago
収録している項目の一覧(要約)。insurance(介護/医療/介護・医療)と kind(加算/減算/単位数/療養費/期限・交付ルール/振り分けルール)で絞れる。詳細は jhnrd_get_item。
{ "type": "object", "properties": { "kind": { "type": "string", "description": "加算 / 減算 / 単位数 / 療養費 / 期限・交付ルール / 振り分けルール" }, "insurance": { "type": "string", "description": "介護 / 医療 / 介護・医療 のいずれか(部分一致)" }, "only_unconfirmed": { "type": "boolean", "description": "true なら、確認できていないものだけ" } }, "additionalProperties": false }arguments 18 linesjhnrd_status reads open 14h ago
このデータベースのいまの状態。版・項目数・出典の素性の内訳・未確認の要件の数・未解決の食い違いの数。項目数は訪問看護の算定要件を網羅した数ではない。まずここを見ること。
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesjhnrd_list_sources reads open 14h ago
出典の一覧。素性ごと、現行かどうかごとに数えたものも返す。statute が何件あるかだけを言うと実態より良く見えるので、現行版の数を分けて出す。
{ "type": "object", "properties": { "tier": { "type": "string", "description": "statute / agency / secondary" }, "only_current": { "type": "boolean", "description": "true なら現行版の出典だけ" } }, "additionalProperties": false }arguments 14 linesjhnrd_get_source reads open 5h ago
出典1件の素性。tier(statute/agency/secondary)と、現行版かどうか(current)を必ず返す。
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "出典の id。例: mhlw-001195261" } }, "additionalProperties": false }arguments 13 linesjhnrd_search reads open 5h ago
項目名・要件の本文・効果の文言を横断して探す。見つからなければ、見つからないと返す(推測しない)。
{ "type": "object", "required": [ "q" ], "properties": { "q": { "type": "string", "description": "探したい語。例: 特別管理加算 / ターミナル / 指示書" }, "limit": { "type": "integer", "description": "最大件数(既定 20)" } }, "additionalProperties": false }arguments 17 linesjhnrd_get_item reads open 5h ago
項目1件の全部。要件・効果・期限に加えて、参照している出典を素性(tier)と現行かどうかつきで解決して返す。
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "項目の id。例: genzan-bcp" } }, "additionalProperties": false }arguments 13 linesjhnrd_how_to_cite reads unknown never probed
引用の仕方。版(seed 番号)を添えること。訂正しても元の記述を消さない方針のため、版が分からないと後から突き合わせられない。
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesjhnrd_disclosure reads unknown never probed
誰がこれを作り、誰に養われているか。利益相反の開示。出典の素性を名乗ることを規律にしている以上、この口自身の素性も名乗る。
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesjhnrd_unconfirmed reads unknown never probed
原文で確認できていない要件の一覧と、なぜ確認できていないかの理由。空欄にせず残してあるもの。このデータベースの弱いところを、先に見るための口。
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesjhnrd_conflicts reads unknown never probed
出典どうし、あるいは同じ出典の読み取りどうしが食い違った記録。解決済みも残す。どちらかを選んで黙る、ということをしていない証拠でもある。
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesjhnrd_gaps reads unknown never probed
埋まっていないもの(known_gaps)、取りに行って取れなかった記録(attempts)、途中まで分かったこと(findings)。何が無いかを、無いと言えるようにするための口。
{ "type": "object", "properties": { "include_resolved": { "type": "boolean", "description": "解決済みの gap も含める" } }, "additionalProperties": false }arguments 10 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id3ea7ad9ec1cfb6d0.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/3ea7ad9ec1cfb6d0/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/3ea7ad9ec1cfb6d0?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.