npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@neabyte/websearch-mcp

v0.1.0

Published

MCP server for web search and web fetch tools

Readme

WebSearch MCP

MCP server for web search and web fetch tools.

Node Deno License

Features

  • Two tools
    • web_search: find relevant URLs for a query
    • web_fetch: fetch latest page content (markdown/text)
  • Cost-aware workflow: recall → search → selective fetch (save quota)
  • Docs-first answers: answers can cite freshly fetched official pages

Official reference: Ollama Web Search

Installation

[!NOTE] Prerequisites: Node.js for npm install. OLLAMA_API_KEY is required for web_search.

npm:

npm install -g @neabyte/websearch-mcp

Quick Start

Run MCP Server (Stdio)

Run the server (example for MCP clients using stdio):

websearch-mcp

If you want to set the API key for Ollama web search:

export OLLAMA_API_KEY="..."
websearch-mcp

Editor Integration (Cursor / VSCode)

You can integrate this MCP server directly into editors (Cursor/VSCode) via stdio MCP configuration. Two common options:

  • Global install: npm install -g @neabyte/websearch-mcp then run websearch-mcp
  • No global install: use npx -y @neabyte/websearch-mcp (recommended for editors)

Example (Recommended): npx Stdio + Env

Paste this MCP server config in your editor (example JSON used by many MCP clients):

{
  "mcpServers": {
    "websearch-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@neabyte/websearch-mcp"],
      "env": {
        "OLLAMA_API_KEY": "YOUR_OLLAMA_API_KEY"
      }
    }
  }
}

OLLAMA_API_KEY is required for web_search. web_fetch can run without a key.

Smoke Test Prompt

After the server is registered in your editor, try a prompt like this:

Use installed MCP Servers: `websearch-mcp` - `web_fetch` to fetch https://reactnative.dev/docs/environment-setup. Summarize the macOS install steps.

Example Prompts

Direct fetch (when the URL is known):

Use installed MCP Servers: `websearch-mcp` - `web_fetch` to fetch the official React Native documentation pages. Question: How to install in macOS?

Search → fetch (when the URL is unknown):

Use installed MCP Servers: `websearch-mcp` - `web_search` to find official React Native docs URLs for "environment setup macOS". Then use `web_fetch` on the most relevant official doc page URLs. Question: How to install React Native in macOS?

Concept: LLM Knowledge → Latest Docs

This approach uses two steps:

  • Recall: the LLM proposes likely official URLs from its knowledge
  • Fetch: the LLM calls web_fetch to retrieve the latest content

This is useful for fast-changing documentation, because the final answer is grounded in pages fetched at tool-call time.

Strategy: Save Quota

Ollama can get expensive if you web_fetch many pages. A cost-aware pattern is:

  • Recall first: ask for a shortlist of likely official URLs
  • Search if needed: use web_search to find fresh candidates
  • Fetch selectively: fetch only 1–3 most relevant pages

With this pattern, you only spend fetch calls on pages you actually cite.

Examples (Screenshots)

Web Fetch (Single Tool)

| Prompt | Output | | ------------------------------------------ | ------------------------------------------ | | | |

  • Prompt: ask the model to use websearch-mcp + web_fetch to fetch official React Native docs
  • Output: the model fetches reactnative.dev and summarizes install steps

Web Search → Web Fetch (Double Tool)

Even if web_search has its own quota/limits, the “double tool” pattern can reduce total cost by shortlisting URLs first and fetching only what you need.

Use websearch-mcp web_search with query: "latest crypto payment gateway 2026".
Then use websearch-mcp web_fetch to fetch the official pages from the top results.
Answer with a short list of the latest crypto payment gateways and include the source links.

Build & Test

From the repo root (requires Deno).

Check — format, lint, and typecheck source:

deno task check

Unit Tests:

deno task test
  • Tests live under tests/

License

This project is licensed under the MIT license. See the LICENSE file for details.