
serpbridge
io.github.CloudCorpRecords/serpbridge
Google, Bing, DuckDuckGo and Google Maps search results, forwarded from the Litescrape API.
Documentation
serpbridge
Four search engines, one small bridge. serpbridge is a local forwarding client for the hosted Litescrape MCP service: it answers tools/list on your own machine from the captured tool definitions and forwards every search to Litescrape, returning the results exactly as the service sends them back.
The built surface covers Google Search (including the AI Overview and People also ask), Bing web search, DuckDuckGo web search, and Google Maps place search. Nothing is cached, stored or computed locally — the package is a pipe, not an index.
This is a labelled subset rebuild: the upstream capture enumerates six tools, and four are built here. The remaining two, find_tools and call_tool, form a meta-dispatch pair onto a wider Litescrape catalogue that the capture does not enumerate, so they are omitted — not registered, not served in tools/list, and not available on the CLI.
The tools
google_search— Google search results, including the AI Overview and People also ask. Every parameter is optional in the captured schema;qis the query, and apage_tokenfrom a previous response fetches the next page. Supports location biasing (location,uule,lat/lon,radius), verticals (tbm), advanced-search fields (as_*) and result-group filtering.bing_search— Bing web search results.qis required. Supports market and country selection (mkt,cc), safe-search levels, native filters and paging viafirst.duckduckgo_search— DuckDuckGo web search results.qis required. Supports region/language tokens (kl), safe-search levels, date windows (df) and result counts.google_maps— Search Google Maps places, or fetch one place by ID. No parameter is required in the captured schema; a search takesqwith geography (ll,location, orlat/lonpluszorm), and an exact place can be resolved viaplace_idordata_cidwithtype: "place".
Install and run
As an MCP server via npm:
npx -y @reneturcios/serpbridge mcp
MCP client configuration:
{
"mcpServers": {
"serpbridge": {
"command": "npx",
"args": ["-y", "@reneturcios/serpbridge", "mcp"]
}
}
}
As a container:
docker run -i ghcr.io/cloudcorprecords/serpbridge
docker run --rm ghcr.io/cloudcorprecords/serpbridge bing_search '{"q":"openai"}'
CLI
One binary serves both the command line and the MCP server. Each tool is a subcommand taking a single JSON string with that tool's arguments:
serpbridge google_search '{"q":"coffee shops in Austin"}'
serpbridge duckduckgo_search '{"q":"privacy tools"}'
serpbridge google_maps '{"q":"dentist near Denver","type":"search"}'
serpbridge --version
Exit codes: 0 when the forwarded call succeeds, 1 when the upstream result is an error, and 2 for usage problems such as an unknown subcommand or a malformed JSON argument.
Configuration
LITESCRAPE_MCP_URL— Overrides the upstream endpoint. The default is the pinned hosted endpoint,https://mcp.litescrape.com/mcp. (The override variable is a reconstruction added by this rebuild.)LITESCRAPE_API_KEY— When set, its value is sent to the upstream on every request as anAuthorization: Bearer <value>header; the registry record pins theAuthorizationheader name, and without a key the service's free daily allowance applies. When it is not set, no key header is sent. (The env forwarding is a reconstruction added by this rebuild; the tool surface was captured keyless.)
Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with serpbridge error:.
How forwarding works
The first forwarded call opens a session: an initialize request (protocol version 2025-03-26), followed by a notifications/initialized notification, then the tools/call itself. If the service answers the initialize request with an Mcp-Session-Id header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any isError flag and any extra fields the service includes.
Development
npm install
npm run build # tsc -> dist/ (dist/cli.js is the bin)
npm test # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev # run the CLI from source
The test suite checks the served tool list against the captured surface, asserts the omitted find_tools and call_tool tools are absent at the registry, MCP and CLI levels, exercises the session handshake and its reuse, covers both branches of the Authorization header (key set and unset), and verifies that arguments go upstream untouched and results come back untouched.
License
MIT — see LICENSE. Copyright (c) 2026 Rene Turcios.
@reneturcios/serpbridgenpm install @reneturcios/serpbridgeghcr.io/cloudcorprecords/serpbridge:0.1.0docker pull ghcr.io/cloudcorprecords/serpbridge:0.1.0:undefinedRelated Servers
io.github.CloudCorpRecords/abandoncheck
Judge whether a dependency is maintained, from factual signals: releases, commits, archival.
io.github.CloudCorpRecords/actionbridge
Zapier exposed actions as MCP tools via a generic action runner.
io.github.CloudCorpRecords/actionpin
GitHub Actions supply-chain hardener: audit workflows for unpinned actions and build a SHA pin plan.