by fatwang2
Discover Search1API for web searches, news API, and newspaper API capabilities. Power content extraction and stay inform
Provides web search, news queries, and content extraction through the Search1API service. Connects AI assistants to real-time web information and crawling capabilities.
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.
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.
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.
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
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
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
Share your MCP server with the developer community
Search1API is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Search1API is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We evaluated Search1API against two servers with overlapping tools; this profile had the clearer scope statement.
Search1API has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
I recommend Search1API for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We evaluated Search1API against two servers with overlapping tools; this profile had the clearer scope statement.
Strong directory entry: Search1API surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Search1API is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
According to our notes, Search1API benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
I recommend Search1API for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
showing 1-10 of 30
The official MCP server for Search1API — web search, news, crawling, and more in one API.
No installation required. Just configure your MCP client with the remote URL and your API key.
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 |
{
"mcpServers": {
"search1api": {
"url": "https://mcp.search1api.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_SEARCH1API_KEY"
}
}
}
}
Settings > Connectors > Add custom connector:
https://mcp.search1api.com/mcp?apiKey=YOUR_SEARCH1API_KEY
{
"mcpServers": {
"search1api": {
"url": "https://mcp.search1api.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_SEARCH1API_KEY"
}
}
}
}
{
"servers": {
"search1api": {
"type": "http",
"url": "https://mcp.search1api.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_SEARCH1API_KEY"
}
}
}
}
claude mcp add --transport http search1api https://mcp.search1api.com/mcp \
--header "Authorization: Bearer YOUR_SEARCH1API_KEY"
{
"mcpServers": {
"search1api": {
"serverUrl": "https://mcp.search1api.com/mcp?apiKey=YOUR_SEARCH1API_KEY"
}
}
}
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
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"
}
}
}
}
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 |
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 |
Extract content from a URL.
| Parameter | Required | Description |
|---|---|---|
url | Yes | URL to crawl |
Get all related links from a URL.
| Parameter | Required | Description |
|---|---|---|
url | Yes | URL to get sitemap |
Deep thinking and complex problem solving with DeepSeek R1.
| Parameter | Required | Description |
|---|---|---|
content | Yes | The question or problem |
Get trending topics from popular platforms.
| Parameter | Required | Default | Description |
|---|---|---|---|
search_service | Yes | - | github, hackernews |
max_results | No | 10 | Number of items |
.env support for LibreChat integrationMIT
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
Prerequisites
Time Estimate
20-40 minutes including configuration and testing
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
Compatibility
✓ 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.