Is io.github.jamboree777/nightwatch up? Live MCP status

Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-06-18.

A stock client connected with no credential and negotiated 2025-06-18. Use it.

Outcomeusable
HTTP status200
Protocol version2025-06-18
Server says it isnightwatch 1.5.0
Answered in559 ms
Endpoint checkedhttps://nightwatch-v1-api.onrender.com/mcp
Checked

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

A2A agent cardNot published (HTTP 404).
/.well-known/agent-card.json
MCP server card (SEP-2127)Not published (HTTP 404).
https://nightwatch-v1-api.onrender.com/mcp/server-card
MCP server card (SEP-1649 location)Not published (HTTP 404).
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryNot published (HTTP 404).
/.well-known/http-message-signatures-directory

Read at https://nightwatch-v1-api.onrender.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 31 tools: agent_connect, agent_contribute, agent_status, forge_signal_plan, forge_signals, get_kg_facts, get_microburst, get_pair_gate, get_price, get_price_stats, get_quartermaster, get_rules, get_stats, get_token_intel, get_token_research, get_unanimous, get_warnings, guardrail_ratings, guardrail_subindices, hive_list_rooms, hive_post, hive_read_room, obsidian_quote, obsidian_state, route_intent, sbt_name, sbt_naming_window, search_tokens, task_claim, task_submit_proof, tasks_browse.

Its tools changed between 2026-09 and 2026-10:

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Registry nameio.github.jamboree777/nightwatch
TitleNightWatch Live Intelligence
DescriptionReal-time crypto asset intel for trading AIs: liquidity grades, transfer routes, spreads, BTI
Endpointhttps://nightwatch-v1-api.onrender.com/mcp
Publisher repositoryhttps://github.com/jamboree777/nightwatch-skills
Version1.5.0
Listing updated

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy