Skip to main content
Glama
@mcp/openverse

@mcp/openverse

by neno-is-ooo

Related Servers

Alternatives to @mcp/openverse

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      MCP server for searching and attributing images from Openverse and Wikimedia Commons, enabling insertion via insertUrl and attribution formatting.
      2
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for searching and retrieving Creative-Commons-licensed images and audio from Openverse. Enables AI agents to query open media content.
      204 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      This MCP server enables AI assistants to search for images on Wikimedia Commons, providing detailed metadata and optional thumbnail combinations to assist AI models in visual comparisons.
      1
      2
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server for searching and retrieving photos from Unsplash with proper attribution, designed for LLMs building content pages.
      3
      38
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI assistants to search for royalty-free images from Pexels and Unsplash using natural language, returning structured results with metadata.
      5
      56 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server for browsing and downloading open-licensed imagery from major museum and archive APIs including Wellcome, Met, Library of Congress, Smithsonian, and Europeana.
      12
      13 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools have distinct purposes: get_image_details, get_image_stats, get_related_images, and search_images are clearly differentiated. However, search_images and search_images_for_essay have overlapping functionality, as the latter seems like a specialized version of the former, which could cause minor confusion for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_image_details, search_images). There are no deviations in naming conventions, making the set predictable and easy to parse.

    Tool Count5/5

    With 5 tools, the count is well-scoped for an image search and retrieval server. Each tool serves a specific function in the domain, and there are no extraneous or redundant tools, making the set appropriately sized.

    Completeness4/5

    The tool surface covers core operations for image search and retrieval, including search, details, stats, and related images. A minor gap exists in lacking explicit tools for actions like filtering or advanced search parameters, but agents can likely work around this using the provided search tools.