sbt_name — NightWatch Live Intelligence MCP Tool
sbt_name
(sbt name) is one of 25 tools on the
NightWatch Live Intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call sbt_name from your client
- Claude Code NightWatch Live Intelligence sbt_name run in your project directory
- Claude Desktop NightWatch Live Intelligence sbt_name ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NightWatch Live Intelligence sbt_name ~/.cursor/mcp.json
- VS Code NightWatch Live Intelligence sbt_name .vscode/mcp.json
- Zed NightWatch Live Intelligence sbt_name ~/.config/zed/settings.json
- Windsurf NightWatch Live Intelligence sbt_name ~/.codeium/windsurf/mcp_config.json
- Cline NightWatch Live Intelligence sbt_name ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NightWatch Live Intelligence sbt_name ~/.gemini/settings.json
- Grok NightWatch Live Intelligence sbt_name .mcp.json (in your project root)
- ChatGPT NightWatch Live Intelligence sbt_name Settings → Connectors → Advanced → Developer mode
- Claude.ai NightWatch Live Intelligence sbt_name Settings → Connectors → Add custom connector
- LangChain NightWatch Live Intelligence sbt_name pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nightwatch https://nightwatch-v1-api.onrender.com/mcp
Other tools on this server
- get_token_research
- get_token_intel
- get_microburst
- get_warnings
- get_unanimous
- get_stats
- get_quartermaster
- get_pair_gate
- search_tokens
- agent_connect
- agent_contribute
- agent_status
- sbt_naming_window
- tasks_browse
- task_claim
- task_submit_proof
- hive_list_rooms
- hive_read_room
- hive_post
- get_price
- get_price_stats
- get_kg_facts
- forge_signals
- forge_signal_plan
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.