mcpbeat Sign in

Desearch MCP Server

by desearch-ai Your server? Claim it
not responding

Desearch is listed as active in the registry but did not answer our last check. 88 installs a week from npm. It exposes 15 tools. Last commit 5 Oct 2026.

AI search, X search, web search, page extraction, and X trends.

Installs per day peak 281 · avg 71 · +146% w/w
a month agotoday
Uptime history 15 days of history · worst day 0%
15 days agonow
39.1%
Uptime 24h
36 of 92 checks
15
Tools
read from the server
239 ms
Response time
average over 24h
88
Installs / week
npm and PyPI

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 October 2026. No other catalogue keeps this.

8 Oct 2 tool descriptions were rewritten ai-search, x-search
8 Oct a tool changed the parameters it asks for ai-search

Desearch does not always answer

Over the last week it answered 8.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add mcp-desearch --transport http https://mcp.desearch.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-desearch": {
      "url": "https://mcp.desearch.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-desearch]
url = "https://mcp.desearch.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-desearch": {
      "url": "https://mcp.desearch.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp-desearch": {
      "url": "https://mcp.desearch.ai/mcp"
    }
  }
}

This one needs environment variables set before it will start: DESEARCH_API_KEY (Desearch API key from https://console.desearch.ai/api-keys). The author declared them in the registry entry; get the values from the project itself.

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

post
x-post-by-id
Fetch a single X (Twitter) post by its ID.
x-post-replies
Fetch replies to an X (Twitter) post, with an optional keyword query.
x-post-retweeters
List users who retweeted an X (Twitter) post. Pass cursor to page through more users.
web
web-crawl
Crawl a public URL and return its content as plain text or HTML on the legacy Desearch /web/crawl route. The SDK marks webCrawl deprecated in favor of extract; this tool stays for parity with that route. Prefer extract for new integrations.
web-links-search
Search the web for links using Desearch. Only the web source is accepted.
web-search
SERP-style web search using Desearch. Returns ranked titles, links, and snippets.
posts
x-posts-by-urls
Fetch full X (Twitter) posts for a list of post URLs.
x-posts-by-user
Search X (Twitter) posts by a specific user, with an optional keyword query.
user
x-user-posts
Retrieve a user's X (Twitter) timeline posts by username. Pass cursor to page through more posts.
x-user-replies
Fetch posts and replies by an X (Twitter) user, with an optional keyword query.
ai
ai-search
AI search and analysis on web using Desearch AI
extract
extract
Extract a public URL and return its content as plain text or HTML using Desearch. Preferred over web-crawl for new integrations.
links
x-links-search
AI search for X (Twitter) post links using Desearch. Returns links from posts that match the prompt.
trends
x-trends
Retrieve trending topics on X (Twitter) for a location by its WOEID using Desearch.
x
x-search
Search X (Twitter) using Desearch AI. Optional filters narrow by user, date, language, verification, media, and engagement. Sort stays Top.

Endpoints

URLTransportStateLatencyChecked
https://mcp.desearch.ai/mcp streamable-http answering 45 ms 3 min ago

Alternatives to Desearch

same job, measured the same way
mcp-retriever
by keiranhaax

One MCP server for web search, page extraction, and cited research.

100 installs/wk local only
AIsa Web Search & Research
by aisa

Web search and page extraction across several independent search providers.

answering
You.com Web Access & AI
by youdotcom-oss

Web search, AI agent, and content extraction via You.com APIs

6 393 installs/wk 6 tools answering
Trawlia
by trawlia

Web search and page extraction for agents, returned as readable text rather than raw JSON.

25 installs/wk local only
P
Payx Tavily Search
by swathi-muralisrinivasan

FastMCP server for Tavily search API with web search and content extraction

local only
Websharp
by jgador

Search the web and extract article text for LLMs.

local only
Baizhi Cloud Agent Toolkit
by ct-jaryn

Web search, page extraction, visual tools and developer utilities through Baizhi Cloud.

answering
search-rotation
by robin-bially

MCP server for web search and page extraction across the free tiers of several providers

277 installs/wk local only

Desearch — questions

Answers built from our own checks of this server.

What can Desearch do?
It exposes 15 tools, read directly from the server on our last check. Among them: ai-search, extract, web-crawl, web-links-search, web-search, x-links-search and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Desearch mostly used for?
Its tools cluster around web, post and user. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Desearch working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 36 of 92 checks got a reply (39.1%), average response time 239 ms. The bar chart above shows every period we have measured.
The registry lists Desearch as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Desearch?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Desearch need an API key?
No. Desearch completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Desearch?
It answers our handshake in 239 ms on average, which is faster than 54% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Desearch?
The npm package desearch-mcp-server was installed 88 times in the last week. Week over week that is +146%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Desearch open source?
Yes — it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.