GSearch - Free Google Search MCP
v1.0.2Search the web with Google Search grounding. Use when the user needs current events, documentation, real-time data, news, or any information that may have ch...
⭐ 0· 94·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name, description, and runtime instructions all describe a Google-search MCP implemented as a CLI tool (gsearch-mcp). Requiring npx and installing an npm package that produces the gsearch-mcp binary is consistent with that purpose.
Instruction Scope
SKILL.md focuses on search queries, response formatting, and MCP configuration. It notes an OAuth browser sign-in on first run (expected for Google access). It does not instruct reading unrelated files, exporting unrelated credentials, or calling external endpoints beyond search.
Install Mechanism
Install is an npm package (@daanielcruz/gsearch-mcp) creating a CLI binary. Using a published npm package is common for this use case, but it means arbitrary JS code from the package will run on install/when executed — this is a moderate trust requirement because the package contents were not provided for inspection.
Credentials
The skill declares no environment variables or unrelated credentials. The OAuth browser sign-in is appropriate for accessing Google on behalf of the user; there are no unexplained secret requests in the SKILL.md.
Persistence & Privilege
always is false and the skill is user-invocable. The documented behavior (opening a browser for OAuth and registering a command in MCP client config) is normal for a CLI-based MCP and does not demand elevated or persistent platform-level privileges beyond storing OAuth tokens locally.
Assessment
This skill appears to do what it says: provide Google-backed web search via a CLI MCP. Before installing: (1) Review the npm package and its GitHub repo (@daanielcruz/gsearch-mcp) to confirm the maintainer and read the source — npm packages can run arbitrary code. (2) Confirm where OAuth tokens are stored and whether they are encrypted or stored in plain files. (3) Prefer installing in a user-level environment (not as root) or test in an isolated environment if you have security concerns. (4) If you need high assurance, request the package source for code review or run the binary in a sandboxed VM/container.Like a lobster shell, security has layers — review code before you run it.
latestvk9752dzagvg9rp6rxfbk86xpy983smd3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔍 Clawdis
OSmacOS · Linux · Windows
Binsnpx
Install
Node
Bins: gsearch-mcp
npm i -g @daanielcruz/gsearch-mcp