noapi-google-search-mcp

Provides an MCP server exposing ~38 tools for local LLMs to perform Google web/search-like discovery, page visiting/extraction, and many other capabilities (feeds subscriptions with SQLite+FTS, YouTube transcription/RAG and clip extraction, local document OCR/extraction, image-related tools, email via IMAP, and utilities like QR/code/URL shortener/wiki/S3 upload). Designed to run without API keys by driving headless Chromium/Playwright and local ML tools.

Evaluated Mar 30, 2026 (22d ago)
Repo ↗ DevTools mcp python headless-browsing web-scraping playwright chromium local-llm feeds youtube-transcription ocr whisper sqlite fts5 ffmpeg vision s3
⚙ Agent Friendliness
60
/ 100
Can an agent use this?
🔒 Security
42
/ 100
Is it safe for agents?
⚡ Reliability
38
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
68
Documentation
55
Error Messages
--
Auth Simplicity
80
Rate Limits
70

🔒 Security

TLS Enforcement
60
Auth Strength
45
Scope Granularity
30
Dep. Hygiene
45
Secret Handling
30

Security posture is not fully evidenced in provided content. Likely no auth for web fetching (headless browsing), with credentials potentially supplied for IMAP/S3. README claims stealth patches and CAPTCHA-solving for Google anti-bot detection, which can increase legal/ToS and operational risk. TLS enforcement, logging/telemetry, input sanitization, and secret handling practices are not documented here, so scores reflect uncertainty. Headless browsing increases exposure to untrusted web content if not sandboxed.

⚡ Reliability

Uptime/SLA
0
Version Stability
55
Breaking Changes
50
Error Recovery
45
AF Security Reliability

Best When

You want a local-first assistant that can browse/ingest content for research or knowledge capture on your own machine, and you can tolerate occasional breakage due to upstream site changes.

Avoid When

You need a stable, documented, contractual API for Google-like data access; you must minimize legal/ToS risk; or you cannot review/contain the headless browser and data storage behaviors.

Use Cases

  • • Enable an on-prem/local assistant to browse and search the web (Google-like results) without API keys
  • • Create a searchable local archive of subscribed feeds (news/Reddit/HN/GitHub/arXiv/YouTube/etc.)
  • • Perform local OCR and document text extraction for downstream Q&A
  • • Transcribe and search YouTube content locally and extract relevant video clips based on transcript context
  • • Let an LLM understand and extract text from webpages/images and process local media (via OCR/Whisper/FFmpeg)
  • • Upload files to S3-compatible storage (MinIO/AWS S3/R2/etc.) using the tool interface

Not For

  • • Production-grade compliance requirements for automated access to third-party websites (headless browsing/CAPTCHA-solving risk)
  • • Environments that forbid circumvention/bot-detection interaction or require explicit vendor API use
  • • Security-sensitive deployments without reviewing data handling, logging, and transport controls in the code
  • • High-reliability automated pipelines without monitoring (scraping/browsing can break when site layouts change)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: None advertised for Google/web tools (operates via local headless browsing) IMAP credentials for fetch_emails (per README example) S3-compatible credentials for upload_to_s3 (implied by tool)
OAuth: No Scopes: No

No API keys are advertised for the main Google/search features. However, IMAP and S3 upload capabilities imply users must provide credentials to the server configuration/tool calls.

Pricing

Free tier: No
Requires CC: No

Monetization for usage is not described; costs are primarily local infrastructure and model/compute requirements.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • ⚠ Web automation/scraping can break when Google page structures or bot detection changes.
  • ⚠ CAPTCHA-solving is attempted; results are best-effort and may fail depending on challenge types and upstream defenses.
  • ⚠ Rate limiting and dynamic content can lead to timeouts unless the agent handles backoff.
  • ⚠ Some tools have significant runtime (headless Chromium, transcription, OCR) and may need timeouts/queueing.
  • ⚠ Upstream content variability (feeds/transcripts/video pages) can yield inconsistent schemas/fields unless the agent robustly validates outputs.

Alternatives

Use Google CSE/official APIs (when allowed) with an API-key-based MCP server Use Brave/Perplexity/other providers that offer API access with clear rate limits Use generic web search via other stable APIs or open search engines Use a dedicated browser automation service with explicit policies rather than CAPTCHA-solving

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for noapi-google-search-mcp.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo
API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-30.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
♥
Community Powered