SERPdive Web Search
NPM · SERPDIVE-MCP · 2 COMPONENTS · SCANNED SEP 20
AI-agent web search, answer-ready content. Beats Tavily: 60.7% of quality duels, 20.2% fewer tokens.
Available components
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 56 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 358 tokens (~358/item across 1 items; 1 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the SERPdive Web Search MCP server?
SERPdive Web Search runs locally as an npm package, launched with npx -y serpdive-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 · serpdive-mcp
claude mcp add com-serpdive-serpdive-mcp -- npx -y serpdive-mcp
{
"mcpServers": {
"com-serpdive-serpdive-mcp": {
"command": "npx",
"args": [
"-y",
"serpdive-mcp"
]
}
}
} {
"servers": {
"com-serpdive-serpdive-mcp": {
"command": "npx",
"args": [
"-y",
"serpdive-mcp"
]
}
}
} codex mcp add com-serpdive-serpdive-mcp -- npx -y serpdive-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-serpdive-serpdive-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"serpdive-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-serpdive-serpdive-mcp --command npx --arg -y --arg serpdive-mcp
mcp_servers:
com-serpdive-serpdive-mcp:
command: "npx"
args: ["-y", "serpdive-mcp"] {
"McpServers": {
"com-serpdive-serpdive-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"serpdive-mcp"
]
}
}
} assistant mcp add com-serpdive-serpdive-mcp -t stdio -c npx -a -y serpdive-mcp
{
"mcpServers": {
"com-serpdive-serpdive-mcp": {
"command": "npx",
"args": [
"-y",
"serpdive-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/serpdive-mcp@0.1.4
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 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
serpdive_search SERPdive Web Search ~304
Search the live web and get back answer-ready page content, not a list of links. Each result carries the actual text of the page (url, title, date, content), already extracted, cleaned and trimmed for LLM use, so facts can be quoted and cited straight from the response. Use it for anything that needs current or post-training information: news, prices, releases, docs, sports, niche facts. Write the query the way a person would type it, in any language: localization is automatic. The 'mako' model (default) returns the fact-carrying sentences of each page, fast and concise, right for most questions. The 'moby' model returns the full readable text of each page: use it for deep research or when complete context matters. Set answer=true to also get a direct answer synthesized from the sources.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | boolean | – | When true, the response also carries an 'answer' field: a direct answer to the query synthesized from the sources. |
| max_results | integer | – | Maximum number of results to return (1 to 10). Omit to let the engine pick its calibrated mix. |
| model | string | – | 'mako' (default): the key sentences of each page, concise and fast. 'moby': the full readable text of each page, for deep research. |
| query | string | yes | The search query, in any language, phrased like a real web search. |
No output schema declared.
No examples provided.
What is the SERPdive Web Search MCP server?
SERPdive Web Search is an MCP server listed in the public MCP registry as com.serpdive/serpdive-mcp. AI-agent web search, answer-ready content. Beats Tavily: 60.7% of quality duels, 20.2% fewer tokens. This page covers its npm package (serpdive-mcp).
Is the SERPdive Web Search MCP server safe to use?
SERPdive Web Search scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 SERPdive Web Search MCP server expose?
SERPdive Web Search exposes 1 tool: serpdive_search. Their descriptions and schemas cost roughly 304 tokens of context every time the server is loaded.
Is the SERPdive Web Search MCP server still maintained?
SERPdive Web Search is still listed as active in the MCP registry. We last reached this channel on 20 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 SERPdive Web Search MCP server under?
SERPdive Web Search declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.