imagedata

imagedata is a small local bridge to the hosted HasData Google Images MCP server, which returns Google Images search results as JSON. Give it a query, and it fetches that query's image results: for each image, the title, the page it appears on, the direct image URL, a thumbnail, its dimensions, the source name and its position in the results. Searches can be shaped with the tbs filter string (image size, dominant color, and image type such as face, photo, clipart, line art or animated), safesearch, the similar/omitted-results filter toggle, a Google domain, country and language codes, a canonical or encoded location, a device type, and page-based pagination.

The bridge stores no results of its own. It serves the upstream server's tool list locally, exactly as captured from the live endpoint, and forwards each tool call upstream, returning the result untouched. The captured surface is a single read-only fetch: there is no write, messaging, or payment tool in it.

Tools

• hasdata_google_images_images_getImageSearchResults — fetch one page of Google Images results. Required: q (the search term). Optional: location (Google canonical location), uule (encoded location parameter), domain (the Google domain to use, e.g. google.com), gl (two-letter country code), hl (two-letter language code), tbs (filter string combining size filters such as isz:l, color filters such as ic:color, and type filters such as itp:photo), safe (active / off), filter (1 or 0: similar/omitted-results filtering), deviceType (desktop / mobile / tablet), and ijn (page number, 0 is the first page). Returns each image with title, source page URL, direct image URL, thumbnail, dimensions, source name, and position.

Configuration

• HASDATA_GOOGLE_IMAGES_MCP_URL (optional) — override the upstream endpoint. Defaults to https://mcp.hasdata.com/mcp?apis=google_images. (The override hook is this rebuild's own labelled reconstruction.)
• HASDATA_API_KEY (optional) — when set, every upstream request carries an x-api-key: <key> header, for the caller's own HasData API key. When it is not set, no key header is sent. (The header name and the env name are pinned by the original's registry record; forwarding the key from this env var is a labelled reconstruction — the original surface was captured keyless.)

Forwarding mechanics

On the first tool call the client opens a streamable HTTP session with the upstream: a JSON-RPC initialize request (protocolVersion 2025-03-26, clientInfo name imagedata), then a notifications/initialized notification, then the tools/call request carrying the caller's arguments unchanged. When the upstream answers initialize with an Mcp-Session-Id header, that value rides on every later request of the session, which is reused for the life of the process. Replies may arrive as plain JSON or as server-sent events; both are read.

Successful upstream results pass through verbatim, including any isError flag the upstream sets. Failures — a JSON-RPC error, a non-2xx status, an unreadable response, or a request that cannot be completed — come back as an isError result whose text starts with imagedata error: (this rendering is this rebuild's own labelled reconstruction).

CLI

The tool is also a subcommand taking one JSON argument string:

npx @reneturcios/imagedata hasdata_google_images_images_getImageSearchResults '{"q":"golden retriever puppies","tbs":"isz:l,ic:color,itp:photo","safe":"active"}'
npx @reneturcios/imagedata --version

Exit codes: 0 on success, 1 on an isError result, 2 on a usage error.

MCP server

npx -y @reneturcios/imagedata mcp

MCP client config:

{
  "mcpServers": {
    "imagedata": {
      "command": "npx",
      "args": ["-y", "@reneturcios/imagedata", "mcp"]
    }
  }
}

Docker

docker run -i ghcr.io/cloudcorprecords/imageda

... [View full README on GitHub](https://github.com/cloudcorprecords/imagedata#readme)