Home / MCP registry index / io.github.jamboree777/nightwatch

NightWatch Live Intelligence

io.github.jamboree777/nightwatch in the official MCP registry. Endpoint https://nightwatch-v1-api.onrender.com/mcp. Source: github.com/jamboree777/nightwatch-skills.

The registry describes it as: Real-time crypto asset intel for trading AIs: liquidity grades, transfer routes, spreads, BTI

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http nightwatch https://nightwatch-v1-api.onrender.com/mcp

{
  "mcpServers": {
    "nightwatch": {
      "url": "https://nightwatch-v1-api.onrender.com/mcp"
    }
  }
}

code --add-mcp '{"name":"nightwatch","type":"http","url":"https://nightwatch-v1-api.onrender.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

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 agent_inbox sbt_name sbt_naming_window tasks_browse task_claim task_submit_proof hive_list_rooms hive_read_room hive_activity hive_search hive_post hive_desk_open hive_attach get_price get_price_stats get_kg_facts obsidian_state obsidian_quote get_rules strategy_spec_validate strategy_spec_paper route_intent guardrail_ratings guardrail_subindices forge_signals forge_signal_plan forge_signal_publish forge_mirror_consent forge_mirror_revoke forge_signal_fill

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-jamboree777-nightwatch/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-jamboree777-nightwatch)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers · Finance and markets MCP servers