Web Content & URL Tools MCP Server

by avaloncompany Your server? Claim it

answering

Web Content & URL Tools is answering right now. Last checked 13 min ago. Last commit 4 Oct 2026.

26 tools: web pages to Markdown, metadata, tech stack, SSL, SEO, domains, email auth and SSO checks.

Uptime history 9 days of history · worst day 99%

9 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

368 ms

Response time

average over 24h

Stars

last commit 4 Oct 2026

Web Content & URL Tools missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add web-content-url-tools --transport http https://avalonai--web-content-url-tools-mcp.apify.actor/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "web-content-url-tools": {
      "url": "https://avalonai--web-content-url-tools-mcp.apify.actor/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.web-content-url-tools]
url = "https://avalonai--web-content-url-tools-mcp.apify.actor/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "web-content-url-tools": {
      "url": "https://avalonai--web-content-url-tools-mcp.apify.actor/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "web-content-url-tools": {
      "url": "https://avalonai--web-content-url-tools-mcp.apify.actor/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://avalonai--web-content-url-tools-mcp.apify.actor/mcp	streamable-http	needs auth	375 ms	13 min ago

Alternatives to Web Content & URL Tools

same job, measured the same way

x402 Web Tools

by iparadise71

Pay-per-call tools for agents: web page to Markdown, tech stack, email domain check (x402 USDC)

4 tools answering

SiteCheck

by bck-stack

29 pay-per-call agent tools: web reader, PDF, tech stack, email, domain, Solana, KYB. Paid via x402

29 tools answering

Fieldwright

by cybermax-tools

Fieldwright: web page to clean Markdown, metadata, JSON-LD, emails, phones.

1 tools answering

Fieldwright

by shawmena-dotcom

Fieldwright: web page to clean Markdown, metadata, JSON-LD, emails, phones.

1 tools answering

Fieldwright

by workers-cybermax-tools-cybermax

Fieldwright: web page to clean Markdown, metadata, JSON-LD, emails, phones.

1 tools answering

ARC-Relay

by arc-relay

DMARC-safe email forwarding for agents: aliases, DNS health checks, and MCP tools on your domains.

6 tools answering

DomainDNA

by workers-cybermax-tools-cybermax

Tech stack, email security (SPF, DMARC, MX provider) and domain age API + MCP. 25 free domains/day.

4 tools answering

Straelo Relay

by straelo

MCP tools for agents: web research, content extraction, email, DNS, and blockchain intelligence.

8 tools answering

Web Content & URL Tools — questions

Answers built from our own checks of this server.

Why is there no tool list for Web Content & URL Tools?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Web Content & URL Tools working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 368 ms. The bar chart above shows every period we have measured.

How do I connect Web Content & URL Tools?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does Web Content & URL Tools need an API key?

Yes. Every time we knock, Web Content & URL Tools answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Web Content & URL Tools?

It answers our handshake in 368 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Web Content & URL Tools open source?

Yes — it is published under the MIT licence, written in Python, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.