Show HN: SerpApi MCP Server

SerpApi just rolled out a new Model Context Protocol (MCP) server that plugs into AI assistants like Claude and funnels in live search results from Google, Bing, DuckDuckGo, YouTube, eBay—you name it. It even pulls weather and stock info, and you can run it hosted at mcp.serpapi.com or self-host it from GitHub. On paper, it’s a one-stop search pipe for your AI. In the comments? Oh, it’s a drama buffet.

The loudest cheer came from icyfox, who spotlighted SerpApi’s headline-grabbing perk: a “U.S. Legal Shield” that claims to defend customers’ rights to crawl public search data—yes, even assuming scraping liability. Some users called it a bold, First Amendment flex. Others rolled their eyes: is it a real shield or just shiny marketing armor? Cue popcorn.

Then came the backlash over how you connect it. The docs recommend putting your API key in the URL path (they also support Authorization headers), but block_dagger wasn’t having it, calling secrets-in-URLs a nightmare for logs and tooling. The thread lit up with devs joking about “leaving your keys on the porch,” memes about “passwords in the link,” and pleas for env‑var‑friendly setups.

So where did everyone land? Fans love the plug-and-play, multi-engine search for AI workflows and the auto-formatted results. Skeptics warn that convenience shouldn’t trump security—and they want headers by default and cleaner secret management. Between the legal-bravado chatter and the key‑handling roast, this launch delivered exactly what the internet ordered: cool tech with a side of spicy debate.