Search1api MCP vs Scrapi

A side-by-side look at the Search1api MCP and Scrapi MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Search1api MCP logoSearch1api MCPSearch & Data Extraction · Local subprocess (stdio)Search via search1api (requires paid API key)67GreatAuth: api key requiredScrapi logoScrapiSearch & Data Extraction · Local subprocess (stdio)Web scraping for AI agents. Converts URLs to clean, LLM-ready Markdown with anti-bot bypass.59GoodAuth: not declared

Verdict: choose Search1api MCP for search & data extraction work as a local process; choose Scrapi for search & data extraction as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Search1api MCP logoChoose Search1api MCP when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: SEARCH1API_KEY.
  • You want tools like search, news, crawl.
Explore Search1api MCP

Scrapi logoChoose Scrapi when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: SCRAPI_API_KEY.
  • You want tools like scrape_url, scrape_urls, get_usage.
Explore Scrapi

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSearch1api MCP logoSearch1api MCPScrapi logoScrapi
CategorySearch & Data ExtractionSearch & Data Extraction
Quality signal67/100 · Great59/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNot declared
PricingPaid serviceNot declared
Required env varsSEARCH1API_KEYSCRAPI_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars1735
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools55

Tools & capabilities

Search1api MCP tools 5

  • searchSearch the live public web when the user needs current information, sources, or research. Returns citable results with id, title, URL, and text. Pass a result URL to crawl to retrieve the full page.
  • newsSearch current news when the user asks about recent events, announcements, or coverage. Returns citable article results with title, URL, snippet, and optional extracted text.
  • crawlExtract the readable title and full text from a public URL supplied by the user or returned by search.
  • sitemapDiscover related public links from a page or domain when the user wants to explore a site's structure or available pages.
  • trendingList currently trending repositories or stories from GitHub or Hacker News when the user asks what is popular now.

Scrapi tools 5

  • scrape_urlScrapes a webpage and returns the content in AI-readable Markdown format. Can access blocked sites through browser rendering.
  • scrape_urlsScrapes multiple webpages in parallel and returns the content in AI-readable Markdown format. Can access blocked sites through browser rendering.
  • get_usageCheck API usage and remaining credits. Returns current plan, subscription credits, purchased credits, and total remaining credits.
  • scraper_server_statusCheck the status of all ScraperServer instances. Shows server health, circuit breaker state, failure counts, and last success/failure times.
  • get_billingRetrieve MCP billing information: subscription details, available plans, daily usage history, or spending limits.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Search1api MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "fatwang2-search1api-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "search1api-mcp"
      ],
      "env": {
        "SEARCH1API_KEY": "YOUR_SEARCH1API_KEY_HERE"
      }
    }
  }
}

Scrapi

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "scrapi": {
      "command": "npx",
      "args": [
        "-y",
        "@scrapi.ai/mcp-server"
      ],
      "env": {
        "SCRAPI_API_KEY": "YOUR_SCRAPI_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Search1api MCP is categorized under Search & Data Extraction and uses a local stdio subprocess. Scrapi belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Search1api MCP for search & data extraction work and Scrapi for search & data extraction.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Search1api MCP is listed as a paid service. Auth: api key required. Scrapi has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add fatwang2-search1api-mcp and scrapi as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Search1api MCP has a quality signal of 67/100 (Great) with 1 views, 0 installs and 173 GitHub stars. Scrapi has 59/100 (Good) with 1 views, 0 installs and 5 GitHub stars.