mcp-search-suggest
search-suggest: search-box autocomplete suggestions from Google, Bing, DuckDuckGo, YouTube and Amazon. Live keyless proxy.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/pipeworx-io--mcp-search-suggest)HTML
<a href="/listings/pipeworx-io--mcp-search-suggest"><img src="/api/listings/pipeworx-io--mcp-search-suggest/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"search-suggest": {
"url": "https://gateway.pipeworx.io/search-suggest/mcp"
}
}
}What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/search-suggest/mcp` returns the tools in the table above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`, `discover_tools`, `search_within`, `remember`/`recall` and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's `initialize` response states its exact scope, and is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via `ask_pipeworx`, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 2034+ data sources. The only difference is which pack's tools are listed **directly**; `ask_pipeworx` reaches all of them from either one.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 131 lines
- # @pipeworx/search-suggest
- Search-box autocomplete suggestions for a partial query from Google, Bing, DuckDuckGo, YouTube and Amazon. Live and keyless.
- Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2034+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
- ## Tools
- - `search_suggestions(query, engine?, lang?, country?)` — the ordered suggestions an engine's search box offers, with the engine, language and country used.
- ## Auth
- Keyless.
- ## Data sources
- - Google, Search autocomplete (also used for YouTube).
- - Microsoft, Bing autocomplete.
- - DuckDuckGo, search autocomplete.
- - Amazon, shopping search suggestions (markets: us, gb, de, fr, ca, jp).
- Gotchas: suggestions are personalised by region, so pass `country`; Google and YouTube lean toward the location of the server when the engine cannot infer one. DuckDuckGo ignores country. A prefix with no suggestions is reported as an error rather than an empty list.
- ## Quick Start
- Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
- ```json
- {
- "mcpServers": {
- "search-suggest": {
- "url": "https://gateway.pipeworx.io/search-suggest/mcp"
- }
- }
- }
- ```
- ### What this endpoint actually serves
- `tools/list` at `https://gateway.pipeworx.io/search-suggest/mcp` returns the tools in the table
- above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
- `discover_tools`, `search_within`, `remember`/`recall` and the rest of the
- gateway-wide set. So the tool count you see is larger than this table: a
- single-pack endpoint currently lists roughly 30 shared tools alongside the
- pack's own. The connection's `initialize` response states its exact scope, and
- is the authoritative answer for a given day.
- This is deliberate, not multiplexing by accident. The meta-tools are what let a
- scoped connection answer a question this pack does not cover — via
- `ask_pipeworx`, which routes across the whole catalog — without you adding a
- second MCP server. There is currently no way to mount a pack endpoint without
- them; if the extra schemas cost you more context than the routing is worth,
- connect to the full gateway once rather than to several pack endpoints.
- Or connect to the full Pipeworx gateway to get every pack's tools listed
- directly, instead of just this one's:
- ```json
- {
- "mcpServers": {
- "pipeworx": {
- "url": "https://gateway.pipeworx.io/mcp"
- }
- }
- }
- ```
- Both URLs reach the same gateway and the same 2034+ data sources. The
- only difference is which pack's tools are listed **directly**; `ask_pipeworx`
- reaches all of them from either one.
- ## No MCP client? Call it over HTTP
- ```bash
- curl -X POST https://gateway.pipeworx.io/v1/tools/search_suggestions \
- -H 'Content-Type: application/json' \
- -d '{"query":"how to learn","engine":"google","lang":"en","country":"us"}'
- ```
- No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/search_suggestions`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
- ## Run it from npm
- `@pipeworx/mcp-search-suggest` is a local stdio bridge to the Pipeworx gateway: your MCP client
- starts it with `npx`, and it forwards every call to the same
- `https://gateway.pipeworx.io/search-suggest/mcp` endpoint shown above. It needs network access;
- there is no offline mode.
- ```json
- {
- "mcpServers": {
- "search-suggest": {
- "command": "npx",
- "args": ["-y", "@pipeworx/mcp-search-suggest"]
- }
- }
- }
- ```
- Without a key it calls anonymously, capped at 50 calls a day. A free account
- raises that to 200 a day: get a key at https://pipeworx.io/signup and add
- `"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
- The key is sent as a Bearer token, the same way a hosted connection sends it,
- so calls are metered and billed exactly as they are there.
- It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
- also list `ask_pipeworx` and the other gateway-wide tools.
- Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
- default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
- your Node version's documentation.
- ## Using with ask_pipeworx
- Instead of calling tools directly, you can ask questions in plain English —
- this works on the pack endpoint above as well as on the full gateway:
- ```
- ask_pipeworx({ question: "your question about Search Suggest data" })
- ```
- The gateway picks the right tool and fills the arguments automatically.
- ## More
- - [Docs and guides](https://pipeworx.io/docs)
- - [pipeworx.io](https://pipeworx.io)
- ## License
- MIT
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.