Web Content & URL ToolsSAFE
Remote MCP server with 26 tools for AI agents: web pages to Markdown, metadata, tech stack, SSL, security headers, SEO, domains, email auth (SPF/DMARC/DKIM), SSO checks and dev utilities. Hosted on Apify, pay per call.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
A remote Model Context Protocol server that gives AI agents 26 tools for reading and checking the web — no browser, no setup, pay only for successful calls.
Read any page as clean Markdown, pull its metadata or structure, detect its tech stack, and check redirects, TLS certificates, security headers, robots.txt, sitemaps, feeds, domains (WHOIS/DNS), SEO, broken links, email authentication (SPF, DMARC, DKIM) and single sign-on (SAML, OpenID Connect). It also includes everyday developer utilities (cron, regex, color, Unicode, time zones) and Hyperliquid perpetuals market data.
- Apify Store: https://apify.com/avalonai/web-content-url-tools-mcp
- Developer docs: https://avaloncompany.ai/developers/
- Transport: Streamable HTTP (remote, hosted on Apify Standby)
Connect
Option 1 — Standby URL + Apify API token
Use your Apify API token as a Bearer token. Works in Claude Desktop, Claude Code, Cursor, VS Code, Windsurf and any MCP client that supports remote servers with headers.
{
"mcpServers": {
"web-content-url-tools": {
"url": "https://avalonai--web-content-url-tools-mcp.apify.actor/mcp",
"headers": { "Authorization": "Bearer " }
}
}
}Option 2 — OAuth via mcp.apify.com (no token to copy)
Clients that support MCP OAuth can connect through Apify's hosted MCP gateway and sign in with their Apify account in the browser:
https://mcp.apify.com?tools=avalonai/web-content-url-tools-mcp
Claude Code example:
claude mcp add --transport http web-content-url-tools "https://mcp.apify.com?tools=avalonai/web-content-url-tools-mcp"
Tools
Web pages and URLs
9d4201d0e309OBSERVED · 2026-10-05Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (2 observation(s))
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (1)
Gates applied: no_behavioural_pass.
9d4201d0e309full audit observations/trust-audit/mcp-server/avaloncompany__web-content-url-tools.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-05 | 9d4201d0e309 | SAFE | B | 89 | first audit |
Questions
What is the Web Content & URL Tools MCP server?
Remote MCP server with 26 tools for AI agents: web pages to Markdown, metadata, tech stack, SSL, security headers, SEO, domains, email auth (SPF/DMARC/DKIM), SSO checks and dev utilities. Hosted on Apify, pay per call.
Is Web Content & URL Tools safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Web Content & URL Tools need?
It reads WCAPI_SECRET from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Web Content & URL Tools run?
It speaks streamable-http, so it runs as a service you connect to over the network.
How current is this page?
The grade is for one exact copy of the source (9d4201d0e309), read on 2026-10-05. The repository is watched and re-audited when it changes.