
Evocrawl MCP Server
io.github.superaihumanPublished by GitHub account superaihumanv4.0.1Updated Oct 24, 2026
MCP server for Evocrawl — search, scrape, and interact with the web.
Overview
Lets an assistant search, scrape, and interact with web pages through the Evocrawl service.
- What you can do
- This MCP server connects an assistant to Evocrawl, a service for searching, scraping, and interacting with the web. It runs locally over stdio and exposes Evocrawl's web capabilities as tools, so the assistant can retrieve and work with web content on the user's behalf. The manifest does not list individual tool names.
- When to use it
- Worth adding when an assistant needs web search or page scraping and the user already uses Evocrawl or is willing to obtain an API key for it. Not useful for purely local tasks or for users who prefer a scraping tool that needs no account.
- Requirements
- Runs as a local process over stdio, installed from the npm package @evocrawl/evocrawl-mcp, so Node.js and npm are needed. Requires an Evocrawl account and an API key supplied through the EVOCRAWL_API_KEY environment variable. Network access is needed to reach the Evocrawl service. Desktop only.
Installation
In SourceWeft
- Open Evocrawl MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v4.0.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.