# HasData Google Images (remote · mcp.hasdata.com)

Google Images results with source pages, thumbnails and full-resolution URLs, as JSON.

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- remote · `mcp.hasdata.com`: 85/100 (this document), [markdown](https://verifymcp.io/servers/com-hasdata-google-images/mcp.md), [page](https://verifymcp.io/servers/com-hasdata-google-images/mcp)
- npm · `@hasdata/google-images-mcp`: 49/100, [markdown](https://verifymcp.io/servers/com-hasdata-google-images/hasdata-google-images-mcp.md), [page](https://verifymcp.io/servers/com-hasdata-google-images/hasdata-google-images-mcp)
- pypi · `hasdata-google-images-mcp`: 34/100, [markdown](https://verifymcp.io/servers/com-hasdata-google-images/hasdata-google-images-mcp-2.md), [page](https://verifymcp.io/servers/com-hasdata-google-images/hasdata-google-images-mcp-2)

## Channel facts

- Endpoint: `https://mcp.hasdata.com/mcp?apis=google_images`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-16.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 972 tokens (~162/item across 6 items; 1 tools + 5 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the HasData Google Images MCP server?

HasData Google Images is a hosted endpoint at https://mcp.hasdata.com/mcp?apis=google_images, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-hasdata-google-images 'https://mcp.hasdata.com/mcp?apis=google_images'
```

### Cursor

```json
{
  "mcpServers": {
    "com-hasdata-google-images": {
      "url": "https://mcp.hasdata.com/mcp?apis=google_images"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-hasdata-google-images": {
      "type": "http",
      "url": "https://mcp.hasdata.com/mcp?apis=google_images"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-hasdata-google-images]
url = "https://mcp.hasdata.com/mcp?apis=google_images"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hasdata-google-images": {
      "type": "remote",
      "url": "https://mcp.hasdata.com/mcp?apis=google_images",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-hasdata-google-images --url 'https://mcp.hasdata.com/mcp?apis=google_images' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hasdata-google-images:
    url: "https://mcp.hasdata.com/mcp?apis=google_images"
```

### Netclaw

```json
{
  "McpServers": {
    "com-hasdata-google-images": {
      "Transport": "http",
      "Url": "https://mcp.hasdata.com/mcp?apis=google_images"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-hasdata-google-images -t streamable-http -u 'https://mcp.hasdata.com/mcp?apis=google_images'
```

### Other

```json
{
  "mcpServers": {
    "com-hasdata-google-images": {
      "type": "http",
      "url": "https://mcp.hasdata.com/mcp?apis=google_images"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-15 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-09 (score 82, +43)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Stability: unverified → 0.10
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: good
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail

### 2026-09-28 (score 39, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 39, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-22 (score 39)

First indexed and scored.

## MCP tools (1)

### `hasdata_google_images_images_getImageSearchResults` (~761 tokens)

google_images_images: GET /

Get Image Search Results

Scrapes Google Images for a query with advanced filters (size, color, image type, safesearch, domain/country/language, device type) plus page-based pagination (ijn). Returns each image with title, source page URL, direct image URL, thumbnail, dimensions, source name, and position. Use for visual-asset discovery, reverse-image workflows, dataset collection for ML/CV training, brand/logo monitoring, stock-image sourcing, and grounding multimodal LLMs with fresh image context.

Input parameters:

- `deviceType` (string): Specify the device type for the search.
- `domain` (string): Google domain to use. Default is google.com. Provide one exact documented value (195 allowed), e.g. `google.ac`, `google.ad`.
- `filter` (number): Defines whether to enable or disable the filters for 'Similar Results' and 'Omitted Results'. Set to 1 (default) to enable these filters, or 0 to disable them.
- `gl` (string): The two-letter country code for the country you want to limit the search to. Provide one exact documented value (245 allowed), e.g. `ac`, `af`.
- `hl` (string): The two-letter language code for the language you want to use for the search. Provide one exact documented value (159 allowed), e.g. `af`, `ak`.
- `ijn` (number): Page number for paginated results, where 0 is the first page.
- `location` (string): Google canonical location for the search.
- `q` (string, required): Search query term for retrieving image results.
- `safe` (string): Adult Content Filtering option.
- `tbs` (string): `tbs` parameter for the Google Images API customizes image search results with various filters that can be combined using commas. Here are the available options: Image Size Filters:   - `isz:l` - Se…
- `uule` (string): The encoded location parameter.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-hasdata-google-images/mcp#diagnostics

## Score history

- 2026-10-16: 85
- 2026-10-15: 85
- 2026-10-14: 84
- 2026-10-13: 84
- 2026-10-12: 83
- 2026-10-10: 82
- 2026-10-09: 82
- 2026-10-04: 39
- 2026-10-03: 39
- 2026-10-02: 39
- 2026-10-01: 39
- 2026-09-30: 39
- 2026-09-29: 39
- 2026-09-28: 39
- 2026-09-27: 39
- 2026-09-26: 39
- 2026-09-25: 39
- 2026-09-24: 39
- 2026-09-23: 39
- 2026-09-22: 39

## Common questions

### What is the HasData Google Images MCP server?

HasData Google Images is an MCP server listed in the public MCP registry as com.hasdata/google-images. Google Images results with source pages, thumbnails and full-resolution URLs, as JSON. This page covers its hosted endpoint (https://mcp.hasdata.com/mcp?apis=google_images).

### Is the HasData Google Images MCP server safe to use?

HasData Google Images scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the HasData Google Images MCP server expose?

HasData Google Images exposes 1 tool: hasdata_google_images_images_getImageSearchResults. Their descriptions and schemas cost roughly 761 tokens of context every time the server is loaded.

### Does the HasData Google Images MCP server require authentication?

Yes. HasData Google Images asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the HasData Google Images MCP server still maintained?

HasData Google Images is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.hasdata.com/mcp?apis=google_images
- Authorisation metadata: https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/HasData/google-images-mcp
- Website: https://hasdata.com/apis/google-images-api
- Changelog RSS feed: https://verifymcp.io/servers/com-hasdata-google-images/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hasdata-google-images/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-hasdata-google-images/mcp