crawl
Extract the readable title and full text from a public URL supplied by the user or returned by search.
LABSCO SUMMARY
Search and then read the page, inside the same tool call.
crawl_results is the parameter that changes how this gets used: rather than a search followed by one fetch per promising result, the top hits come back with their content already pulled, and each successful crawl adds 1 credit to the base 1-credit request. The hosted endpoint means nothing to install for web clients, and because discovery answers without a credential you can see the tool surface before deciding to sign in.
What it is
The official MCP server for Search1API: web search across a wide set of engines and verticals, news search, single-page crawling, sitemap discovery, and trending topics. Tool discovery is answered without a credential, so a client can inspect the server before anyone signs in.
What you get
- search — web results with a citable id, title, and url, over google, bing, duckduckgo, yahoo, x, reddit, github, youtube, arxiv, wechat, bilibili, imdb, and wikipedia
- news — the same shape against google, bing, duckduckgo, yahoo, and hackernews
- crawl — the full content of a URL, including one that came back from a search result
- sitemap — every related link discoverable from a URL
- trending — what is currently rising on github or hackernews
- crawl_results on search and news, which pulls full page content for the top hits inline instead of leaving the agent to fetch them
- Include and exclude site lists, and a time_range of day, month, or year
Requirements
A Search1API credential for tool calls; discovery works without one. The hosted endpoint is https://mcp.search1api.com/mcp over Streamable HTTP — connect with OAuth 2.1 where your client supports it, or send an Authorization Bearer header with a key from the Search1API dashboard. The URL query-parameter form still works but is the legacy path, and it puts the key into URLs, logs, and shell history. To run it locally instead, use Node.js 20 or newer with npx -y search1api-mcp and SEARCH1API_KEY set. Self-hosted HTTP deployments behind a proxy add their internal hostnames to MCP_ALLOWED_HOSTS, and browser-based clients add their origins to MCP_ALLOWED_ORIGINS.
Setup effort
One command plus a key — claude mcp add --transport http search1api https://mcp.search1api.com/mcp, then supply credentials
USE CASES
01
Researching a topic and reading the sources, not just the snippets
Search, then pull the full text of the results worth reading — or ask for the top hits crawled inline in the first call.
02
Following a story as it develops
News search bounded to the last day or month, narrowed to or away from specific sites.
03
Seeing what shipped in your ecosystem this week
Read what is trending on GitHub or Hacker News, then open the ones that matter.
04
Mapping a documentation site before ingesting it
Discover every related link from one entry URL, then crawl the pages you actually want.
05
Searching inside one community rather than the whole web
Point the search at reddit, github, arxiv, or wikipedia instead of a general engine.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
news
Search current news when the user asks about recent events, announcements, or coverage. Returns citable article results with title, URL, snippet, and optional extracted text.
search
Search 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.
sitemap
Discover related public links from a page or domain when the user wants to explore a site's structure or available pages.
trending
List currently trending repositories or stories from GitHub or Hacker News when the user asks what is popular now.
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected. search_service switches search between sources including google, bing, duckduckgo, reddit, github, youtube, arxiv and wikipedia. The reasoning tool was removed in v0.3.1.
Requires
A client that can reach a remote MCP server over HTTP
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
claude mcp add
TERMINAL
claude mcp add --transport http search1api https://mcp.search1api.com/mcpHosted endpoint
ENDPOINT URL
https://mcp.search1api.com/mcpAdd this hosted endpoint to your MCP client, then sign in.
MCP Clients
Claude.ai
Custom connector url: https://mcp.search1api.com/mcp
Cursor
CURSOR · JSON
{
"mcpServers": {
"search1api": {
"url": "https://mcp.search1api.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_SEARCH1API_KEY>"
}
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"search1api": {
"type": "http",
"url": "https://mcp.search1api.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_SEARCH1API_KEY>"
}
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport http search1api https://mcp.search1api.com/mcp --header "Authorization: Bearer <YOUR_SEARCH1API_KEY>"Windsurf
WINDSURF · JSON
{
"mcpServers": {
"search1api": {
"serverUrl": "https://mcp.search1api.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_SEARCH1API_KEY>"
}
}
}
}Any MCP client — local stdio
ANY MCP CLIENT — LOCAL STDIO · JSON
{
"mcpServers": {
"search1api": {
"command": "npx",
"args": [
"-y",
"search1api-mcp"
],
"env": {
"SEARCH1API_KEY": "<YOUR_SEARCH1API_KEY>"
}
}
}
}
