Scrape websites by following links and extract structured data from natural language instructions.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Scrape a website by following links and extracting relevant information based on natural language instructions
The starting URL for the scraping process
A natural language instruction specifying what information to find
Maximum depth of link following (1-3)
Maximum number of links to follow per page (1-10)
Maximum total number of pages to visit (1-20)
How to handle JavaScript-heavy pages: minimal (fastest), moderate (balanced), aggressive (most thorough)
Maximum duration for the entire scraping process (30-300)
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
claude mcp add --transport http mcp-llm-scraper https://nova.civai.co/mcp/agents/mcp-llm-scraper
Scrape a website by following links and extracting relevant information based on natural language instructions
| Argument | Type |
|---|
| Description |
|---|
| url* | string | The starting URL for the scraping process |
| max_depth | integer | Maximum depth of link following (1-3) |
| max_links | integer | Maximum number of links to follow per page (1-10) |
| max_pages | integer | Maximum total number of pages to visit (1-20) |
| instruction* | string | A natural language instruction specifying what information to find |
| js_handling | string | How to handle JavaScript-heavy pages: minimal (fastest), moderate (balanced), aggressive (most thorough) |
| timeout_seconds | integer | Maximum duration for the entire scraping process (30-300) |
{
"type": "object",
"required": [
"instruction",
"url"
],
"properties": {
"url": {
"type": "string",
"description": "The starting URL for the scraping process"
},
"max_depth": {
"type": "integer",
"default": 2,
"maximum": 3,
"minimum": 1,
"description": "Maximum depth of link following (1-3)"
},
"max_links": {
"type": "integer",
"default": 5,
"maximum": 10,
"minimum": 1,
"description": "Maximum number of links to follow per page (1-10)"
},
"max_pages": {
"type": "integer",
"default": 10,
"maximum": 20,
"minimum": 1,
"description": "Maximum total number of pages to visit (1-20)"
},
"instruction": {
"type": "string",
"description": "A natural language instruction specifying what information to find"
},
"js_handling": {
"enum": [
"minimal",
"moderate",
"aggressive"
],
"type": "string",
"default": "moderate",
"description": "How to handle JavaScript-heavy pages: minimal (fastest), moderate (balanced), aggressive (most thorough)"
},
"timeout_seconds": {
"type": "integer",
"default": 120,
"maximum": 300,
"minimum": 30,
"description": "Maximum duration for the entire scraping process (30-300)"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 2, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.