Desearch
REMOTE · MCP.DESEARCH.AI · 2 COMPONENTS · SCANNED OCT 5
AI search, X search, web search, page extraction, and X trends.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1614 tokens (~107/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Desearch MCP server?
Desearch is a hosted endpoint at https://mcp.desearch.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.desearch.ai
claude mcp add --transport http desearch-ai-mcp-desearch 'https://mcp.desearch.ai/mcp'
{
"mcpServers": {
"desearch-ai-mcp-desearch": {
"url": "https://mcp.desearch.ai/mcp"
}
}
} {
"servers": {
"desearch-ai-mcp-desearch": {
"type": "http",
"url": "https://mcp.desearch.ai/mcp"
}
}
} [mcp_servers.desearch-ai-mcp-desearch] url = "https://mcp.desearch.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"desearch-ai-mcp-desearch": {
"type": "remote",
"url": "https://mcp.desearch.ai/mcp",
"enabled": true
}
}
} openclaw mcp add desearch-ai-mcp-desearch --url 'https://mcp.desearch.ai/mcp' --transport streamable-http
mcp_servers:
desearch-ai-mcp-desearch:
url: "https://mcp.desearch.ai/mcp" {
"McpServers": {
"desearch-ai-mcp-desearch": {
"Transport": "http",
"Url": "https://mcp.desearch.ai/mcp"
}
}
} assistant mcp add desearch-ai-mcp-desearch -t streamable-http -u 'https://mcp.desearch.ai/mcp'
{
"mcpServers": {
"desearch-ai-mcp-desearch": {
"type": "http",
"url": "https://mcp.desearch.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Oct 26 0
- Schema quality: pass → fail ▼ functional
- Server version: 0.1.3 → 0.1.4 functional
- “ai-search” reworded the description of “tools” cosmetic
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Oct 26 +42
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- Tool “x-search” rewrote its description, which is the text the model reads security
- Tool “ai-search” rewrote its description, which is the text the model reads security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- Server version: 0.1.2 → 0.1.3 functional
- “ai-search” reworded the description of “model” cosmetic
- 1 Oct 26 36
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Oct 2026 · Probed https://mcp.desearch.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.desearch.ai | CN=YR1,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | RSA 2048 | SHA256-RSA | 6b53e8e40989cd3f422433c79363bc89170 |
| SANs: mcp.desearch.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.desearch.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| desearch.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.desearch.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.desearch.ai/mcp | HTTPS enforced | 308 | https://mcp.desearch.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ai-search AI Search ~337
AI search and analysis on web using Desearch AI
| Name | Type | Req | Description |
|---|---|---|---|
| date_filter | string | – | Deprecated relative window; prefer start_date/end_date. Example: 'PAST_WEEK' |
| end_date | string | – | End of the date range in UTC (YYYY-MM-DDTHH:MM:SSZ). Use with start_date. |
| exclude_domains | array | – | Drop Web Search results from these domains, example: ['pinterest.com'] |
| include_domains | array | – | Restrict Web Search results to these domains, example: ['bbc.com', 'reuters.com'] |
| model | string | – | Model to use for the search: NOVA (default) or ORBIT. |
| prompt | string | yes | Question, example: 'What is the latest news on AI?' |
| result_type | string | – | ONLY_LINKS returns links only; LINKS_WITH_FINAL_SUMMARY adds an AI summary. Link arrays are kept under whichever key the API uses, along with billing fields. ONLY_LINKS still depends on the API to in… |
| start_date | string | – | Start of the date range in UTC (YYYY-MM-DDTHH:MM:SSZ). Use with end_date. |
| tools | array | – | Source ids sent to POST /desearch/ai/search. Short ids: 'web', 'twitter', 'arxiv', 'wikipedia', 'hackernews', 'reddit'. Legacy labels such as 'Web Search', 'ArXiv Search', 'Wikipedia Search', 'Hacker… |
No output schema declared.
No examples provided.
extract Extract Page Content ~103
Extract a public URL and return its content as plain text or HTML using Desearch. Preferred over web-crawl for new integrations.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Content format to return: 'html' or 'text'. |
| js | boolean | – | Render JavaScript before reading the page. |
| url | string | yes | Public URL to read, example: 'https://desearch.ai' |
| wait | number | – | Post-load wait in milliseconds when JavaScript rendering is enabled. |
No output schema declared.
No examples provided.
web-crawl Crawl Web Page (Legacy) ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Content format to return: 'html' or 'text'. |
| js | boolean | – | Render JavaScript before reading the page. |
| url | string | yes | Public URL to read, example: 'https://desearch.ai' |
| wait | number | – | Post-load wait in milliseconds when JavaScript rendering is enabled. |
No output schema declared.
No examples provided.
web-links-search Web Links Search ~108
Search the web for links using Desearch. Only the web source is accepted.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Results to return per source. Min 10. Max 200. |
| prompt | string | yes | Search query prompt, example: 'open source browser automation tools' |
| tools | array | – | Sources to search. Only 'web' is accepted; other ids are rejected before the API call. 'Web Search' is accepted and rewritten to 'web'. Defaults to ['web']. |
No output schema declared.
No examples provided.
web-search Web Search ~74
SERP-style web search using Desearch. Returns ranked titles, links, and snippets.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query, example: 'latest news on AI' |
| start | integer | – | How many results to skip for pagination (0, 10, 20, ...). Omit for the first page. |
No output schema declared.
No examples provided.
x-links-search X Links Search ~68
AI search for X (Twitter) post links using Desearch. Returns links from posts that match the prompt.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Results to return. Min 10. Max 200. |
| prompt | string | yes | Search query prompt, example: 'Bittensor subnet updates' |
No output schema declared.
No examples provided.
x-post-by-id Get X Post by ID ~43
Fetch a single X (Twitter) post by its ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique ID of the post, example: '1234567890' |
No output schema declared.
No examples provided.
x-post-replies Get X Post Replies ~72
Fetch replies to an X (Twitter) post, with an optional keyword query.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of posts to retrieve (1-100). |
| post_id | string | yes | The ID of the post to fetch replies for. |
| query | string | – | Advanced search query to filter replies. |
No output schema declared.
No examples provided.
x-post-retweeters List X Post Retweeters ~63
List users who retweeted an X (Twitter) post. Pass cursor to page through more users.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor for pagination from a previous response. |
| id | string | yes | The ID of the post to get retweeters for. |
No output schema declared.
No examples provided.
x-posts-by-urls Get X Posts by URLs ~49
Fetch full X (Twitter) posts for a list of post URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | Post URLs to fetch, example: ['https://x.com/user/status/123'] |
No output schema declared.
No examples provided.
x-posts-by-user Search X Posts by User ~77
Search X (Twitter) posts by a specific user, with an optional keyword query.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of posts to retrieve (1-100). |
| query | string | – | Advanced search query to filter this user's posts. |
| user | string | yes | User to search for, example: 'elonmusk' |
No output schema declared.
No examples provided.
x-search X Search ~275
Search X (Twitter) using Desearch AI. Optional filters narrow by user, date, language, verification, media, and engagement. Sort stays Top.
| Name | Type | Req | Description |
|---|---|---|---|
| blue_verified | boolean | – | Filter for blue-checkmark verified users. |
| count | number | – | Number of search results to return (default: 20), max is 100 |
| end_date | string | – | End date in UTC (YYYY-MM-DD). Use with start_date. |
| is_image | boolean | – | Include only posts with images. |
| is_quote | boolean | – | Include only posts that are quotes. |
| is_video | boolean | – | Include only posts with video. |
| lang | string | – | Language code, example: 'en', 'es', 'fr' |
| min_likes | – | – | Minimum number of likes. |
| min_replies | – | – | Minimum number of replies. |
| min_retweets | – | – | Minimum number of retweets. |
| query | string | yes | Twitter advanced search query, example: 'from:elonmusk since:2023-01-01 min_replies:10' |
| start_date | string | – | Start date in UTC (YYYY-MM-DD). Use with end_date. |
| user | string | – | User to search for, example: 'elonmusk' |
| verified | boolean | – | Filter for verified users. |
No output schema declared.
No examples provided.
x-trends Get X Trends ~70
Retrieve trending topics on X (Twitter) for a location by its WOEID using Desearch.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of trends to return (30-100). |
| woeid | integer | yes | WOEID of the location, example: 23424977 for the United States. |
No output schema declared.
No examples provided.
x-user-posts Get X User Timeline ~63
Retrieve a user's X (Twitter) timeline posts by username. Pass cursor to page through more posts.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor for pagination from a previous response. |
| username | string | yes | Username to fetch posts for, example: 'elonmusk' |
No output schema declared.
No examples provided.
x-user-replies Get X User Replies ~82
Fetch posts and replies by an X (Twitter) user, with an optional keyword query.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of posts to retrieve (1-100). |
| query | string | – | Advanced search query to filter this user's posts and replies. |
| user | string | yes | Username of the user to search for, example: 'elonmusk' |
No output schema declared.
No examples provided.
What is the Desearch MCP server?
Desearch is an MCP server listed in the public MCP registry as io.github.Desearch-ai/mcp-desearch. AI search, X search, web search, page extraction, and X trends. This page covers its hosted endpoint (https://mcp.desearch.ai/mcp).
Is the Desearch MCP server safe to use?
Desearch scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Desearch MCP server expose?
Desearch exposes 15 tools: ai-search, x-search, web-search, web-links-search, x-links-search, and 10 more. Their descriptions and schemas cost roughly 1,614 tokens of context every time the server is loaded.
Does the Desearch MCP server require authentication?
Yes. Desearch asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Desearch MCP server still maintained?
Desearch is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.