Skip to main content
Glama
NazarLysyi

Brickognize MCP Server

by NazarLysyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Brickognize MCP Server

No user-submitted related servers found.

    Related Servers

    • ai-vision

      kaijia323
      A
      license
      A
      quality
      C
      maintenance
      Provides image recognition capabilities to MCP clients by integrating with OpenAI-compatible vision models, supporting local images, URLs, multi-image comparison, and model listing.
      4
      MIT

    • openai-vision-mcp-server

      ygq-future
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables image analysis via OpenAI-compatible vision APIs, supporting local files, URLs, and base64 inputs with intelligent tiling for high-resolution images. Provides a secure, configurable MCP stdio server for structured vision analysis.
      184 npm
      2
      MIT

    • Gemini OCR MCP Server

      WindoC
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides OCR services powered by Google's Gemini API to extract text from images via file paths or base64 strings. It enables high-accuracy text recognition and CAPTCHA processing through simple MCP tools.
      8
      -

    • vision-mcp

      sulghu
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for image recognition and OCR via OpenAI-compatible vision APIs, supporting local files, URLs, and data URLs. Enables natural language image description and text extraction.
      14 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.5/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools are mostly distinct with clear purposes: health check, general identification, and specialized identification for minifigures, parts, and sets. However, there is some overlap between brickognize_identify and the specialized tools, as the general tool can also identify these items, potentially causing confusion about when to use which. The descriptions help clarify, but the overlap exists.

    Naming Consistency5/5

    All tool names follow a consistent pattern: they start with 'brickognize_' followed by a verb or verb phrase (e.g., 'health', 'identify', 'identify_fig', 'identify_part', 'identify_set'). This snake_case naming is uniform across all tools, making them predictable and easy to understand.

    Tool Count5/5

    With 5 tools, the count is well-scoped for the server's purpose of LEGO item recognition. It includes a health check and multiple identification tools covering different item types, which is appropriate and manageable without being too sparse or overwhelming.

    Completeness4/5

    The tool set covers the core functionality of checking service health and identifying various LEGO items (general, minifigures, parts, sets), which aligns well with the domain. A minor gap is the lack of tools for additional operations like batch processing or detailed metadata retrieval, but the provided tools support the main workflows effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources