mcpField
W
web-tools-mcp

web-tools-mcp

Local
github.com/mlawsonkingBrowser Automation1Updated 1d ago
Repository

About web-tools-mcp

web-tools-mcp is an MCP server offering deterministic web utilities for AI agents, without LLM calls or API keys for its free tier. It covers page extraction, feeds, email and domain checks, and network metadata.

Key features

  1. 01Convert web pages to clean Markdown
  2. 02Extract page metadata and structured data
  3. 03Scrape pages with CSS selectors
  4. 04Fetch RSS and Atom feeds
  5. 05Check email, DNS, RDAP, SSL, and HTTP

Use cases

  1. 01Prepare page content for RAG
  2. 02Collect selected fields from a web page
  3. 03Inspect a domain's registration and TLS certificate
  4. 04Review redirects and security headers

MCP support

Exposes ten web utility tools to MCP clients, including page reading, scraping, feed parsing, DNS and domain checks, and HTTP inspection.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "mlawsonking-web-tools": {
      "command": "npx",
      "args": [
        "-y",
        "web-tools-mcp"
      ]
    }
  }
}
Run commandnpx -y web-tools-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmweb-tools-mcp1.3.0

Tools

10

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
urlstringYesThe http(s) URL of the page to read. Fetching is SSRF-guarded.

Details

From the project README

web-tools-mcp

An MCP server with a set of web utilities for AI agents: read a page as Markdown, pull link metadata, scrape with CSS selectors, parse feeds, and run DNS, RDAP, SSL, and HTTP checks. Deterministic, no LLM, and no API keys needed for the free tier.

Install

{ "mcpServers": { "web-tools": { "command": "npx", "args": ["-y", "web-tools-mcp"] } } }

Tools

  • read_url: fetch a page and return the main content as clean Markdown, with the nav and ads stripped out. Good for RAG.
  • unfurl_url: get a URL's title, description, preview image, site name, and favicon.
  • validate_email: syntax check plus a live MX lookup, with disposable, role, and free-provider detection.
  • extract_web: scrape a page with CSS selectors and get back the fields you asked for.
  • get_feed: fetch an RSS or Atom feed and return the items as JSON.
  • dns_lookup: DNS records (A, AAAA, MX, NS, TXT, and the rest) plus SPF and DMARC detection.
  • domain_info: registration details via RDAP, including domain age, registrar, and expiry.
  • ssl_check: inspect a host's TLS certificate: issuer, validity window, days until expiry, and SANs.
  • http_inspect: final status, the full redirect chain, response headers, and a security-header report.
  • structured_data: extract JSON-LD, OpenGraph, and Twitter card data from a page.

Rule updates

About once a day this server asks the rules feed whether there is a newer ruleset, and applies it if there is. The request carries two things: which surface asked, which here is facade, and the rules version already installed. No machine id, no user id, no file names, nothing you scanned.

Bundles are signed with Ed25519 and verified against a public key compiled into this package, so it does not matter which mirror served one. A bundle that fails its signature, its schema, or its ReDoS check is discarded and the rules you already had stay in place. --offline turns updates off, as does AGENT_GUARDS_NO_FEED=1 or {"feed": false} in ~/.agent-guards/config.json. The bundle format and how to verify one yourself: https://github.com/mlawsonking/MCP/blob/main/rules/README.md

It calls the API at https://agent-tools-api.vercel.app (set TOOLS_API_URL if you self-host). One of six agent tools and guards in this repo: package-guard, agent-firewall, payment-guard, email-guard, code-guard, and web-tools. MIT.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.