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.yokingma/one-search-mcp

NPM · ONE-SEARCH-MCP · SCANNED SEP 20

Web search, URL discovery, scraping & extraction with agent-browser and search providers

Available components

0 this week 80 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
  • 64 of 219 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 425 tokens (~106/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 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 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
Install

How do I install the io.github.yokingma/one-search-mcp server?

io.github.yokingma/one-search-mcp runs locally as an npm package, launched with npx -y one-search-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 · one-search-mcp

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

  • 20 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 19 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail functional
  • 18 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 16 Sept 26 +1
    • Security disclosure: unverified → fail functional
  • 14 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 13 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 12 Sept 26 0
    • Stability: 0.97 → pass security
  • 11 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.

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 20 Sept 2026 · Analysed npm/one-search-mcp@1.2.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 219 packages
Packages resolved 219
Deprecated 1
Stale 64
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~425 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
one_extract ~47

Fetch and preprocess page content from one or more URLs. Returns cleaned text blocks that can be passed to downstream tools or models.

NameTypeReqDescription
urlsarrayyesList of URLs to extract information from

No output schema declared.

No examples provided.

one_map ~82

Discover URLs from a starting point by loading a page in the browser and extracting links from its HTML.

NameTypeReqDescription
includeSubdomainsbooleanInclude URLs from subdomains in results
limitnumberMaximum number of URLs to return
searchstringOptional search term to filter URLs
urlstringyesStarting URL for URL discovery

No output schema declared.

No examples provided.

one_scrape ~191

Scrape a single webpage and return markdown, HTML, links, or a screenshot. Supports navigation timeout, TLS verification control, full-page screenshots, bounded pre-scrape actions, and advanced executeJavascript only when allowExecuteJavascript is true.

NameTypeReqDescription
actionsarrayList of pre-scrape actions to run before content capture. Standard actions are bounded; executeJavascript requires allowExecuteJavascript: true.
allowExecuteJavascriptbooleanMust be true when actions contain executeJavascript. Use only for advanced page-side scripting.
formatsarrayContent formats to extract (default: ['markdown'])
skipTlsVerificationbooleanSkip TLS certificate verification
timeoutnumberMaximum time in milliseconds to wait for the page to load
urlstringyesThe URL to scrape
waitFornumberTime in milliseconds to wait for dynamic content to load

No output schema declared.

No examples provided.

one_search ~105

Search and retrieve content from web pages. Returns SERP results by default (url, title, description).

NameTypeReqDescription
categoriesstringCategories to search for (default: general)
languagestringLanguage code for search results (default: auto)
limitnumberMaximum number of results to return (default: 10)
querystringyesSearch query string
timeRangestringTime range for search results (default: all)

No output schema declared.

No examples provided.

Common questions

What is the io.github.yokingma/one-search-mcp server?

io.github.yokingma/one-search-mcp is listed in the public MCP registry as io.github.yokingma/one-search-mcp. Web search, URL discovery, scraping & extraction with agent-browser and search providers. This page covers its npm package (one-search-mcp).

Is the io.github.yokingma/one-search-mcp server safe to use?

io.github.yokingma/one-search-mcp scores 80 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 io.github.yokingma/one-search-mcp server expose?

io.github.yokingma/one-search-mcp exposes 4 tools: one_search, one_scrape, one_map, one_extract. Their descriptions and schemas cost roughly 425 tokens of context every time the server is loaded.

Is the io.github.yokingma/one-search-mcp server still maintained?

io.github.yokingma/one-search-mcp 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 io.github.yokingma/one-search-mcp server under?

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