{"id":"scrapy-mcp-server","name":"scrapy-mcp-server","af_score":39.0,"security_score":17.8,"reliability_score":22.5,"what_it_does":"scrapy-mcp-server is an MCP server intended to help AI assistants inspect and debug Scrapy spiders and automatically generate fixes when scraping breaks (e.g., selector changes, A/B layout variants, and anti-bot changes). The README frames a workflow where monitoring/CI triggers the MCP-based debugging and produces a pull request with updated spider logic.","best_when":"You run Scrapy spiders in a controlled engineering workflow and can review/merge AI-generated patches; you also have monitoring signals that indicate scraping regressions.","avoid_when":"You need guaranteed correctness without human oversight, or you cannot tolerate that the tool may make extensive changes to spider code/logic based on sampled live pages.","last_evaluated":"2026-04-04T21:45:09.534900+00:00","has_mcp":true,"has_api":false,"auth_methods":[],"has_free_tier":false,"known_gotchas":["The README describes a high-level workflow but provides no MCP tool schema; an agent may not know exact tool names/inputs/outputs without additional MCP documentation.","AI-generated fixes can be broad; requires human review to prevent regressions or overfitting to a single sampled response.","Live scraping for inspection may trigger anti-bot measures; ensure rate limits, caching, and respectful crawling policies are enforced externally."],"error_quality":0.0}