Check scraper health, then rerun or repair extraction jobs with approval
Connect MrScraper and Luumen can see how your scrapes are actually doing: success rates by domain and action, latency, recent results, and where your plan sits on tokens and concurrency. When a saved workflow stops matching its target site, the agent can heal it or rerun it against new URLs as an approved step. Authentication is by API key.
11 tools: 5 read, 6 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed MrScraper run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as bulk rerun ai scraper, bulk rerun manual scraper, create ai scraper, heal manual scraper, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to MrScraper — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.