io.github.smeet666/mcp-rule34
NPM · MCP-RULE34 · 2 COMPONENTS
Search rule34.xxx posts by tag through the site's own API. Needs a rule34.xxx API key.
Available components
Last scanned (23 hours ago)
Scores higher than 96% of npm servers
Category Search and Retrieval
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 100 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to smeet666/mcp-rule34). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 29 Oct 26 0
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 2.0.2 → 2.1.0 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
- 19 Oct 26 +1
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/mcp-rule34@2.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | smeet666/mcp-rule34 |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/smeet666/mcp-rule34/.github/workflows/publish.yml@refs/tags/v2.1.0 |
| Rekor log index | 3571341080 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:df6efacd5479136a986cfdb1c730707ba916359f4865ce1955fce14209199a4dfb3d173711b99d9085af43387f3429c5d4c0709ada1557af8d5dee988 |
Background: How many MCP packages publish verified provenance →
Dependencies 100 packages
| Packages resolved | 100 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_tags Find how a tag is spelled ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The start of a tag name, such as 'kimagure' or 'prince of tennis'. Spaces are joined with underscores. |
| Name | Type | Req | Description |
|---|---|---|---|
| notes | array | yes | – |
| query | string | yes | The text as rule34.xxx would spell it. |
| source | string | yes | – |
| tags | array | yes | – |
No examples provided.
get_post Read one post ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| changed_at | string|null | yes | When the post last changed, ISO 8601. |
| comment_count | – | yes | – |
| created_at | string|null | yes | 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 | yes | – |
| has_notes | boolean | yes | – |
| height | integer | yes | – |
| id | integer | yes | – |
| md5 | string | yes | – |
| notes | array | yes | – |
| owner | string|null | yes | The account that uploaded the post. |
| parent_id | – | yes | – |
| post_url | string | yes | – |
| preview_url | string|null | yes | – |
| rating | string | yes | – |
| sample_url | string|null | yes | – |
| score | integer | yes | The site's own score, updated once a day. |
| source | string|null | yes | – |
| source_site | string | yes | – |
| status | string | yes | – |
| tags | array | yes | – |
| width | integer | yes | – |
No examples provided.
search_posts Search posts by tag ~399
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Tags a post must all carry, such as ['asuka langley sohryu', 'black hair']. |
| Name | Type | Req | Description |
|---|---|---|---|
| any_of | array | yes | The alternatives, as rule34.xxx spells them. |
| exclude | array | yes | The excluded tags, as rule34.xxx spells them. |
| has_more | boolean | yes | – |
| next_page | – | yes | – |
| notes | array | yes | – |
| page | integer | yes | – |
| posts | array | yes | – |
| query | string | yes | The search as it was sent, in the site's own language. |
| source | string | yes | – |
| tags | array | yes | The required tags, as rule34.xxx spells them. |
| total | integer | yes | Posts the whole search matches, as counted by the site. |
No examples provided.
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.
npm · mcp-rule34
claude mcp add smeet666-mcp-rule34 -- npx -y mcp-rule34
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 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 4 November 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.