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.

SearchHub

NPM · SEARCHHUB · SCANNED SEP 25

Aggregate Serper, Tavily, Exa and AnySearch behind one MCP-ready API with key rotation and quotas.

Available components

70 Trust /100
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
  • 42 of 142 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 264 tokens (~88/item across 3 items; 3 tools + 0 resources), lean.Pass
  • 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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.

Install

How do I install the SearchHub MCP server?

SearchHub runs locally as an npm package, launched with npx -y searchhub. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · searchhub

# add to Claude Code
claude mcp add woodcoal-searchhub -- npx -y searchhub
// .cursor/mcp.json
{
  "mcpServers": {
    "woodcoal-searchhub": {
      "command": "npx",
      "args": [
        "-y",
        "searchhub"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "woodcoal-searchhub": {
      "command": "npx",
      "args": [
        "-y",
        "searchhub"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add woodcoal-searchhub -- npx -y searchhub
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "woodcoal-searchhub": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "searchhub"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add woodcoal-searchhub --command npx --arg -y --arg searchhub
# ~/.hermes/config.yaml
mcp_servers:
  woodcoal-searchhub:
    command: "npx"
    args: ["-y", "searchhub"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "woodcoal-searchhub": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "searchhub"
      ]
    }
  }
}
# add to Vellum
assistant mcp add woodcoal-searchhub -t stdio -c npx -a -y searchhub
// mcp.json
{
  "mcpServers": {
    "woodcoal-searchhub": {
      "command": "npx",
      "args": [
        "-y",
        "searchhub"
      ]
    }
  }
}
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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Sept 26 70

    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 25 Sept 2026 · Analysed npm/searchhub@0.1.10

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 142 packages
Packages resolved 142
Stale 42
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~264 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
searchhub_providers ~38

列出内置供应商及其支持的能力(时间范围、站内限定、地域、语言、翻页等)。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

searchhub_search ~186

通过 SearchHub 聚合网关执行网络搜索,自动在多家供应商(Serper/Tavily/Exa/AnySearch)之间轮换密钥与容灾切换。返回标题、链接、摘要等结构化结果。

NameTypeReqDescription
countrystring–国家/地区 ISO 码,如 us、cn
langstring–语言,如 en、zh
pageinteger–页码,从 1 开始(部分供应商不支持翻页)
pageSizeinteger–返回条数,默认 10
providerIdstring–强制指定供应商,留空按优先级自动选择
qstringyes检索词
sitestring–站内限定,如 github.com
timeRangestring–时间范围

No output schema declared.

No examples provided.

searchhub_status ~40

查看各搜索供应商的启用状态、熔断状态、可用/冷却/隔离的密钥数量与调用统计。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the SearchHub MCP server?

SearchHub is an MCP server listed in the public MCP registry as io.github.woodcoal/searchhub. Aggregate Serper, Tavily, Exa and AnySearch behind one MCP-ready API with key rotation and quotas. This page covers its npm package (searchhub).

Is the SearchHub MCP server safe to use?

SearchHub scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 SearchHub MCP server expose?

SearchHub exposes 3 tools: searchhub_search, searchhub_status, searchhub_providers. Their descriptions and schemas cost roughly 264 tokens of context every time the server is loaded.

Is the SearchHub MCP server still maintained?

SearchHub is still listed as active in the MCP registry. We last reached this channel on 25 September 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 SearchHub MCP server under?

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