Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/serpbridge

NPM · @RENETURCIOS/SERPBRIDGE · 2 COMPONENTS

Google, Bing, DuckDuckGo and Google Maps search results, forwarded from the Litescrape API.

66 Trust /100

Last scanned (14 hours ago)

Scores higher than 38% of npm servers

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability52
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2158 tokens (~539/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 51

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@reneturcios/serpbridge@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~2,158 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
bing_search ~340

Get Bing web search results.

NameTypeReqDescription
cc––Case-insensitive two-letter country of origin. Format: US or GB. Cannot be combined with mkt.
devicestring–Selects desktop, tablet, or mobile result behavior.
enginestring–Selects the Bing web-search engine.
filters––Native Bing display or date filter expression. Maximum length: 8,192 characters. Control characters are rejected.
firstinteger–One-based native offset for organic results. Range: 1 through 9,007,199,254,740,991. Prefer litescrape_pagination.next when it is returned.
lat––Latitude from -90 through 90. May be supplied independently or with lon.
location––Named city-level origin used to localize the Bing request. Maximum length: 256 characters. Control characters are rejected.
lon––Longitude from -180 through 180. May be supplied independently or with lat.
mkt––Case-insensitive Bing language-country market token. Format: two-letter language and country, such as en-US. Cannot be combined with cc.
qstringyesBing search query after trimming. Accepted length: 1 through 2,048 characters. Control characters are rejected. Bing query syntax such as quoted phrases and exclusions remains available.
result_groupsarray–Return only these top-level result groups, e.g. ["organic_results", "knowledge_graph"]; omit for the complete response. search_metadata is always kept
safeSearchstring–Bing adult-content policy; values are case-insensitive.

No output schema declared.

No examples provided.

duckduckgo_search ~186

Get DuckDuckGo web search results.

NameTypeReqDescription
df––Date window: d, w, m, y, or YYYY-MM-DD..YYYY-MM-DD.
kl––DuckDuckGo region and language token, such as us-en.
minteger–Requested result count from 1 through 50; mutually exclusive with search_assist.
qstringyesRequired search text, up to 500 characters.
result_groupsarray–Return only these top-level result groups, e.g. ["organic_results", "knowledge_graph"]; omit for the complete response. search_metadata is always kept
safestring–DuckDuckGo safe-search level.
search_assistboolean–Enable DuckDuckGo query assistance; mutually exclusive with m.
startinteger–Result offset from 0 through 10,000.

No output schema declared.

No examples provided.

google_maps ~722

Search Google Maps places, or get one place by ID.

NameTypeReqDescription
data––A Google Maps protobuf parameter sequence for search filters or an exact place. Maximum length: 8,192 characters. Exact-place data requires type=place.
data_cid––A decimal Google CID used to resolve one exact place. Cannot be combined with place_id or exact-place data.
gl––Two-letter country code used for regional result localization. Examples: us, gb, ca, au
google_domain––Validated Google domain used for the request. Examples: google.com, google.co.uk, google.ca
hl––Language used for Google Maps labels and returned text. Examples: en, es, fr, de
lat––Latitude for a coordinate-based viewport. Must be supplied with lon and either z or m.
ll––A complete viewport containing latitude, longitude, and either zoom or radius. Format: @lat,lon,14z or @lat,lon,5000m
location––A named geographic location resolved by the API. Cannot be combined with ll or lat/lon. Requires z or m.
lon––Longitude for a coordinate-based viewport. Must be supplied with lat and either z or m.
m––Search radius in meters for location or lat/lon geography. Accepted range: 1 through 15,028,132. Cannot be combined with z.
max_price––Maximum price level for returned places. Must be non-negative and cannot be lower than min_price.
min_price––Minimum price level for returned places. Must be non-negative and cannot exceed max_price.
min_rating––Preferred minimum Google rating. Google treats this as a relevance preference.
nearby––Uses the supplied geography as a nearby-search scope. Requires ll, location, or a lat/lon pair.
open_at_hour––Filters for places open at a specific hour using 24-hour time. Accepted range: 0 through 23. Requires open_on_day.
open_on_day––Filters for places open on a specific day.
open_state––Filters by the current open state. Cannot be combined with open_on_day or open_at_hour.
place_id––A Google place identifier used to resolve one exact place or request live foot traffic. Cannot be combined with data_cid or exact-place data on the primary Maps endpoint. It is the only required par…
q––The business, category, address, or natural-language query to search. Required when type is search. Examples: coffee shops in Austin, dentist near Denver
result_groupsarray–Return only these top-level result groups, e.g. ["organic_results", "knowledge_graph"]; omit for the complete response. search_metadata is always kept
start––Native Maps result offset: 0, 20, 40, and so on. Each request returns up to 20 places and each successful request costs one credit. Use pagination.next when it is present instead of constructing the…
type––Chooses a result search or an exact place response. Required for query and filter searches. Use place when sending an exact-place data sequence.
z––Google Maps zoom level for location or lat/lon geography. Accepted range: 3 through 30. Cannot be combined with m.

No output schema declared.

No examples provided.

google_search ~910

Get Google search results, including the AI Overview and People also ask.

NameTypeReqDescription
as_dt––Includes or excludes as_sitesearch. Requires as_sitesearch.
as_epq––Exact phrase query.
as_eq––Excluded phrase query.
as_lq––Require results that link to this URL.
as_nhi––Inclusive range upper bound. Requires as_nlo.
as_nlo––Inclusive range lower bound. Requires as_nhi.
as_oq––Any-of search terms.
as_q––Additional all-of search terms.
as_qdr––Quick range d, w, m, or y with an optional positive count.
as_rq––Find pages related to this URL.
as_sitesearch––Site hostname to include or exclude.
color_scheme––Google result color presentation.
cr––One or more countryXX restrictions joined with |.
devicestring–Request device profile and radius bound.
fast_modeboolean–Return organic results only, skipping AI Overview and all other result groups. Keeps search metadata and parameters. Omits cross-module position_absolute.
filter––Google similar-result filtering control.
gl––Lowercase two-letter country localization code.
google_domainstring–Results use google.com. Use gl, hl, cr, lr or geography for localization.
gs_lp––Google gs_lp value associated with an autocomplete selection.
hlstring–Google interface and result language code.
ibp––Google layout or expansion control.
kgmid––Google Knowledge Graph machine ID, such as /m/0k8z.
lat––Latitude from -90 through 90. Requires lon and conflicts with location and uule.
location––Human-readable city-level location encoded to UULE by Litescrape. Conflicts with uule and lat/lon.
lon––Longitude from -180 through 180. Requires lat and conflicts with location and uule.
lr––One or more lang_xx restrictions joined with |.
lsig––Opaque Knowledge Graph or local-pack signature.
ludocid––Google local CID used to search for one entity.
nfpr––Google auto-correction control.
num––Best-effort first-page result count, 1 to 10.
oq––Original query associated with an autocomplete selection.
page_token––Opaque token from pagination.next_page_token. Send it alone to fetch the next page with the original search parameters. Prefer page_token to repeating the same search with start=10, start=20, or ano…
peek_pws––Google personalization peek flag, forwarded unchanged.
pws––Google personalization control; 0 asks for non-personalized results.
q––Google Search query, up to 2,048 characters. Required unless ludocid, kgmid, or page_token is supplied.
radius––Decimal search-bias radius in meters. Requires location or lat/lon. Desktop: 1–199; tablet/mobile: 1–1,000.
result_groupsarray–Return only these top-level result groups, e.g. ["organic_results", "knowledge_graph"]; omit for the complete response. search_metadata is always kept
safe––Google adult-content filtering.
sclient––Google client identifier such as gws-wiz-serp.
si––Opaque cached Google search context.
startinteger–Non-negative Google result offset. Prefer page_token to repeating the same search with start=10, start=20, or another offset.
tbm––Google vertical: lcl, vid, nws, shop, or pts. For image searches, use /api/google/images.
tbs––Google native date or search filter string.
uds––Opaque Google filter token.
uule––Pre-encoded Google location value. Conflicts with location and lat/lon.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/serpbridge MCP server?

io.github.CloudCorpRecords/serpbridge runs locally as an npm package, launched with npx -y @reneturcios/serpbridge mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @reneturcios/serpbridge

# add to Claude Code
claude mcp add cloudcorprecords-serpbridge -- npx -y @reneturcios/serpbridge mcp
Common questions

What is the io.github.CloudCorpRecords/serpbridge MCP server?

io.github.CloudCorpRecords/serpbridge is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/serpbridge. Google, Bing, DuckDuckGo and Google Maps search results, forwarded from the Litescrape API. This page covers its npm package (@reneturcios/serpbridge).

Is the io.github.CloudCorpRecords/serpbridge MCP server safe to use?

io.github.CloudCorpRecords/serpbridge scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.CloudCorpRecords/serpbridge MCP server expose?

io.github.CloudCorpRecords/serpbridge exposes 4 tools: google_search, bing_search, duckduckgo_search, google_maps. Their descriptions and schemas cost roughly 2,158 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/serpbridge MCP server still maintained?

io.github.CloudCorpRecords/serpbridge is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.CloudCorpRecords/serpbridge MCP server under?

io.github.CloudCorpRecords/serpbridge declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.CloudCorpRecords/serpbridge MCP server?

VerifyMCP ran 15 checks on io.github.CloudCorpRecords/serpbridge, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/serpbridge: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.