# Japanese Article Deep Audit (remote · jp-article-check-paid.9gbnk9sztm.workers.dev)

Paid Japanese article audit for claims, sources, PR disclosure, duplication, and quality.

- Trust score: 64/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `jp-article-check-paid.9gbnk9sztm.workers.dev`: 64/100 (this document), [markdown](https://verifymcp.io/servers/45b6sm69tr-ops-jp-article-check-paid/jp-article-check-paid.md), [page](https://verifymcp.io/servers/45b6sm69tr-ops-jp-article-check-paid/jp-article-check-paid)

## Channel facts

- Endpoint: `https://jp-article-check-paid.9gbnk9sztm.workers.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-09-20.

- **Endpoint Security**: 46/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 1 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - 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**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 74 tokens (~74/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Japanese Article Deep Audit MCP server?

Japanese Article Deep Audit is a hosted endpoint at https://jp-article-check-paid.9gbnk9sztm.workers.dev/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.

### Claude

```bash
claude mcp add --transport http 45b6sm69tr-ops-jp-article-check-paid 'https://jp-article-check-paid.9gbnk9sztm.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "45b6sm69tr-ops-jp-article-check-paid": {
      "url": "https://jp-article-check-paid.9gbnk9sztm.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "45b6sm69tr-ops-jp-article-check-paid": {
      "type": "http",
      "url": "https://jp-article-check-paid.9gbnk9sztm.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.45b6sm69tr-ops-jp-article-check-paid]
url = "https://jp-article-check-paid.9gbnk9sztm.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "45b6sm69tr-ops-jp-article-check-paid": {
      "type": "remote",
      "url": "https://jp-article-check-paid.9gbnk9sztm.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 45b6sm69tr-ops-jp-article-check-paid --url 'https://jp-article-check-paid.9gbnk9sztm.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  45b6sm69tr-ops-jp-article-check-paid:
    url: "https://jp-article-check-paid.9gbnk9sztm.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "45b6sm69tr-ops-jp-article-check-paid": {
      "Transport": "http",
      "Url": "https://jp-article-check-paid.9gbnk9sztm.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add 45b6sm69tr-ops-jp-article-check-paid -t streamable-http -u 'https://jp-article-check-paid.9gbnk9sztm.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "45b6sm69tr-ops-jp-article-check-paid": {
      "type": "http",
      "url": "https://jp-article-check-paid.9gbnk9sztm.workers.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-09-19 (score 64, +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-09-17 (score 63, +1)

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

### 2026-09-15 (score 62, +1)

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

### 2026-09-14 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-13 (score 61)

First indexed and scored.

## MCP tools (1)

### `deep_article_audit` (~74 tokens)

Performs a detailed rule-based audit of Japanese article text. Checks strong claims, numeric claims without sources, duplicate sentences, long sentences and paragraphs, excessive CTA, commercial links, PR disclosure, and article structure. No external AI API is used.

Input parameters:

- `text` (string, required): 監査対象の日本語記事本文

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/45b6sm69tr-ops-jp-article-check-paid/jp-article-check-paid#diagnostics

## Score history

- 2026-09-20: 64
- 2026-09-19: 64
- 2026-09-18: 63
- 2026-09-17: 63
- 2026-09-16: 62
- 2026-09-15: 62
- 2026-09-14: 61
- 2026-09-13: 61

## Common questions

### What is the Japanese Article Deep Audit MCP server?

Japanese Article Deep Audit is an MCP server listed in the public MCP registry as io.github.45b6sm69tr-ops/jp-article-check-paid. Paid Japanese article audit for claims, sources, PR disclosure, duplication, and quality. This page covers its hosted endpoint (https://jp-article-check-paid.9gbnk9sztm.workers.dev/mcp).

### Is the Japanese Article Deep Audit MCP server safe to use?

Japanese Article Deep Audit scores 64 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 Japanese Article Deep Audit MCP server expose?

Japanese Article Deep Audit exposes 1 tool: deep_article_audit. Their descriptions and schemas cost roughly 74 tokens of context every time the server is loaded.

### Does the Japanese Article Deep Audit MCP server require authentication?

No. We connected to Japanese Article Deep Audit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Japanese Article Deep Audit MCP server still maintained?

Japanese Article Deep Audit is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://jp-article-check-paid.9gbnk9sztm.workers.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/45b6sm69tr-ops-jp-article-check-paid/jp-article-check-paid.xml
- Changelog JSON feed: https://verifymcp.io/servers/45b6sm69tr-ops-jp-article-check-paid/jp-article-check-paid.json
- HTML version of this page: https://verifymcp.io/servers/45b6sm69tr-ops-jp-article-check-paid/jp-article-check-paid