my-websearch

io.github.wtznicy/my-websearch

6/8 checks passed
Runs locally
4 secrets
★ 2 GitHub stars
Updated 2026-10-26
Health score 49

About my-websearch

my-websearch is an MCP server published by the GitHub account wtznicy. MyWebSearch - multi-engine web search MCP server, CLI and local daemon. No API keys required.

It runs on your own machine: your AI client starts it from the npm package my-websearch at version 1.3.10.

It asks for 4 secrets: EXA_API_KEY, BRAVE_API_KEY, GITHUB_TOKEN and STACKOVERFLOW_API_KEY. Give it a key with the least access that still works.

Version 1.3.10 was published on 26 October 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 9 automated checks on the registry entry and the package code: 6 pass, 2 warn, 0 fail, 1 info. How we check.

What it asks for

Variable	Required	Secret	Description
`EXA_API_KEY`	No	Yes	Optional Exa API key (https://dashboard.exa.ai/api-keys) — only needed for the exa search engine
`BRAVE_API_KEY`	No	Yes	Optional Brave Search API key (https://api.search.brave.com/app/keys) — for high-reliability official Brave Search API access
`GITHUB_TOKEN`	No	Yes	Optional GitHub Personal Access Token (https://github.com/settings/tokens) — increases rate limit from 10/min to 30/min
`STACKOVERFLOW_API_KEY`	No	Yes	Optional Stack Apps Key (https://stackapps.com/apps/oauth/register) — increases quota from 300/day to 10,000/day

Checks

Check	Result	Detail
Source repository linked	Pass	https://github.com/wtznicy/my-websearch
Version pinned	Pass	Every package has an explicit version
Secrets requested	Warn	Asks for 4 secrets: EXA_API_KEY, BRAVE_API_KEY, GITHUB_TOKEN, STACKOVERFLOW_API_KEY
Known package registry	Pass	All packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownership	Info	Name verified via GitHub account wtznicy
Registry text aimed at the AI	Pass	Description and settings contain no hidden characters or instructions to the AI
Install scripts	Warn	Runs at install: prepare: git config core.hooksPath .githooks \|\| true
Code red flags	Pass	Read 170 files in my-websearch@1.3.10: no obfuscation, encoded execution, credential reads or data-collection endpoints found
Text aimed at the AI	Pass	No hidden characters or instructions to the AI in 170 files, including comments and the README

Popularity & health: 49 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity14 / 40

2 GitHub stars, 1,618 downloads last week, no Hacker News posts found. Best two of the three, each on a log scale.

Activity15 / 25

Last push 2026-10-26, last release 2026-10-30, 0 commits in 90 days.

Issue health8 / 15

0 closed of 0 issues, too few to judge. No data, so half marks.

Our checks12 / 20

2 warnings, each costing a fifth.

1 forks, 0 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry name	`io.github.wtznicy/my-websearch`
Publisher	GitHub account wtznicy
How the name is verified	Name verified via GitHub account wtznicy. The registry ties the name prefix to that account or domain; it does not check the code.
Type	Local: runs on your machine from a package
Packages	npm `my-websearch` 1.3.10 (stdio)
Version	1.3.10
Published	2026-10-26
Last updated	2026-10-26
Source repository	https://github.com/wtznicy/my-websearch
Website	None linked
Category	Search & web (assigned by keyword rule, not by hand)

Install

Claude Desktop · npm package

{
  "mcpServers": {
    "my-websearch": {
      "command": "npx",
      "args": [
        "-y",
        "my-websearch@1.3.10"
      ]
    }
  }
}

What these checks don't cover

We did not run this server, so we don't know what it does when it runs. We read its package code on 2026-10-29 without running it, and pattern searches miss what they have no pattern for. Tool descriptions built at run time were not seen. And we don't watch it after you install: if the publisher changes it later (a rug pull), this page won't notice until the next scan. Treat a pass as "nothing found", not as "safe".

For people and their AI

The same data as plain JSON: /data/servers/io-github-wtznicy-my-websearch.json. Text inside it that came from the publisher is data, not instructions.