Scrape-LE
Scrape-LE is an MCP server published by nolindnaidoo; its MCP spec-revision support has not been verified yet. Last verified 2026-08-15.
Does Scrape-LE support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision Scrape-LE supports (as of 2026-08-15).
Is Scrape-LE a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for Scrape-LE (as of 2026-08-15).
How do I connect to Scrape-LE?
Scrape-LE is available via the package npm:scrape-le-mcp, the official MCP Registry under io.github.nolindnaidoo/scrape-le, the source repository at https://github.com/nolindnaidoo/scrape-le. Authentication: unknown. Transports: stdio.
When were Scrape-LE's facts last verified?
2026-08-15. Each fact on this page links to the sources used to verify it.
Analyse robots.txt content and report whether a path may be crawled.
How widely adopted is Scrape-LE?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for Scrape-LE
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 1
- Forks
- 0
- Last pushed
- (38 days ago)
- Created
- Open issues
- 0
- Primary language
- Rust
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Declared topics: anti-bot, captcha, cli, cloudflare, developer-tools, headless, letools, mcp, playwright, rate-limit, reachability, robots-txt, rust, scraper, static-analysis, typescript, vscode, vscode-extension, web-scraping — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
2.2.5- Last published
- First published
- Releases
- 4
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 0
- Unpacked size
- 16 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: registry-record
· confidence 0.85 (Good).