cursor-search-mcp
Related Servers
Alternatives to cursor-search-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables MCP-compatible agents to perform web searches via the agent-web-search engine, returning ranked results with sources.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and LLM apps to run live web searches and fetch public web pages as Markdown, returning structured search results and page content through MCP clients.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI agents to search the web and obtain cited answers, step-by-step reasoning, and deep research through hosted APIs.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to search the web and fetch public web pages via DeepSeek's Search and Fetch APIs, returning ranked results and Markdown page content for agent use.MIT
- AlicenseCqualityBmaintenanceEnables MCP clients to run web searches and optionally fetch webpages through Moonshot's open platform API, using a configured API key.2118 npmMIT
- AlicenseAqualityCmaintenanceEnables web search and page fetching through the DeepSeek Search and Fetch APIs, exposing search and fetch tools to MCP clients. Supports paginated content retrieval with cursors so long pages can be read in chunks without repeating upstream requests.252 npmAGPL 3.0
TDQS
Scored across 4 tools
The three auth-related tools have distinct roles: status check, OAuth initiation, and OAuth completion wait. An agent could briefly hesitate between cursor_login and cursor_oauth_login when unauthenticated, but the descriptions clarify the intended sequence.
All tools use a consistent cursor_ prefix and snake_case, with auth tools following a clear cursor_oauth_* subpattern. cursor_login and cursor_web_search are slightly less uniform in verb style but remain readable and predictable.
Four tools is reasonable for a narrow web-search server with an unavoidable OAuth lifecycle. The set is slightly auth-heavy (three auth tools to one search tool), but that reflects a legitimate setup flow rather than unnecessary bloat.
The auth lifecycle is well covered with status, initiation, and completion tools, and web search is present. Minor gaps like logout/token clearing or richer search options exist, but core workflows are covered.