tokkyo-maru MCP server
io.github.yukihamada/tokkyo-maruyukihamadastreamable-httpv0.1.0Scanned
特許まる — 発明を入れるだけで特許性の事前診断・明細書骨子・新規性喪失(特許法30条)判定。本人/弁理士の出願支援(代理しない)。
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- 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 tokkyo-maru MCP server can do
The tokkyo-maru MCP server is published by the GitHub account yukihamada. It has 3 tools. It can create or change data (2 tools: tokkyo_draft and tokkyo_check), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
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 21, 2026, version 0.1.0.
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.
3 tools
Changes things 2Claude Code: ask
tokkyo_checktokkyo.json を渡すと、新規性喪失(特許法30条)・記載要件(サポート/実施可能)・発明適格性・進歩性を、その場で決定論的に◯△✕判定する。bim.house の houki_check(建築基準法その場判定)の特許版。登録可否の法的確定ではない(最終は弁理士)。No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it tokkyo.json を渡すと、新規性喪失(特許法30条)・記載要件(サポート/実施可能)・発明適格性・進歩性を、その場で決定論的に◯△✕判定する。bim.house の houki_check(建築基準法その場判定)の特許版。登録可否の法的確定ではない(最終は弁理士)。
tokkyo_draft発明から、特許明細書一式の骨子(tokkyo.json正本+特許請求の範囲+明細書セクション+要約)を決定論生成して返す。bim.house の bim.json/商標まるの shohyo.json に相当。tokkyo_check も同梱。No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 発明から、特許明細書一式の骨子(tokkyo.json正本+特許請求の範囲+明細書セクション+要約)を決定論生成して返す。bim.house の bim.json/商標まるの shohyo.json に相当。tokkyo_check も同梱。
Only reads 1Show 1 read-only tool
tokkyo_analyze発明(名称・技術分野・課題・解決手段・技術事実)を渡すと、特許性を事前診断する。IPC候補・新規性喪失(特許法30条)・記載要件・発明適格性・進歩性を◯△✕で自己診断し、先行技術調査の角度とクエリも返す。代理出願はしない(本人/弁理士支援)。最終判断は弁理士。No findings
Why it is in this group
- The name "tokkyo_analyze" says "analyze": a word for reading.
Description, as the server wrote it 発明(名称・技術分野・課題・解決手段・技術事実)を渡すと、特許性を事前診断する。IPC候補・新規性喪失(特許法30条)・記載要件・発明適格性・進歩性を◯△✕で自己診断し、先行技術調査の角度とクエリも返す。代理出願はしない(本人/弁理士支援)。最終判断は弁理士。
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 private-data or untrusted-input or outbound.
- Reads private data0
- 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 20, 2026, 19:13 UTC, unchanged since Oct 22, 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
- 2
- Protocol version
- 2024-11-05
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://tokkyo-maru.fly.dev/mcp: tools/list returned 3 tools to an anonymous client, including tokkyo_draft (write), tokkyo_check (write)
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 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http tokkyo-maru https://tokkyo-maru.fly.dev/mcpclaude mcp add --transport http tokkyo-maru https://tokkyo-maru.fly.dev/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__tokkyo-maru__tokkyo_analyze"
],
"ask": [
"mcp__tokkyo-maru__tokkyo_draft",
"mcp__tokkyo-maru__tokkyo_check"
],
"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 tokkyo-maru. Review it before you use it.
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.yukihamada/tokkyo-maru/verify?hash=50191fc18255c8db8b2baa5ac7390b02b5212c38b6e97b24bd1f676f2fb16501" | jq -e '.changed == false'Pinned hash 50191fc18255, from Nov 21, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.yukihamada/tokkyo-maru/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.yukihamada/tokkyo-maru)Source: MCP Registry. Synced Oct 21, 2026, 18:52 UTC.
tokkyo-maru MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the tokkyo-maru MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the tokkyo-maru MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the tokkyo-maru 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 tokkyo-maru MCP server have?
- 3 tools: 2 write, 1 read. tokkyo_draft, tokkyo_check and tokkyo_analyze.
Does the tokkyo-maru MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the tokkyo-maru MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the tokkyo-maru MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.