Skip to main content
Glama
LeviReisJs

openi

by LeviReisJs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to openi

No user-submitted related servers found.

    Related Servers

    • PubMed MCP Server

      openpharma-org
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to search and retrieve biomedical research articles from PubMed's database of over 35 million citations, including metadata, abstracts, MeSH terms, and full-text PDFs when available.
      1
      1
      MIT

    • StatPearls MCP Server

      jpoles1
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides AI systems with access to peer-reviewed medical information from StatPearls, enabling searches for diseases and medical conditions with comprehensive, reliable content formatted in AI-friendly Markdown.
      1
      -

    • openfda-mcp-server

      ek-nath
      A
      license
      A
      quality
      D
      maintenance
      Enables LLMs to search FDA drug labels and adverse event data via the OpenFDA API, supporting natural language queries for drug safety information.
      2
      MIT

    • wikipedia-mcp-image-crawler

      dazeb
      A
      license
      B
      quality
      D
      maintenance
      Enables searching and retrieving images from Wikipedia Commons with detailed metadata including licenses and authors.
      2
      14 npm
      10
      MIT

    • Multimodal MCP

      erickpxd
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables semantic image search using CLIP embeddings and visual question answering through MCP tools, allowing natural language interaction with images.
      -
    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.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely different purposes: one is for looking up filter codes, the other for searching images. There is no overlap or ambiguity.

    Naming Consistency5/5

    Both tools follow a consistent 'openi_verb_noun' pattern using snake_case, making them predictable.

    Tool Count3/5

    With only 2 tools, the server feels thin for a biomedical image search engine. A couple more tools (e.g., fetching image details, listing filters) would be appropriate.

    Completeness3/5

    The search tool covers the primary use case, but there is no way to retrieve dynamic filter options or individual image metadata beyond what the search returns, leaving minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources