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 🙏

© 2025 – Pkg Stats / Ryan Hefner

advanced-websearch-mcp

v1.0.4

Published

```bash # Install runtime dependencies npm install @modelcontextprotocol/sdk axios cheerio puppeteer ``` ```bash # Install dev dependencies npm install -D typescript @types/node ``` ## Step 2: Create package.json (if it doesnt exist yet) ```bash bashcat >

Downloads

467

Readme

Local Developement of the MCP Server

Step 1: Install All Dependencies

# Install runtime dependencies
npm install @modelcontextprotocol/sdk axios cheerio puppeteer
# Install dev dependencies
npm install -D typescript @types/node

Step 2: Create package.json (if it doesnt exist yet)

bashcat > package.json << 'EOF'
{
  "name": "advanced-websearch-mcp",
  "version": "1.0.0",
  "type": "module",
  "main": "index.js",
  "bin": {
    "advanced-websearch-mcp": "index.js"
  },
  "scripts": {
    "build": "tsc",
    "start": "node index.js",
    "dev": "tsx index.ts"
  },
  "dependencies": {
    "@modelcontextprotocol/sdk": "^1.0.4",
    "axios": "^1.7.0",
    "cheerio": "^1.0.0",
    "puppeteer": "^23.0.0"
  },
  "devDependencies": {
    "@types/node": "^22.0.0",
    "typescript": "^5.6.0",
    "tsx": "^4.19.0"
  }
}
EOF

Step 3: Install Dependencies

npm install

Step 4: Create tsconfig.json (if it doesnt exist yet)

cat > tsconfig.json << 'EOF'
{
  "compilerOptions": {
    "target": "ES2022",
    "module": "NodeNext",
    "moduleResolution": "NodeNext",
    "outDir": "./dist",
    "rootDir": ".",
    "strict": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,
    "resolveJsonModule": true,
    "allowSyntheticDefaultImports": true
  },
  "include": ["index.ts"],
  "exclude": ["node_modules", "dist"]
}
EOF

Step 5: Compile

# Or compile to current folder
npx tsc --outDir .

Step 6: Run with Inspector

# Run the compiled JavaScript
npx @modelcontextprotocol/inspector node index.js
  • Then click "connect" in the Browser UI.
  • Then click "List Tools" to see the available tools
  • Then click "fetch_and_ground" for the primary endpoint
  • Then click "Add Item", enter a URL you want to test and click "Run Tool"

Publishing the npm package of the mcp server to use it with mcpo

Make sure you’re logged in:

npm login
npm publish
  • then add the npm package to mcpo here: config.json
  • pushing or tagging in the mcpo repository will create a new docker image
  • then make the mcpo kubernetes pod use the newest docker image