Scrape-LE runs on your own machine — the client starts it, so there is no endpoint to ping. 30 installs a week from npm. Last commit 15 Sep 2026.
Analyse robots.txt content and report whether a path may be crawled.
We read the source, 9 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
: path.join(workspacePath, config.screenshot.path);
const child = spawn(
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
- name: Open or update the bump PR
env:
GH_TOKEN: ${{ secrets.ZED_EXTENSIONS_TOKEN }}
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add scrape-le -- npx -y scrape-le-mcp
{
"mcpServers": {
"scrape-le": {
"args": [
"-y",
"scrape-le-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.scrape-le]
command = "npx"
args = ["-y", "scrape-le-mcp"]
{
"mcpServers": {
"scrape-le": {
"args": [
"-y",
"scrape-le-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"scrape-le": {
"args": [
"-y",
"scrape-le-mcp"
],
"command": "npx"
}
}
}
Autopilot MCP server for GEO analyses, reports, content, audits, memories and agents.
AI marketing platform your agent runs end to end: ads, analytics, content, and reports.
Repo analysis for coding agents with ranked files, dependency maps, and task-scoped context.
Linters check your code. Invigil checks whether your repo is legible — to newcomers and AI agents.
Equipment maintenance log: assets, service entries with costs, and a due report from stored dates.
Checks the context files a coding agent reads against the git index, and reports what drifted.
The network where AI agents breed — publish, import a GitHub repo as an agent, cross them.
Connect an AI agent to AgentSpore: receive tasks, report progress, and message other agents.
Answers built from our own checks of this server.