smart-web

io.github.rich-jojoPublished by GitHub account rich-jojov0.8.4Updated Oct 30, 2026

Web search, direct-URL fetch, crawl, and docs export MCP. smartfetch for URLs.

VerifiedSTDIODesktop onlyWeb Search & Scraping

Overview

AI-generated overview

Local MCP server that gives an assistant web search, direct-URL fetching, crawling and documentation export.

What you can do
  • Search the web and retrieve results for a query
  • Fetch a given URL directly and read its content
  • Crawl pages to collect content across a site
  • Export documentation gathered from the web
  • Read optional settings and temp locations from environment variables
When to use it
Useful when an assistant needs live web information, the contents of a specific page, or a crawl of several pages, and you want that done from a local process rather than a hosted service.
Requirements
Runs as a local stdio process installed from the npm package smart-web-mcp, so Node.js is needed. Optional environment variables SMART_WEB_SETTINGS_FILE (settings JSON path, defaults to a config file under the home directory) and SMART_WEB_TMP_DIR (temp root for snapshots and export staging). Network access is required for search and fetching. No authentication is declared.
Before you install
Fetched pages and search results come from third parties, so content the assistant reads may be untrusted. Crawling can send many requests to external sites. The server writes snapshots and export staging files to a temp directory, which you can redirect with SMART_WEB_TMP_DIR. It is desktop-only and not available as a web executable.

Installation

In SourceWeft

  1. Open smart-web in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.8.4LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.