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