Skip to content

MCPFax Web Extract

by mcpscores.com · remote · no sign-in to list tools · v1.0.1 · published by com.mcpscores

Read any web page as clean text for a prompt, or list every link on it.

Changes · 3
CompareRegistry entry

4 tools: 3 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http web-extract https://web-extract.bowling-anthony.workers.dev/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 3Claude Code: ask
  • demand_reportFREE, no payment.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    FREE, no payment. The aggregate of what agents have told us they are looking for, most-requested first, with the categories nothing available yet serves.
  • page_linksEvery hyperlink on a page, resolved to absolute URLs, each with its anchor text and whether it stays on the same host.Can send data outNo findings

    Why it is in this group

    • The name "page_links" says "link": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Every hyperlink on a page, resolved to absolute URLs, each with its anchor text and whether it stays on the same host. Use to crawl an index, find the real article behind a landing page, or enumerate a documentation table of contents before deciding what to read. Capped at 300 links. Costs $0.008 USDC per call via x402 on Base.
  • request_dataFREE, no payment.No findings

    Why it is in this group

    • The name "request_data" says "request": a word for a change.
    Description, as the server wrote it
    FREE, no payment. Describe in your own words the data you are trying to buy — anything, not just web pages — and get back whether we operate a service that supplies it, with the MCP endpoint if so. Every request is catalogued so repeatedly-requested data gets built. Nothing identifying is stored, only the words of the request.
Only reads 1Claude Code: allow, ask for 1 outbound
  • read_pageFetch a URL and return its readable text with scripts, styles, navigation and markup stripped, plus the title, description, site name and publication date from the page's own metad…Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "read_page" says "read": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Fetch a URL and return its readable text with scripts, styles, navigation and markup stripped, plus the title, description, site name and publication date from the page's own metadata. Use whenever you need the contents of a page rather than a search result about it. Output is capped so it fits a prompt — raise maxChars if you need more. JavaScript is not executed, so a page that renders entirely client-side returns its shell, and the character count tells you when that happened. A site that blocks automated clients is reported honestly and is NOT charged. Costs $0.008 USDC per call via x402 on Base.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http web-extract https://web-extract.bowling-anthony.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__web-extract__request_data",
      "mcp__web-extract__demand_report",
      "mcp__web-extract__read_page",
      "mcp__web-extract__page_links"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as web-extract. Review it before you use it.

Capability tags behind 2 rules
  • mcp__web-extract__read_page untrusted-input, outbound
  • mcp__web-extract__page_links outbound