yasashii.org MCP server
io.github.dror-jp/yasashii-org-mcpdror-jpstreamable-httpv1.1.3Scanned
Human-verified Easy Japanese versions of Japanese administrative and disaster-preparedness info.
4 tools: 4 only read.
- Reads private data · 3
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the yasashii.org MCP server can do
The yasashii.org MCP server is published by the GitHub account dror-jp. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
3 tools read private data (list_documents, get_document and get_meta).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.1.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
get_documentGet one Easy Japanese document by ID: full Markdown body (with furigana in 《…》 and wakachi-gaki spacing, ready to hand to a reader), plain-Japanese term explanations, human-verifie…Reads private dataNo findings
Why it is in this group
- The name "get_document" says "get": a word for reading.
What it can reach
- private-dataThe name "get_document" says "get" and "document": it reads documents.
- private-dataThe description's first sentence says "get" and "document": it reads documents.
Description, as the server wrote it Get one Easy Japanese document by ID: full Markdown body (with furigana in 《…》 and wakachi-gaki spacing, ready to hand to a reader), plain-Japanese term explanations, human-verified primary-source links (go.jp / e-Gov) and the last_verified date. Use list_documents first to find the ID.
Annotations the server declares
- title: Get a document
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_metaGet API metadata for yasashii.org: all endpoints, the oldest verification date across documents, license and attribution.Reads private dataNo findings
Why it is in this group
- The name "get_meta" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "document": it reads documents.
Description, as the server wrote it Get API metadata for yasashii.org: all endpoints, the oldest verification date across documents, license and attribution.
Annotations the server declares
- title: Get API metadata
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_documentsList all Easy Japanese (やさしい日本語) documents on yasashii.org — Japanese administrative procedures (転入届, 国民健康保険, 国民年金, マイナンバーカード, 在留期間の更新...) and disaster preparedness (避難所, 119番...).Reads private dataNo findings
Why it is in this group
- The name "list_documents" says "list": a word for reading.
What it can reach
- private-dataThe name "list_documents" says "list" and "document": it reads documents.
- private-dataThe description's first sentence says "list" and "document": it reads documents.
Description, as the server wrote it List all Easy Japanese (やさしい日本語) documents on yasashii.org — Japanese administrative procedures (転入届, 国民健康保険, 国民年金, マイナンバーカード, 在留期間の更新...) and disaster preparedness (避難所, 119番...). Each has a stable ID, a one-line summary, and a verification tier.
Annotations the server declares
- title: List documents
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_termsLook up Japanese administrative terms (住民票, 転入届, 保険料, 避難所...) and get their Easy Japanese (やさしい日本語) explanations — plain wording a non-native reader can understand.No findings
Why it is in this group
- The name "search_terms" says "search": a word for reading.
Description, as the server wrote it Look up Japanese administrative terms (住民票, 転入届, 保険料, 避難所...) and get their Easy Japanese (やさしい日本語) explanations — plain wording a non-native reader can understand. Matches the term, its reading, or words inside the explanation.
Annotations the server declares
- title: Search terms
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:21 UTC, unchanged since Nov 10, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http yasashii-org https://mcp.yasashii.org/mcpclaude mcp add --transport http yasashii-org https://mcp.yasashii.org/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__yasashii-org__list_documents",
"mcp__yasashii-org__get_document",
"mcp__yasashii-org__search_terms",
"mcp__yasashii-org__get_meta"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as yasashii-org. Review it before you use it.
Capability tags behind 3 rules
- mcp__yasashii-org__list_documents private-data
- mcp__yasashii-org__get_document private-data
- mcp__yasashii-org__get_meta private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.dror-jp/yasashii-org-mcp/verify?hash=efcbcfb07cc6923a15ef38fae35a42a1ea67c963c8c16bbbfd43d078a374b33b" | jq -e '.changed == false'Pinned hash efcbcfb07cc6, from Nov 10, 2026, 06:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.dror-jp/yasashii-org-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.dror-jp/yasashii-org-mcp)Source: MCP Registry · repository. Synced Nov 10, 2026, 06:17 UTC.
yasashii.org MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the yasashii.org MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the yasashii.org MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the yasashii.org MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the yasashii.org MCP server have?
- 4 tools: 4 read. list_documents, get_document, search_terms and get_meta.
Does the yasashii.org MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the yasashii.org MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the yasashii.org MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.