英语 |简体中文

统一的实时搜索MCP服务器，支持通用网页搜索、垂直域搜索、并行批处理搜索和全页URL内容提取。

特色

• 通用网络搜索 — 开放式自然语言查询
• 垂直领域搜索 — 涵盖金融、学术、安全、法律、代码等领域的结构化查询
• 并行批处理搜索 — 在一次调用中执行多个独立查询
• URL 内容提取 — 以 Markdown 方式获取并提取全页内容
• 匿名访问 — 无需API密钥即可工作（速率限制较低）

API 密钥配置

API密钥是可选但推荐。没有密钥，所有功能仍通过匿名访问以较低速率使用。

注册API密钥（推荐）

代理只需一次通话即可注册用户并获取API密钥——无需验证码，无需手动注册。向用户索要真实邮箱地址：它会成为账户用户名。

成功响应（code: 0）返回账户信息和一次性明文API密钥：

配额字段如rate_limit是账户特定的响应值;不要将示例视为固定计划。

AnySearch MCP Server

English | 简体中文

Unified real-time search MCP server supporting general web search, vertical domain search, parallel batch search, and full-page URL content extraction.

Features

• General Web Search — open-ended natural language queries
• Vertical Domain Search — structured queries across finance, academic, security, legal, code, and more
• Parallel Batch Search — execute multiple independent queries in one call
• URL Content Extraction — fetch and extract full page content as Markdown
• Anonymous Access — works without an API key (with lower rate limits)

API Key Configuration

An API key is optional but recommended. Without a key, all features still work via anonymous access with lower rate limits.

Register for an API Key (Recommended)

The agent can register the user and obtain an API key in a single call — no verification code, no manual signup. Ask the user for a real email address: it becomes the account username.

curl -s -X POST "https://api.anysearch.com/v1/auth/email/register" \
  -H "Content-Type: application/json" \
  -d '{"email": "[email protected]"}'

Success response (code: 0) returns the account info and a one-time plaintext API key:

{
  "code": 0,
  "message": "success",
  "data": {
    "username": "[email protected]",
    "email": "[email protected]",
    "login_url": "https://www.anysearch.com/login",
    "api_key": {
      "id": "key_xxxxxxxx",
      "key": "as_sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
      "key_prefix": "as_sk_xxxxxx...",
      "name": "default",
      "rate_limit": 100,
      "quota_limit": 0,
      "expires_at": null,
      "created_at": "2026-06-23T10:23:00Z"
    }
  }
}

Quota fields such as rate_limit are account-specific response values; do not treat the example as a fixed plan.

On success the agent MUST:

1. Put data.api_key.key into the MCP server config as the Authorization: Bearer value (and/or set ANYSEARCH_API_KEY) — it is shown only once (it can also be retrieved later from the dashboard).
2. Tell the user their username (= email) and the login_url.

Errors can be expressed through the HTTP status, application-level code, or message; do not assume every error uses code: -1: