Search rule34.xxx posts by tag through the site's own API. Needs a rule34.xxx API key.
MCPpedia last refreshed this data
io.github.smeet666/mcp-rule34 is an MCP server that search rule34.xxx posts by tag through the site's own API. Needs a rule34.xxx API key. Its tool list has not been published yet over stdio, requires no API key, and scores 86/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-smeet666-mcp-rule34": {
"command": "npx",
"args": [
"-y",
"mcp-rule34"
]
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Search rule34.xxx posts by tag through the site's own API. Needs a rule34.xxx API key.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'mcp-rule34' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked mcp-rule34 against OSV.dev.
Click any tool to inspect its schema.
This server is missing a description.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
Transport for TMCP using STDIO
The graph based agentic IDE
Buddhist canon tools: search, passages, cross-canon parallels, dictionaries — all URN-cited.
MCP Security Weekly
Get CVE alerts and security updates for io.github.smeet666/mcp-rule34 and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server for rule34.xxx. Search the site's posts by tag through its own API, and get back each post's page, its file, its dimensions, its score, its rating and its full tag list, alongside the number of posts the whole search matches.
This server needs credentials. rule34.xxx issues an API key per account, and its terms allow automated reading through the API alone. Getting one takes a minute and is described under Configuration.
(Version française plus bas / French version below)
Claude Code
claude mcp add rule34 --env RULE34_USER_ID=your-id --env RULE34_API_KEY=your-key -- npx -y mcp-rule34
Claude Desktop, Cursor, and any client using the standard config format
{
"mcpServers": {
"rule34": {
"command": "npx",
"args": ["-y", "mcp-rule34"],
"env": {
"RULE34_USER_ID": "your-id",
"RULE34_API_KEY": "your-key"
}
}
}
}
{
"mcpServers": {
"rule34": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"RULE34_USER_ID",
"-e",
"RULE34_API_KEY",
"ghcr.io/smeet666/mcp-rule34:2.0.0"
],
"env": {
"RULE34_USER_ID": "your-key",
"RULE34_API_KEY": "your-key"
}
}
}
}
-i keeps stdin open, which is where the protocol travels, and no -t is
passed: a TTY rewrites the stream and breaks it. The container needs outbound
HTTPS to rule34.xxx and api.rule34.xxx, and nothing else: no volume, no port, and the keys travel through the environment rather than inside the image.
Put this in your user configuration rather than in a project file: a
.mcp.json at the root of a repository travels with the repository, and the key
travels with it.
| Variable | What it is | Default |
|---|---|---|
RULE34_USER_ID | Your numeric account id. Required. | — |
RULE34_API_KEY | Your API key. Required, and personal. | — |
RULE34_MIN_INTERVAL_MS | Milliseconds between two requests. | 1000, and never lower |
RULE34_TIMEOUT_MS | How long one request may take. | 20000 |
RULE34_MAX_RETRIES | Attempts after the first, for transient failures. | 3 |
RULE34_CACHE_TTL_MS | How long an answer stays in memory. | 300000 |
RULE34_CACHE_MAX_ENTRIES | How many answers stay in memory. | 300 |
RULE34_USER_AGENT | Overrides the agent this client sends. | mcp-rule34/<version> (+…) |
RULE34_LOG_LEVEL | silent, error, info or debug, on stderr. | error |
Where the credentials come from. Sign in, open
Account options, and find
the row named API Access Credentials. It shows &api_key=…&user_id=…; those
two values are what goes in the configuration above. If the key is empty, tick
Generate New Key? and save.
The site issues one key per person and asks that applications serving its content display no advertising and put it behind no paywall. This server ships no key