ddddocr Smithery MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ocr_recognizeC | Perform OCR recognition on an image to extract text content |
| text_detectionA | Detect text regions and bounding boxes in an image |
| slide_matchC | Match sliding captcha pieces to find the correct position |
| slide_comparisonA | Compare two images to find the sliding distance for captcha solving |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
ocr_recognize and text_detection are fairly distinguishable, but slide_match and slide_comparison both target sliding captcha solving with descriptions that seem to describe the same task. The boundary between matching pieces and comparing images for a sliding distance is unclear.
All names use snake_case and have recognizable prefixes, but verb/noun forms are inconsistent: ocr_recognize uses a verb while text_detection and slide_comparison use nouns. slide_match and slide_comparison follow a common slide_ pattern, yet the overall set is not uniformly structured.
Four tools is a reasonable size for an OCR and captcha-focused server. However, slide_match and slide_comparison appear redundant, so the count is acceptable but not perfectly lean.
The core OCR recognition, text detection, and sliding captcha workflows are covered. Minor gaps include lack of a dedicated captcha classification tool or preprocessing utilities, but they are likely workarounds given the stated scope.