Back to MCP Directory
Search1api
Model Context Protocol moderate risk

Search1api

The Search1API MCP server provides search, news, crawling, and reasoning capabilities via API key authentication, enabling integration with various MCP clients and LibreChat.

Connections & Capabilities

Connects To

GitHubDocker

Capabilities

readexec

Quickstart

Install

npm install
npm

Config

{
  "mcpServers": {
    "search1api": {
      "command": "npx",
      "args": [
        "-y",
        "search1api-mcp"
      ],
      "env": {
        "SEARCH1API_KEY": "YOUR_SEARCH1API_KEY"
      }
    }
  }
}

Exposed MCP Tools (6)

safe
search

Searches the web using the Search1API service and returns relevant results.

Read-only operation; retrieves search results without modifying data.

safe
news

Searches for news articles using the Search1API service and returns relevant results.

Read-only operation; retrieves news articles without modifying data.

moderate
crawl

Extracts content from a specified URL using the Search1API service.

Crawls arbitrary URLs, potentially exposing the system to malicious content or excessive resource consumption.

safe
sitemap

Retrieves all related links from a specified URL's sitemap.

Read-only operation; retrieves sitemap links without modifying data.

moderate
reasoning

Uses the DeepSeek R1 model to perform deep thinking and complex problem-solving, leveraging web search capabilities.

Relies on an external model and web search, potentially exposing the system to biased or inaccurate information.

safe
trending

Retrieves trending topics from specified platforms like GitHub and Hacker News.

Read-only operation; retrieves trending topics without modifying data.

Safety Assessment

This server offers moderate safety due to its reliance on API key authentication and primarily read-only search operations. The crawl and reasoning tools introduce some risk if used carelessly. It's safe when used responsibly with rate limits and trusted URLs, but risky if API keys are exposed or untrusted URLs are crawled.

  • API key authentication
  • Read-only search operations by default
  • Optional crawl functionality with configurable limits
  • No direct filesystem access
  • Rate limiting via Search1API service
  • API key management responsibility on the user
  • Potential for excessive API usage leading to cost
  • Crawling tool can access arbitrary URLs, posing a risk if misused
  • Reasoning tool relies on external model (DeepSeek R1) with unknown biases
  • No built-in input sanitization; relies on Search1API for security