Search1api MCP vs LinkupPlatform Linkup MCP Server

A side-by-side look at the Search1api MCP and LinkupPlatform Linkup MCP Server 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 requiredLinkupPlatform Linkup MCP Server logoLinkupPlatform Linkup MCP ServerSearch & Data Extraction · Local subprocess (stdio)Search the web in real time to get trustworthy, source-backed answers. Find the latest news and co…65GreatAuth: not declared

Verdict: choose Search1api MCP for search & data extraction work as a local process; choose LinkupPlatform Linkup MCP Server 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

LinkupPlatform Linkup MCP Server logoChoose LinkupPlatform Linkup MCP Server when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: LINKUP_API_KEY.
  • You want tools like linkup-search, linkup-research, linkup-get-research.
Explore LinkupPlatform Linkup MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSearch1api MCP logoSearch1api MCPLinkupPlatform Linkup MCP Server logoLinkupPlatform Linkup MCP Server
CategorySearch & Data ExtractionSearch & Data Extraction
Quality signal67/100 · Great65/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNot declared
PricingPaid serviceNot declared
Required env varsSEARCH1API_KEYLINKUP_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars17329
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools54

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.

LinkupPlatform Linkup MCP Server tools 4

  • linkup-searchSearch the web in real time using Linkup to retrieve current information, facts, and news from trusted sources. Use this tool for: real-time data (weather, stocks, sports scores, events), breaking news, current events, recent research, product information, up-to-date prices, schedules, and any information not available in your knowledge base. Returns comprehensive content from the most relevant sources.
  • linkup-researchSubmits an autonomous Linkup research task: an agent that investigates the web to answer questions a single search query cannot resolve, returning a synthesized, cited answer. Use for verified answers to precise questions, focused investigations of a defined subject, or broad multi-angle reports. This is async and long-running (can take several minutes): it does not return the final result. It returns immediately with a task "id" and a "status" of "pending". Poll "linkup-get-research" with that id until the status is "completed" (result in "output") or "failed" (reason in "error"). For quick, direct answers prefer "linkup-search" instead.
  • linkup-get-researchRetrieve the current state of a Linkup research task previously started with "linkup-research". Returns the task object with its "status". While the status is "pending" or "processing", keep polling every few seconds until it reaches a terminal state; polling faster than once per second is rate-limited. When "completed", the result is in the "output" field; when "failed", the reason is in the "error" field.
  • linkup-fetchFetch a URL and return the content of the page. If you are unable to fetch the page content, might be worth trying to render the JavaScript content.

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"
      }
    }
  }
}

LinkupPlatform Linkup MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "linkupplatform-linkup-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "linkup-mcp-server"
      ],
      "env": {
        "LINKUP_API_KEY": "YOUR_LINKUP_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Search1api MCP is categorized under Search & Data Extraction and uses a local stdio subprocess. LinkupPlatform Linkup MCP Server belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Search1api MCP for search & data extraction work and LinkupPlatform Linkup MCP Server 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. LinkupPlatform Linkup MCP Server 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 linkupplatform-linkup-mcp-server 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. LinkupPlatform Linkup MCP Server has 65/100 (Great) with 1 views, 0 installs and 29 GitHub stars.