Search1API▌
by fatwang2
Discover Search1API for web searches, news API, and newspaper API capabilities. Power content extraction and stay inform
Execute web searches, news queries, and content extraction.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / AI assistants needing current web information
- / Research and content gathering workflows
- / News monitoring and analysis
- / Web scraping and data extraction tasks
capabilities
- / Execute web searches
- / Query news articles
- / Extract content from web pages
- / Crawl websites for data
- / Access real-time web information
what it does
Provides web search, news queries, and content extraction through the Search1API service. Connects AI assistants to real-time web information and crawling capabilities.
about
Search1API is a community-built MCP server published by fatwang2 that provides AI assistants with tools and capabilities via the Model Context Protocol. Discover Search1API for web searches, news API, and newspaper API capabilities. Power content extraction and stay inform It is categorized under search web.
how to install
You can install Search1API in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Search1API is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
Search1API MCP Server
The official MCP server for Search1API — web search, news, crawling, and more in one API.
Get Your API Key
- Register at Search1API
- Get your API key from the dashboard
Quick Start (Remote MCP)
No installation required. Just configure your MCP client with the remote URL and your API key.
Authentication
Two methods are supported — use whichever your client supports:
| Method | Format |
|---|---|
| Authorization Header | Authorization: Bearer YOUR_SEARCH1API_KEY |
| URL Query Parameter | https://mcp.search1api.com/mcp?apiKey=YOUR_SEARCH1API_KEY |
Claude Desktop
{
"mcpServers": {
"search1api": {
"url": "https://mcp.search1api.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_SEARCH1API_KEY"
}
}
}
}
Claude.ai (Web)
Settings > Connectors > Add custom connector:
https://mcp.search1api.com/mcp?apiKey=YOUR_SEARCH1API_KEY
Cursor
{
"mcpServers": {
"search1api": {
"url": "https://mcp.search1api.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_SEARCH1API_KEY"
}
}
}
}
VS Code
{
"servers": {
"search1api": {
"type": "http",
"url": "https://mcp.search1api.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_SEARCH1API_KEY"
}
}
}
}
Claude Code
claude mcp add --transport http search1api https://mcp.search1api.com/mcp \
--header "Authorization: Bearer YOUR_SEARCH1API_KEY"
Windsurf
{
"mcpServers": {
"search1api": {
"serverUrl": "https://mcp.search1api.com/mcp?apiKey=YOUR_SEARCH1API_KEY"
}
}
}
Agent Skill
This repo also includes an Agent Skill that teaches agents how to use Search1API effectively — with decision strategies (when to search vs. crawl, how to tune parameters for different intents), multi-step workflows, and constraints.
The skill works in two modes: it prefers MCP tools when available, and falls back to bundled shell scripts for agents that don't support MCP (e.g. OpenClaw).
npx skills add fatwang2/search1api-mcp
Even if you're already using the MCP server above, the skill adds a strategy layer that helps agents make smarter decisions — like adjusting max_results based on research depth, choosing the right search_service for a query, or running a multi-step search → crawl → synthesize workflow. See the skills/ directory for details.
Quick start — copy and send this to your Agent:
I want to use Search1API for web search and content retrieval. Install the skill (npx skills add fatwang2/search1api-mcp), help me complete the setup, and run a quick test to verify it works.
Update skills:
Update my installed skills to the latest version: npx skills update
Local Mode (stdio)
If you prefer to run the server locally, use npx — no cloning required:
{
"mcpServers": {
"search1api": {
"command": "npx",
"args": ["-y", "search1api-mcp"],
"env": {
"SEARCH1API_KEY": "YOUR_SEARCH1API_KEY"
}
}
}
}
Tools
search
Search the web using Search1API.
| Parameter | Required | Default | Description |
|---|---|---|---|
query | Yes | - | Search query |
max_results | No | 10 | Number of results |
search_service | No | google, bing, duckduckgo, yahoo, x, reddit, github, youtube, arxiv, wechat, bilibili, imdb, wikipedia | |
crawl_results | No | 0 | Number of results to crawl for full content |
include_sites | No | [] | Sites to include |
exclude_sites | No | [] | Sites to exclude |
time_range | No | - | day, month, year |
news
Search for news articles.
| Parameter | Required | Default | Description |
|---|---|---|---|
query | Yes | - | Search query |
max_results | No | 10 | Number of results |
search_service | No | bing | google, bing, duckduckgo, yahoo, hackernews |
crawl_results | No | 0 | Number of results to crawl for full content |
include_sites | No | [] | Sites to include |
exclude_sites | No | [] | Sites to exclude |
time_range | No | - | day, month, year |
crawl
Extract content from a URL.
| Parameter | Required | Description |
|---|---|---|
url | Yes | URL to crawl |
sitemap
Get all related links from a URL.
| Parameter | Required | Description |
|---|---|---|
url | Yes | URL to get sitemap |
reasoning
Deep thinking and complex problem solving with DeepSeek R1.
| Parameter | Required | Description |
|---|---|---|
content | Yes | The question or problem |
trending
Get trending topics from popular platforms.
| Parameter | Required | Default | Description |
|---|---|---|---|
search_service | Yes | - | github, hackernews |
max_results | No | 10 | Number of items |
Version History
- v0.3.0: Remote MCP support via Streamable HTTP; per-session API key authentication
- v0.2.0: Fallback
.envsupport for LibreChat integration - v0.1.8: X (Twitter) and Reddit search services
- v0.1.7: Trending tool for GitHub and Hacker News
- v0.1.6: Wikipedia search service
- v0.1.5: New search parameters and services (arxiv, wechat, bilibili, imdb)
- v0.1.4: Reasoning tool with DeepSeek R1
- v0.1.3: News search
- v0.1.2: Sitemap
- v0.1.1: Web crawling
- v0.1.0: Initial release
License
MIT
FAQ
- What is the Search1API MCP server?
- Search1API is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Search1API?
- This profile displays 30 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.6 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Web Research & Information Gathering
Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Content Monitoring & Alerts
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Data Extraction & Aggregation
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
API-less Integration
Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Implementation Guide▌
Prerequisites
- ›Claude Desktop or Cursor with MCP support
- ›Understanding of web scraping ethics and robots.txt
- ›Rate limiting awareness to avoid overwhelming target sites
- ›Knowledge of legal restrictions on data collection
Time Estimate
20-40 minutes including configuration and testing
Installation Steps
- 1.Install web automation MCP server via npm or pip
- 2.Configure allowed domains and rate limits in MCP config
- 3.Test with simple fetch: 'Get content from example.com'
- 4.Progress to extraction: 'Extract all product prices from this page'
- 5.Set up monitoring: 'Check this URL daily for changes'
- 6.Parse structured data: 'Create CSV from this table'
- 7.Respect robots.txt and rate limits always
Troubleshooting
- ⚠403 Forbidden: Website blocks bots—respect their wishes, use official API instead
- ⚠Rate limit errors: Slow down requests, add delays between fetches
- ⚠Stale data: Target site changed HTML structure—update selectors
- ⚠Timeout errors: Site is slow or blocking—increase timeout, try different user agent
- ⚠JavaScript-rendered content: Use headless browser MCP servers for dynamic sites
Best Practices▌
✓ Do
- +Check robots.txt and respect crawl rules
- +Rate limit requests: 1-2 requests/second maximum
- +Use official APIs when available instead of scraping
- +Identify your bot with descriptive user agent
- +Cache results to minimize repeated requests
- +Handle errors gracefully with retries and fallbacks
- +Validate extracted data for accuracy
✗ Don't
- −Don't scrape sites that explicitly forbid it (robots.txt, ToS)
- −Don't overwhelm servers with rapid requests—use rate limiting
- −Don't scrape personal data without consent and legal basis
- −Don't ignore copyright on extracted content
- −Don't assume HTML structure is stable—handle changes
- −Don't use scraped data for commercial purposes without permission
💡 Pro Tips
- ★Use CSS selectors or XPath for robust data extraction
- ★Set up monitoring alerts for extraction failures (structure changed)
- ★Implement exponential backoff for retries on failures
- ★Store raw HTML for reprocessing if extraction logic changes
- ★Combine with data analysis tools for insights from extracted data
- ★Consider using official APIs or RSS feeds as more stable alternatives
Technical Details▌
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
- HTTP/HTTPS
- WebSocket (for real-time sites)
- Puppeteer/Playwright (for JavaScript sites)
Compatibility
- Static HTML sites
- JavaScript-rendered SPAs (with headless browser)
- REST APIs
- GraphQL endpoints
When to Use This▌
✓ Use When
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid When
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.
Integration▌
- →Scheduled monitoring with change detection
- →Multi-source data aggregation pipelines
- →Fallback to web scraping when API rate limits hit
- →Headless browser for JavaScript-heavy sites
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.6★★★★★30 reviews- ★★★★★Ama Johnson· Dec 24, 2024
Search1API is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Rahul Santra· Nov 19, 2024
Search1API is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Meera Harris· Nov 15, 2024
We evaluated Search1API against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Pratham Ware· Oct 10, 2024
Search1API has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Meera Rahman· Oct 6, 2024
I recommend Search1API for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Sakshi Patil· Sep 25, 2024
We evaluated Search1API against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Arjun Anderson· Sep 13, 2024
Strong directory entry: Search1API surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Arjun White· Sep 1, 2024
Search1API is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Arjun Thomas· Aug 20, 2024
According to our notes, Search1API benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Chaitanya Patil· Aug 16, 2024
I recommend Search1API for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
showing 1-10 of 30