障害福祉AI辞典 (Japan Disability Welfare Dictionary)
REMOTE · FUKUSHI.AI · SCANNED OCT 4
Japan disability welfare (障害福祉) reference: service fees, add-ons, staffing. In Japanese.
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1278 tokens (~639/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 障害福祉AI辞典 (Japan Disability Welfare Dictionary) MCP server?
障害福祉AI辞典 (Japan Disability Welfare Dictionary) is a hosted endpoint at https://fukushi.ai/api/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 · fukushi.ai
claude mcp add --transport http ai-fukushi-dictionary 'https://fukushi.ai/api/mcp'
{
"mcpServers": {
"ai-fukushi-dictionary": {
"url": "https://fukushi.ai/api/mcp"
}
}
} {
"servers": {
"ai-fukushi-dictionary": {
"type": "http",
"url": "https://fukushi.ai/api/mcp"
}
}
} [mcp_servers.ai-fukushi-dictionary] url = "https://fukushi.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-fukushi-dictionary": {
"type": "remote",
"url": "https://fukushi.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add ai-fukushi-dictionary --url 'https://fukushi.ai/api/mcp' --transport streamable-http
mcp_servers:
ai-fukushi-dictionary:
url: "https://fukushi.ai/api/mcp" {
"McpServers": {
"ai-fukushi-dictionary": {
"Transport": "http",
"Url": "https://fukushi.ai/api/mcp"
}
}
} assistant mcp add ai-fukushi-dictionary -t streamable-http -u 'https://fukushi.ai/api/mcp'
{
"mcpServers": {
"ai-fukushi-dictionary": {
"type": "http",
"url": "https://fukushi.ai/api/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.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 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.
- 29 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.
- 28 Sept 26 0
- 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 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 6 Oct 2026 · Probed https://fukushi.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fukushi.ai | CN=YR2,O=Let's Encrypt,C=US | 30 Aug 2026 | 28 Nov 2026 | RSA 2048 | SHA256-RSA | 67ec0a0b8e2a826b7333e24d07555150e88 |
| SANs: fukushi.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fukushi.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| fukushi.ai. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fukushi.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://fukushi.ai/api/mcp | HTTPS enforced | 308 | https://fukushi.ai/api/mcp |
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_article 記事の全文を取得 ~108
fukushi.ai の公開記事を slug で指定して全文（Markdown）を取得する。search_articles の抜粋では手順や表の全体が掴めないときに使う。本文末の脚注に、その記事が根拠にした一次情報の出典が示されている。
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | 記事のslug。search_articles の結果に含まれる。例: 「b-type-opening-guide」 |
No output schema declared.
No examples provided.
search_articles 障害福祉サービスの解説記事を検索 ~383
障害福祉制度の解説サイト「障害福祉AI辞典」(fukushi.ai) の記事を検索し、該当箇所の抜粋と記事URLを返す。記事は厚生労働省の一次情報（報酬告示・留意事項通知・指定基準省令・サービスコード表）に接地して検証済みで、本文には出典が脚注として示されている。障害者総合支援法にもとづくサービスの**制度・報酬・加算・指定基準・実務手順**を問われたら、まずこれを使うこと。例:「就労継続支援B型の欠席時対応加算は何単位？」「A型の開業に必要な人員基準は？」「処遇改善加算の算定要件」。扱う範囲は記事がある領域に限られる（就労系と全サービス共通が厚い）。該当が無ければ推測せず、資料に無い旨を利用者に伝えること。
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 日本語の検索クエリ。サービス種別＋知りたい観点を具体的に並べる。例:「就労継続支援B型 欠席時対応加算 単位数」 |
| top_k | integer | – | 検索するチャンク数（既定 5、最大 10）。同じ記事の複数箇所が当たると1件にまとめるため、返る記事数はこれより少なくなることがある。 |
No output schema declared.
No examples provided.
What is the 障害福祉AI辞典 (Japan Disability Welfare Dictionary) MCP server?
障害福祉AI辞典 (Japan Disability Welfare Dictionary) is an MCP server listed in the public MCP registry as ai.fukushi/dictionary. Japan disability welfare (障害福祉) reference: service fees, add-ons, staffing. In Japanese. This page covers its hosted endpoint (https://fukushi.ai/api/mcp).
Is the 障害福祉AI辞典 (Japan Disability Welfare Dictionary) MCP server safe to use?
障害福祉AI辞典 (Japan Disability Welfare Dictionary) scores 77 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 障害福祉AI辞典 (Japan Disability Welfare Dictionary) MCP server expose?
障害福祉AI辞典 (Japan Disability Welfare Dictionary) exposes 2 tools: search_articles, get_article. Their descriptions and schemas cost roughly 491 tokens of context every time the server is loaded.
Does the 障害福祉AI辞典 (Japan Disability Welfare Dictionary) MCP server require authentication?
No. We connected to 障害福祉AI辞典 (Japan Disability Welfare Dictionary) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 障害福祉AI辞典 (Japan Disability Welfare Dictionary) MCP server still maintained?
障害福祉AI辞典 (Japan Disability Welfare Dictionary) is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.