search_status — DejaBars MCP Tool Read-only

search_status (search status) is one of 17 tools on the DejaBars MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call search_status from your client

Claude Code DejaBars search_status run in your project directory
Claude Desktop DejaBars search_status ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor DejaBars search_status ~/.cursor/mcp.json
VS Code DejaBars search_status .vscode/mcp.json
Zed DejaBars search_status ~/.config/zed/settings.json
Windsurf DejaBars search_status ~/.codeium/windsurf/mcp_config.json
Cline DejaBars search_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI DejaBars search_status ~/.gemini/settings.json
Grok DejaBars search_status .mcp.json (in your project root)
ChatGPT DejaBars search_status Settings → Connectors → Advanced → Developer mode
Claude.ai DejaBars search_status Settings → Connectors → Add custom connector
LangChain DejaBars search_status pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http pattern-search https://dejabars.com/api/v1/mcp

Other tools on this server

agent_capabilities
search_submit
search_result
quota_status
list_coins
market_klines
catalog_list
catalog_save
analytics_schema
analytics_report
analytics_quote
analytics_fast_verify
analytics_config_list
analytics_config_save
analytics_config_delete
analytics_run

This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

DejaBars MCP server