Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/HasData/google-search-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/hasdata/google-search-mcp/google-search)<a href="https://agentmods.dev/mcp/hasdata/google-search-mcp/google-search"><img src="https://agentmods.dev/badge/mcp/hasdata/google-search-mcp/google-search/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/hasdata/google-search-mcp/google-search"><img src="https://agentmods.dev/badge/mcp/hasdata/google-search-mcp/google-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
google-search scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"google-search": {
"command": "npx",
"args": [
"-y",
"@hasdata/google-search-mcp"
],
"env": {
"HASDATA_API_KEY": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 12 lines scan A 904dc3131d0e
google-search is an MCP server published in the GitHub repository HasData/google-search-mcp (16 stars, last pushed 13d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
scavio
MCP server "scavio", hosted remotely at mcp.scavio.dev, as configured in scavio-ai/scavio-mcp.
scavio-mcp
AI-agent search API: Google, YouTube, Amazon, Reddit, TikTok, TikTok Shop, Instagram, X, LinkedIn. Runs locally from the @scavio/mcp-server npm package. Needs 1 environment variable to run.
x-use
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no API keys required. Runs locally from the x-use-mcp Python package. Needs 3 environment variables to run.
seo
Spot keyword demand rising or fading. Trend volume and growth signals. Free key at trendsmcp.ai. Remote server at seo.api.trendsmcp.ai.
sportscore-mcp
Live scores, standings, top scorers, brackets for football, basketball, cricket, tennis. Free API. Runs locally from the sportscore-mcp npm package. Needs 2 environment variables to run.
chronicle-mcp
Local MCP server to sync, clean, and index AI chat logs locally. Saves up to 40% context tokens. Runs locally from the chronicle-mcp-server Python package.