# io.github.yukihamada/tokkyo-maru (remote · tokkyo-maru.fly.dev)

特許まる — 発明を入れるだけで特許性の事前診断・明細書骨子・新規性喪失(特許法30条)判定。本人/弁理士の出願支援(代理しない)。

- Trust score: 53/100 (low)
- Change this week: +16
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `tokkyo-maru.fly.dev`: 53/100 (this document), [markdown](https://verifymcp.io/servers/yukihamada-tokkyo-maru/tokkyo-maru.md), [page](https://verifymcp.io/servers/yukihamada-tokkyo-maru/tokkyo-maru)

## Channel facts

- Endpoint: `https://tokkyo-maru.fly.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 36/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 712 tokens (~237/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 33% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http yukihamada-tokkyo-maru https://tokkyo-maru.fly.dev/mcp
```

### Codex

```toml
[mcp_servers.yukihamada-tokkyo-maru]
url = "https://tokkyo-maru.fly.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yukihamada-tokkyo-maru": {
      "type": "remote",
      "url": "https://tokkyo-maru.fly.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yukihamada-tokkyo-maru --url https://tokkyo-maru.fly.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  yukihamada-tokkyo-maru:
    url: "https://tokkyo-maru.fly.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "yukihamada-tokkyo-maru": {
      "type": "http",
      "url": "https://tokkyo-maru.fly.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 52, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 51, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 49, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 48, +11)

- [security regression] HSTS header: unverified → fail
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

### 2026-07-27 (score 37, −9)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 46)

First indexed and scored.

## MCP tools (3)

### `tokkyo_analyze` (~367 tokens)

発明（名称・技術分野・課題・解決手段・技術事実）を渡すと、特許性を事前診断する。IPC候補・新規性喪失(特許法30条)・記載要件・発明適格性・進歩性を◯△✕で自己診断し、先行技術調査の角度とクエリも返す。代理出願はしない(本人/弁理士支援)。最終判断は弁理士。

Input parameters:

- `category` (string): software | chem | other
- `claimCores` (array): 独立項の核 [{kind:装置/方法/プログラム/組成物/製造方法/用途/システム, core:限定文}]
- `disclosures` (array): 自己公開歴 [{where, date:YYYY-MM-DD}]（新規性喪失判定用）
- `facts` (array): 実装事実・数値・手順(実施可能要件の裏付け)
- `field` (string): 技術分野
- `ipc` (array)
- `priorArt` (array): [{id, title, threat:高/中/低}]
- `problem` (string): 解決しようとする課題
- `solution` (string): 課題を解決するための手段(=独立項の要旨)
- `title` (string, required): 発明の名称
- `today` (string): 判定基準日 YYYY-MM-DD（30条の残余月数計算に使用）

### `tokkyo_draft` (~177 tokens)

発明から、特許明細書一式の骨子(tokkyo.json正本＋特許請求の範囲＋明細書セクション＋要約)を決定論生成して返す。bim.house の bim.json／商標まるの shohyo.json に相当。tokkyo_check も同梱。

Input parameters:

- `applicant` (string)
- `category` (string)
- `claimCores` (array)
- `disclosures` (array)
- `facts` (array)
- `field` (string)
- `ipc` (array)
- `priorArt` (array)
- `problem` (string)
- `solution` (string)
- `title` (string, required)
- `today` (string)

### `tokkyo_check` (~168 tokens)

tokkyo.json を渡すと、新規性喪失(特許法30条)・記載要件(サポート/実施可能)・発明適格性・進歩性を、その場で決定論的に◯△✕判定する。bim.house の houki_check(建築基準法その場判定)の特許版。登録可否の法的確定ではない(最終は弁理士)。

Input parameters:

- `category` (string)
- `claimCores` (array)
- `disclosures` (array)
- `facts` (array)
- `priorArt` (array)
- `title` (string, required)
- `today` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/yukihamada-tokkyo-maru/tokkyo-maru#diagnostics

## Score history

- 2026-08-03: 53
- 2026-08-02: 52
- 2026-08-01: 52
- 2026-07-31: 51
- 2026-07-30: 49
- 2026-07-29: 48
- 2026-07-28: 48
- 2026-07-27: 37
- 2026-07-26: 46

## Links

- Remote endpoint: https://tokkyo-maru.fly.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/yukihamada-tokkyo-maru/tokkyo-maru/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/yukihamada-tokkyo-maru/tokkyo-maru/changelog.json
- HTML version of this page: https://verifymcp.io/servers/yukihamada-tokkyo-maru/tokkyo-maru