# io.github.smeet666/mcp-rule34 (npm · mcp-rule34)

Search rule34.xxx posts by tag through the site's own API. Needs a rule34.xxx API key.

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

## Components

- mcpb · `mcp-rule34-2.0.2.mcpb`: 52/100, [markdown](https://verifymcp.io/servers/smeet666-mcp-rule34/https-github-com-smeet666-mcp-rule34-releases-download-v2-0-2-mcp-rule34-2-0-2-m.md), [page](https://verifymcp.io/servers/smeet666-mcp-rule34/https-github-com-smeet666-mcp-rule34-releases-download-v2-0-2-mcp-rule34-2-0-2-m)
- npm · `mcp-rule34`: 91/100 (this document), [markdown](https://verifymcp.io/servers/smeet666-mcp-rule34/mcp-rule34.md), [page](https://verifymcp.io/servers/smeet666-mcp-rule34/mcp-rule34)

## Channel facts

- Registry: `npm`
- Package: `mcp-rule34`
- Version: `2.0.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 103 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to smeet666/mcp-rule34).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 20 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 938 tokens (~312/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**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 io.github.smeet666/mcp-rule34 server?

io.github.smeet666/mcp-rule34 runs locally as an npm package, launched with npx -y mcp-rule34. 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 smeet666-mcp-rule34 -- npx -y mcp-rule34
```

### Cursor

```json
{
  "mcpServers": {
    "smeet666-mcp-rule34": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-rule34"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "smeet666-mcp-rule34": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-rule34"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add smeet666-mcp-rule34 -- npx -y mcp-rule34
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "smeet666-mcp-rule34": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-rule34"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add smeet666-mcp-rule34 --command npx --arg -y --arg mcp-rule34
```

### Hermes

```yaml
mcp_servers:
  smeet666-mcp-rule34:
    command: "npx"
    args: ["-y", "mcp-rule34"]
```

### Netclaw

```json
{
  "McpServers": {
    "smeet666-mcp-rule34": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-rule34"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add smeet666-mcp-rule34 -t stdio -c npx -a -y mcp-rule34
```

### Other

```json
{
  "mcpServers": {
    "smeet666-mcp-rule34": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-rule34"
      ]
    }
  }
}
```

## 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 91, +1)

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

### 2026-09-17 (score 90, +1)

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

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

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

### 2026-09-13 (score 88, +1)

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

### 2026-09-10 (score 87, +1)

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

### 2026-09-08 (score 86, +1)

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

### 2026-09-06 (score 85, +1)

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

### 2026-09-04 (score 84, +1)

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

## MCP tools (3)

### `search_posts` (~399 tokens)

Search posts by tag

Search rule34.xxx for posts carrying a tag, or several tags at once. Tags are written as one token, so a name said as words is joined by underscores: 'asuka langley sohryu' and 'ranma 1/2' are single tags, and this tool joins them for you. Returns each post's page, its image or video URL, dimensions, score and rating, alongside the number of posts the whole search matches. A row shows the first 12 of a post's tags and says how many it has; call get_post for the whole list with a kind for every tag. Use 'media_type' to ask for still images, animations or video; the site classifies these itself. When a search finds nothing, the answer names the tags rule34.xxx does not hold, or says how many posts the tags match once the restrictions are dropped.

Input parameters:

- `any_of` (array): Tags a post must carry at least one of.
- `exclude` (array): Tags a post must not carry, such as ['monochrome'] to leave out black and white.
- `limit` (integer)
- `media_type` (string): 'image' for stills, 'animated' for GIFs, 'video' for MP4. The site states this in its own tags, so the classification is as good as the tagging.
- `page` (integer)
- `rating` (string): The two ratings rule34.xxx holds. Leave unset to search both.
- `sort` (string): 'score' is the site's own tally of votes, recomputed once a day. 'id' is newest first. 'updated' is by when a post last changed, which retagging moves. 'random' draws a different set on each call.
- `tags` (array, required): Tags a post must all carry, such as ['asuka langley sohryu', 'black hair'].

Output parameters:

- `any_of` (array): The alternatives, as rule34.xxx spells them.
- `exclude` (array): The excluded tags, as rule34.xxx spells them.
- `has_more` (boolean)
- `next_page`
- `notes` (array)
- `page` (integer)
- `posts` (array)
- `query` (string): The search as it was sent, in the site's own language.
- `source` (string)
- `tags` (array): The required tags, as rule34.xxx spells them.
- `total` (integer): Posts the whole search matches, as counted by the site.

### `get_post` (~170 tokens)

Read one post

Read one rule34.xxx post, named by its id or by a link to its page. Returns every tag the post carries, each with its kind (character, copyright, artist, general or metadata) and how many posts share it, alongside the image or video, the dimensions, the score, the rating, the uploader, the number of comments, the credited source and the date the site took the post in. Use this after a search, whose rows show only the first few tags of each post.

Input parameters:

- `id` (integer): The post's numeric id, as a search returns it.
- `url` (string): A link to the post's page, such as https://rule34.xxx/index.php?page=post&s=view&id=2195419. The link is read rather than followed.

Output parameters:

- `changed_at` (string|null): When the post last changed, ISO 8601.
- `comment_count`
- `created_at` (string|null): When the post was added to rule34.xxx, ISO 8601. The site imported much of its older catalogue in bulk, so thousands of posts share one day.
- `file_url` (string)
- `has_notes` (boolean)
- `height` (integer)
- `id` (integer)
- `md5` (string)
- `notes` (array)
- `owner` (string|null): The account that uploaded the post.
- `parent_id`
- `post_url` (string)
- `preview_url` (string|null)
- `rating` (string)
- `sample_url` (string|null)
- `score` (integer): The site's own score, updated once a day.
- `source` (string|null)
- `source_site` (string)
- `status` (string)
- `tags` (array)
- `width` (integer)

### `find_tags` (~124 tokens)

Find how a tag is spelled

Find how rule34.xxx spells a tag, and how many posts carry it. The site matches from the start of a name, so 'kimagure' finds 'kimagure_orange_road' while 'orange road' finds nothing. It offers at most ten names. Use this before searching when a name might be spelled differently, and after a search that found nothing because a tag does not exist.

Input parameters:

- `query` (string, required): The start of a tag name, such as 'kimagure' or 'prince of tennis'. Spaces are joined with underscores.

Output parameters:

- `notes` (array)
- `query` (string): The text as rule34.xxx would spell it.
- `source` (string)
- `tags` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/smeet666-mcp-rule34/mcp-rule34#diagnostics

## Score history

- 2026-09-20: 91
- 2026-09-19: 91
- 2026-09-18: 90
- 2026-09-17: 90
- 2026-09-16: 89
- 2026-09-15: 89
- 2026-09-14: 88
- 2026-09-13: 88
- 2026-09-12: 87
- 2026-09-11: 87
- 2026-09-10: 87
- 2026-09-09: 86
- 2026-09-08: 86
- 2026-09-07: 85
- 2026-09-06: 85
- 2026-09-05: 84
- 2026-09-04: 84
- 2026-09-03: 83
- 2026-09-02: 83
- 2026-09-01: 82
- 2026-08-31: 82
- 2026-08-30: 66
- 2026-08-29: 66
- 2026-08-28: 80
- 2026-08-27: 80
- 2026-08-26: 69
- 2026-08-25: 77
- 2026-08-24: 77

## Common questions

### What is the io.github.smeet666/mcp-rule34 server?

io.github.smeet666/mcp-rule34 is listed in the public MCP registry as io.github.smeet666/mcp-rule34. Search rule34.xxx posts by tag through the site's own API. Needs a rule34.xxx API key. This page covers its npm package (mcp-rule34).

### Is the io.github.smeet666/mcp-rule34 server safe to use?

io.github.smeet666/mcp-rule34 scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.smeet666/mcp-rule34 server expose?

io.github.smeet666/mcp-rule34 exposes 3 tools: search_posts, get_post, find_tags. Their descriptions and schemas cost roughly 693 tokens of context every time the server is loaded.

### Is the io.github.smeet666/mcp-rule34 server still maintained?

io.github.smeet666/mcp-rule34 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.

### What licence is the io.github.smeet666/mcp-rule34 server under?

io.github.smeet666/mcp-rule34 declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/mcp-rule34
- Socket report: https://socket.dev/npm/package/mcp-rule34
- Repository: https://github.com/smeet666/mcp-rule34
- Changelog RSS feed: https://verifymcp.io/servers/smeet666-mcp-rule34/mcp-rule34.xml
- Changelog JSON feed: https://verifymcp.io/servers/smeet666-mcp-rule34/mcp-rule34.json
- HTML version of this page: https://verifymcp.io/servers/smeet666-mcp-rule34/mcp-rule34