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.lennney/agent-search-mcp

NPM · AGENT-SEARCH-MCP · SCANNED SEP 20

Free-first Chinese and English web search MCP using zero-key sources and inspectable evidence.

Available components

0 this week 77 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
  • 38 of 130 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency48
  • 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 (Apache-2.0).Pass
  • Actively maintained (last published 39 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability45
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1236 tokens (~123/item across 10 items; 7 tools + 3 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 Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% of tool parameters carry a description.Partial
  • Structured output schemas are declared (43% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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.lennney/agent-search-mcp server?

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

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

  • 19 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.

  • 18 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 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.

  • 14 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.

  • 12 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.

  • 11 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
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/agent-search-mcp@3.2.1

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 130 packages
Packages resolved 130
Deprecated 1
Stale 38
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~1,165 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
fetch_csdn_article ~84

Fetch content from a CSDN blog article. Best for: Chinese developer blog content on CSDN. Not recommended for: Other Chinese sites — use free_extract instead. @readOnly true @idempotent true — makes outbound HTTP requests to the CSDN article URL.

NameTypeReqDescription
urlstringyesHTTPS article URL on blog.csdn.net

No output schema declared.

No examples provided.

fetch_github_readme ~85

Fetch README content from a GitHub repository. Best for: Getting project documentation quickly. Not recommended for: Non-GitHub URLs — use free_extract instead. @readOnly true @idempotent true — makes outbound HTTP requests to raw.githubusercontent.com.

NameTypeReqDescription
urlstringyesGitHub repository URL (e.g., https://github.com/owner/repo)

No output schema declared.

No examples provided.

fetch_juejin_article ~78

Fetch content from a Juejin article. Best for: Chinese developer articles on Juejin. Not recommended for: Non-Juejin content — use free_extract instead. @readOnly true @idempotent true — makes outbound HTTP requests to juejin.cn API.

NameTypeReqDescription
urlstringyesJuejin article URL

No output schema declared.

No examples provided.

free_extract ~198

Extract one selected URL into clean Markdown. Use after search when snippets are insufficient, or for a URL supplied by the user. It fetches one page; it does not search or bulk-extract URLs. Behavior: Makes an outbound HTTP request to Jina Reader (r.jina.ai) which fetches and converts the page to markdown. Has SSRF protection: blocks private IPs, localhost, and metadata endpoints. 10s request timeout — pages exceeding this will fail with a timeout error. HTTP errors (4xx, 5xx) are returned as structured error responses.

NameTypeReqDescription
max_lengthnumberMaximum characters to return (default: 5000). Content beyond this limit is truncated. Increase for long articles, decrease for quick snippets.
urlstringyesURL to extract content from. Supports any public web page URL (http/https). For best results, use a complete URL including the protocol (https://).

No output schema declared.

No examples provided.

free_search ~225

Quick public-web search for current facts and discovery. Use free_search_advanced for verification or domain filters. Use free_extract for one selected URL. Returns compact multi-source evidence with confidence, relevance, source_count, stop_reason, evidence_budget, and partialFailures. Provider families are counted once even when several adapters use the same upstream. Optional API providers run only when credentials and policy allow. @readOnly true @idempotent true — makes outbound HTTP requests to configured search engines. Injection detection and SSRF protection active.

NameTypeReqDescription
enginesarraySearch engines to use (default: duckduckgo + sogou). Free engines work without API keys. Optional API engines require their corresponding environment-variable credentials. For Chinese results, includ…
limitintegerNumber of results to return (1-50). Default 10. Higher values increase token usage.
querystringyesSearch query string. Use natural language (e.g., "latest AI news 2026"). For Chinese coverage, include Sogou or Baidu in engines.
NameTypeReqDescription
cache_hitboolean
detected_languagestring
enginesarrayyes
metaobjectyes
partialFailuresarray
querystringyes
rate_limitsobject
resultsarrayyes
security_notestringyes

No examples provided.

free_search_advanced ~317

Verification-oriented search with domain filters and waterfall fallback. Use for claim checking, Chinese-source search, or publisher restrictions. Start with free_search for quick discovery. The response exposes source_count, stop_reason, evidence_budget, and partialFailures. @readOnly true @idempotent true — runs waterfall progressive search across policy-allowed engines. Makes outbound HTTP requests to search engines and optionally to Jina Reader for content enrichment.

NameTypeReqDescription
countintegerNumber of results (1-20)
enrichbooleanEnable content enrichment (extract full page for low-confidence results)
enrich_maxnumberMax results to enrich per search
exclude_domainsarrayExclude these domains
include_domainsarrayOnly search these domains
languagestringLanguage preference
min_confidencenumberMinimum source-reliability confidence (0-1). Legacy values 2-3 are treated as min_source_count.
min_source_countintegerMinimum independent upstream provider families; the input contract is capped at 12 for compatibility
querystringyesSearch query
time_rangestringDeprecated compatibility field; returns UNSUPPORTED_FILTER because general-search recency is not enforced end to end
waterfallbooleanEnable waterfall progressive search (saves engine calls)
waterfall_min_confidencenumberMinimum average confidence to stop waterfall early
waterfall_min_resultsnumberMinimum results per phase for waterfall confidence check
NameTypeReqDescription
cache_hitboolean
detected_languagestring
enginesarrayyes
metaobjectyes
partialFailuresarray
querystringyes
rate_limitsobject
resultsarrayyes
security_notestringyes

No examples provided.

search_with_synthesis ~178

Opt-in deep search with waterfall verification and content enrichment. Returns structured results plus a prompt_hint; it does not call an external LLM. Use when multi-source evidence needs a synthesis handoff. free_search is the default for discovery; this path uses more tokens and network time. @readOnly true @idempotent true — runs waterfall search across free+paid engines with content enrichment.

NameTypeReqDescription
countintegerNumber of search results to gather (1-20)
languagestring
min_confidencenumberMinimum source-reliability confidence (0-1). Legacy values 2-3 are treated as min_source_count.
min_source_countintegerMinimum independent upstream provider families; the input contract accepts 1-12 for compatibility.
querystringyesSearch query
NameTypeReqDescription
cache_hitboolean
detected_languagestring
enginesarrayyes
metaobjectyes
partialFailuresarray
prompt_hintstringyes
querystringyes
rate_limitsobject
resultsarrayyes
security_notestringyes

No examples provided.

Common questions

What is the io.github.lennney/agent-search-mcp server?

io.github.lennney/agent-search-mcp is listed in the public MCP registry as io.github.lennney/agent-search-mcp. Free-first Chinese and English web search MCP using zero-key sources and inspectable evidence. This page covers its npm package (agent-search-mcp).

Is the io.github.lennney/agent-search-mcp server safe to use?

io.github.lennney/agent-search-mcp scores 77 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.lennney/agent-search-mcp server expose?

io.github.lennney/agent-search-mcp exposes 7 tools: free_search, free_search_advanced, free_extract, fetch_github_readme, fetch_csdn_article, and 2 more. Their descriptions and schemas cost roughly 1,165 tokens of context every time the server is loaded.

Is the io.github.lennney/agent-search-mcp server still maintained?

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

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