Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Google AI Search MCP

NPM · GOOGLE-AI-SEARCH-MCP

Google AI search and documentation tools for MCP clients using Vertex AI or the Gemini API.

0 this week 44 Trust /100

Last scanned (7 minutes ago)

Scores higher than 27% of npm servers

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.6.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 24 of 63 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to shariqriazz/google-ai-search-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 66 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 12 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: unverified → pass ▲ functional
  • 11 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: pass → unverified ▼ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 17 Oct 2026 · Analysed npm/google-ai-search-mcp@1.1.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo shariqriazz/google-ai-search-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/shariqriazz/google-ai-search-mcp/.github/workflows/publish.yml@refs/heads/main
Rekor log index 2426931272
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:4dc66481540d5c7c53d31e9c15956853bbc347e2b720bff47c06089fc70861970e3683311ad87272b1d03a26639ca9ef0edf90b7bac73e4bd103af2b9

Background: How many MCP packages publish verified provenance →

Vulnerabilities 2 findings
ID CVE Severity Vector Fix available
GHSA-w48q-cv73-mx4w CVE-2025-66414 high yes
GHSA-73rr-hh4g-fpgx CVE-2026-24001 low yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 63 packages
Packages resolved 63
Deprecated 1
Stale 23
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the Google AI Search MCP server?

Google AI Search MCP runs locally as an npm package, launched with npx -y google-ai-search-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · google-ai-search-mcp

# add to Claude Code
claude mcp add shariqriazz-google-ai-search-mcp -- npx -y google-ai-search-mcp
Common questions

What is the Google AI Search MCP server?

Google AI Search MCP is listed in the public MCP registry as io.github.shariqriazz/google-ai-search-mcp. Google AI search and documentation tools for MCP clients using Vertex AI or the Gemini API. This page covers its npm package (google-ai-search-mcp).

Is the Google AI Search MCP server safe to use?

Google AI Search MCP scores 44 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 17 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.

Is the Google AI Search MCP server still maintained?

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

What licence is the Google AI Search MCP server under?

Google AI Search MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.