company_signals — BORME API MCP Tool
company_signals
(company signals) is one of 13 tools on the
BORME API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call company_signals from your client
- Claude Code BORME API company_signals run in your project directory
- Claude Desktop BORME API company_signals ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BORME API company_signals ~/.cursor/mcp.json
- VS Code BORME API company_signals .vscode/mcp.json
- Zed BORME API company_signals ~/.config/zed/settings.json
- Windsurf BORME API company_signals ~/.codeium/windsurf/mcp_config.json
- Cline BORME API company_signals ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BORME API company_signals ~/.gemini/settings.json
- Grok BORME API company_signals .mcp.json (in your project root)
- ChatGPT BORME API company_signals Settings → Connectors → Advanced → Developer mode
- Claude.ai BORME API company_signals Settings → Connectors → Add custom connector
- LangChain BORME API company_signals pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http borme-mcp https://mcp.bormeapi.com/mcpOther tools on this server
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.