io.github.wtznicy/my-websearch
NPM · MY-WEBSEARCH · SCANNED AUG 19
MyWebSearch - multi-engine web search MCP server, CLI and local daemon. No API keys required.
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 →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 192 of 197 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 192 of 197 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
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 (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 647 tokens (~92/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 45% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · my-websearch
claude mcp add wtznicy-my-websearch -- npx -y my-websearch
codex mcp add wtznicy-my-websearch -- npx -y my-websearch
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wtznicy-my-websearch": {
"type": "local",
"command": [
"npx",
"-y",
"my-websearch"
],
"enabled": true
}
}
} openclaw mcp add wtznicy-my-websearch --command npx --arg -y --arg my-websearch
mcp_servers:
wtznicy-my-websearch:
command: "npx"
args: ["-y", "my-websearch"] {
"mcpServers": {
"wtznicy-my-websearch": {
"command": "npx",
"args": [
"-y",
"my-websearch"
]
}
}
} 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 Aug 26 +26
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Dependency health: unverified → partial ▲ functional
- 18 Aug 26 −10
- Known CVEs: partial → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: partial → unverified ▼ functional
- Package version: 1.0.3 → 1.0.5 functional
- Package version: 1.0.3 → 1.0.4 functional
- 17 Aug 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 1.0.2 → 1.0.3 functional
- 16 Aug 26 0
- Known CVEs: pass → partial ▼ security
- Stability: unverified → 0.03 ▲ functional
- Dependency health: 0.88 → partial functional
- Package version: 1.0.1 → 1.0.2 functional
- 15 Aug 26 66
First indexed and scored.
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 19 Aug 2026 · Analysed npm/my-websearch@1.0.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 192 packages
| Packages resolved | 192 |
|---|---|
| Deprecated | 1 |
| Stale | 48 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
fetchCsdnArticle ~29
Fetch full article content from a csdn post URL
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
fetchGithubReadme ~27
Fetch README content from a GitHub repository URL
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
fetchJuejinArticle ~35
Fetch full article content from a Juejin(掘金) post URL
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
fetchWebContent ~96
Fetch content from a public HTTP(S) URL (supports Markdown files and normal web pages)
| Name | Type | Req | Description |
|---|---|---|---|
| includeLinks | boolean | – | – |
| maxChars | integer | – | – |
| raw | boolean | – | Return the raw response body (HTML/plain text) without extraction |
| readability | boolean | – | – |
| startIndex | integer | – | Character offset to start reading from (for paging through long content) |
| url | string | yes | – |
No output schema declared.
No examples provided.
queryDocs ~176
Get up-to-date, version-specific official docs and code snippets for a Context7 library ID (e.g. /vercel/next.js, version-pinnable like /vercel/next.js@v15.1.8). Use with resolveLibraryId for official documentation lookups — direct, reliable, no proxy needed.
| Name | Type | Req | Description |
|---|---|---|---|
| libraryId | string | yes | Exact Context7-compatible library ID (e.g. /vercel/next.js, /packages/express; optional version like /vercel/next.js@v15.1.8) |
| limit | integer | – | Maximum number of code snippets to return (default 5) |
| query | string | – | The question or task to get relevant documentation for (optional; defaults to an overview when omitted, e.g. 'how to set up middleware with auth') |
No output schema declared.
No examples provided.
resolveLibraryId ~151
PREFERRED for official docs: resolve a library/package name to a Context7 library ID (e.g. /vercel/next.js). Use this (then queryDocs) FIRST when the task needs official library/framework documentation — more reliable than web search and works without a proxy.
| Name | Type | Req | Description |
|---|---|---|---|
| libraryName | string | yes | The library or package name to search for (e.g. 'Next.js', 'express', 'prisma') |
| limit | integer | – | Maximum number of library matches to return (default 5) |
| query | string | – | The user's question or task, used to rank results by relevance (optional; defaults to the library name when omitted, e.g. 'how to implement authentication') |
No output schema declared.
No examples provided.
search ~133
Search the web across multiple engines with no API key required. searchMode: omit/auto = server SEARCH_MODE; request/playwright force that mode. For OFFICIAL library/framework documentation, prefer resolveLibraryId + queryDocs (more reliable, works without proxy). Use the site: operator for site-specific queries (e.g. "update site:docs.elastic.co").
| Name | Type | Req | Description |
|---|---|---|---|
| engines | array | – | – |
| limit | number | – | – |
| minResults | integer | – | Auto-run additional engines when fewer than this many results come back (default: disabled) |
| query | string | yes | – |
| searchMode | string | – | – |
No output schema declared.
No examples provided.