A single-entry local MCP server that routes image tasks to Anthropic-compatible or OpenAI-compatible vision APIs.
Single tool 'process_images' has a clear, action-oriented name and comprehensive description (194 chars). Input schema is well-structured with proper types, minItems constraint, and parameter descriptions. However, output schema is completely undocumented, the tool returns unstructured text from vision APIs with no guidance on format, structure, or fields. Error handling is minimal: missing env vars throw generic errors without recovery guidance. No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Parameter descriptions are adequate but lack format constraints (e.g., valid image extensions, max file size guidance in param description rather than only in code).
General-purpose vision tool for one or more local images. Use it for OCR, extracting structured information, describing content, answering questions, locating elements, summarizing screenshots, or reasoning across multiple images in a single API call.
Output schema completely undocumented. Tool returns free-form text from vision APIs with no structured schema, field definitions, or format guidance. LLMs cannot plan downstream operations or extract structured data reliably.
Error handling lacks recovery guidance. Missing environment variables throw generic 'Missing environment variable(s)' errors without suggesting next steps (e.g., 'Set VISION_API_KEY to your Anthropic or OpenAI API key'). Vision API failures return raw HTTP status + truncated response body with no actionable guidance.
Parameter 'image_paths' lacks format constraints in description. Code enforces file existence, extension validation (png/jpg/jpeg/webp/gif/bmp), and optional size limits, but these constraints are not documented in the parameter description. LLMs cannot self-validate inputs.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
No tool annotations. Tool is read-only (processes images, no side effects) but lacks readOnlyHint annotation. This prevents clients from optimizing caching, retry logic, or safety policies.
STDIO transport only. Server is not remotely accessible and cannot be used by hosted MCP clients. Limits deployment to local/containerized environments only.