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

@agent-sh/harness-web-mcp

v0.2.2

Published

MCP stdio server exposing @agent-sh/harness-websearch and @agent-sh/harness-webfetch to Claude Code, Codex and any MCP client: keyless web search plus SSRF-safe fetch with markdown extraction

Readme

@agent-sh/harness-web-mcp

MCP server that gives Claude Code, Codex, and any other MCP client two web tools:

  • websearch: web search with no API key and no setup (Exa → Parallel → Mojeek → Marginalia → Wikipedia). Add Brave, Tavily or a self-hosted SearXNG for more coverage.
  • webfetch: fetch a URL and get clean markdown back, with SSRF defense, redirect reporting, size caps and a per-session cache.

They are the @agent-sh/harness-websearch and @agent-sh/harness-webfetch tools served over stdio, with their own descriptions and schemas unchanged. Part of the agent-sh/tools monorepo.

Add it to your agent

Claude Code

claude mcp add -s user harness-web -- npx -y @agent-sh/harness-web-mcp

Codex

codex mcp add harness-web -- npx -y @agent-sh/harness-web-mcp

Restart the agent (in Claude Code, /mcp reconnects). The tools show up as mcp__harness-web__websearch and mcp__harness-web__webfetch in Claude Code, and as harness-web tools in Codex.

npx -y downloads the latest version on first start. To pin a version, or skip npx's startup cost, install it globally and point the client at the binary:

npm i -g @agent-sh/harness-web-mcp
claude mcp add -s user harness-web -- harness-web-mcp

Claude Code (~/.claude.json, or a project .mcp.json):

{
  "mcpServers": {
    "harness-web": {
      "command": "npx",
      "args": ["-y", "@agent-sh/harness-web-mcp"],
      "env": { "BRAVE_API_KEY": "optional" }
    }
  }
}

Codex (~/.codex/config.toml):

[mcp_servers.harness-web]
command = "npx"
args = ["-y", "@agent-sh/harness-web-mcp"]

[mcp_servers.harness-web.env]
BRAVE_API_KEY = "optional"

Any other MCP client: run npx -y @agent-sh/harness-web-mcp as a stdio server.

Configuration

Everything is optional; with no configuration you get keyless search and strict fetch.

| Variable | Effect | |---|---| | BRAVE_API_KEY | Brave leads the search chain; the keyless chain remains a fallback. Free tier at api-dashboard.search.brave.com. | | TAVILY_API_KEY | Tavily joins the head of the search chain. | | EXA_API_KEY, PARALLEL_API_KEY | Raise those engines' keyless rate limits. | | SEARXNG_URL | Self-hosted SearXNG (e.g. http://127.0.0.1:8888) leads the chain. Loopback is allowed for this URL only. | | HARNESS_WEB_FETCH_ALLOW_LOOPBACK=1 | Let webfetch reach localhost. Off by default. | | HARNESS_WEB_FETCH_ALLOW_PRIVATE=1 | Let webfetch reach private networks (RFC 1918). Off by default. |

Pass variables with claude mcp add -e KEY=value …, codex mcp add --env KEY=value …, or the env block in the config file.

Safety

  • The MCP client approves each call. Claude Code and Codex ask before running a tool unless you allow it, so this server does not add a second permission prompt.
  • webfetch refuses loopback, private networks and cloud metadata endpoints by default, resolves DNS once to block rebinding, and caps response size.
  • Treat results as data, not instructions. Both tool descriptions tell the model so, because a fetched page or a search snippet can contain prompt-injection text.
  • Search queries go to the engines in the chain (Exa, Parallel, Mojeek, Marginalia, Wikipedia, plus any keyed engine you add).

Programmatic use

import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { createWebMcpServer, optionsFromEnv } from "@agent-sh/harness-web-mcp";

await createWebMcpServer({ ...optionsFromEnv(), braveApiKey: process.env.MY_KEY })
  .connect(new StdioServerTransport());

License

MIT © Avi Fenesh