Skip to main content
Glama
smeet666

mcp-rule34

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RULE34_API_KEYYesYour API key, which is personal.
RULE34_USER_IDYesYour numeric account id.
RULE34_LOG_LEVELNosilent, error, info or debug, written to stderr.error
RULE34_TIMEOUT_MSNoDeadline for one request, from 1000 to 120000.20000
RULE34_USER_AGENTNoNames your application to the site, with an address where a person can be reached.the project identity
RULE34_MAX_RETRIESNoAttempts after a transient failure, from 0 to 10.3
RULE34_CACHE_TTL_MSNoHow long an answer stays in memory, from 0 to 86400000.300000
RULE34_MIN_INTERVAL_MSNoGap between two requests, from 1000 to 60000.1000
RULE34_CACHE_MAX_ENTRIESNoAnswers held in memory at once, from 0 to 10000.300

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_postsA

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.

get_postA

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.

find_tagsA

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.8/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: search_posts queries by tags, get_post retrieves one post's full details, and find_tags resolves tag spellings. There is no overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow the same verb_noun pattern: search_posts, get_post, find_tags. The naming is predictable and consistent, making it easy for an agent to infer what each tool does.

Tool Count5/5

Three tools is an appropriate scope for a focused rule34.xxx client: find tags, search posts, and inspect a single post. Each tool earns its place and there is no unnecessary bloat.

Completeness5/5

The tool set covers the core user workflow end to end: discovering the correct tag, searching posts with filters, and retrieving complete post metadata. No obvious missing operation is needed for the server's stated purpose.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive