mcp-registry/io.github.jamboree777/nightwatch · v1.5.0
As of 2026-10-23 22:05 UTC, the Jamboree777 Nightwatch MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 18 outages in 90 days, with a median recovery of 7 minutes.
Real-time crypto asset intel for trading AIs: liquidity grades, transfer routes, spreads, BTI
Claude Code
claude mcp add --transport http jamboree777-nightwatch-mcp-server https://nightwatch-v1-api.onrender.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"jamboree777-nightwatch-mcp-server": {
"type": "http",
"url": "https://nightwatch-v1-api.onrender.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
8 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
In the last 30 days: 1 tool(s) removed and 8 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
7 of 40 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.jamboree777%2Fnightwatch/fixes
{
"name": "get_microburst",
"description": "High-frequency orderbook microstructure for a token: quality score (0-100), quote persistence, concentration HHI, imbalance volatility, active anomaly flags. Detects bot/MM activity and depth resilience. Null-safe: has_data=false when no HF capture exists. Requires: exchange, symbol.",
"inputSchema": {
"type": "object",
"required": [
"exchange",
"symbol"
],
"properties": {
"symbol": {
"type": "string",
"description": "Trading pair symbol (e.g. BTC/USDT)"
},
"exchange": {
"type": "string",
"description": "Exchange ID"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_token_intel",
"description": "ONE-call token intelligence for trading decisions: rating (grade, 15-step grade_detail, GPA, outlook, verdict, lifecycle), per-venue grades (each with as_of, the age of its 7-day grade), unanimous-club membership, microburst quality score, warning severity/convergence, prediction hit-rate + history (history is cumulative-to-date per day; last_warning_at says when the last warning was), KG fill, 1d cross-exchange spread, open/blocked transfer routes, PLUS coverage (Coverage Grade v0: A-D score of",
"inputSchema": {
"type": "object",
"required": [
"exchange",
"symbol"
],
"properties": {
"symbol": {
"type": "string",
"description": "Trading pair symbol (e.g. BTC/USDT)"
},
"exchange": {
"type": "string",
"description": "Exchange ID (e.g. binance, upbit, gateio) or its two-letter venue code. An unknown pair answers ok:false, reason pair_not_found."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_token_research",
"description": "Get comprehensive research data for a token including grade, liquidity metrics, risk assessment, and percentile rankings. Requires: exchange, symbol.",
"inputSchema": {
"type": "object",
"required": [
"exchange",
"symbol"
],
"properties": {
"symbol": {
"type": "string",
"description": "Trading pair symbol"
},
"exchange": {
"type": "string",
"description": "Exchange ID"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.jamboree777/nightwatch"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.jamboree777/nightwatch"}) over MCP.
forge_signal_publish ~620 tokensagent_contribute ~406 tokensroute_intent ~374 tokenshive_read_room ~320 tokensstrategy_spec_paper ~312 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.jamboree777%2Fnightwatch?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.jamboree777%2Fnightwatch?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jamboree777%2Fnightwatch.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jamboree777%2Fnightwatch.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.jamboree777%2Fnightwatch?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:782f038dfedea4b5…, first seen 2026-10-21, included at leaf 36776 of 54,860. Version history · verify what your client received.
Compare: most reliable security servers · most reliable knowledge servers · most reliable communication servers · most reliable other servers · most reliable finance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 22:05 UTC, the Jamboree777 Nightwatch MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 18 outages in 90 days, with a median recovery of 7 minutes.
Jamboree777 Nightwatch MCP server advertises 40 tools, including agent_connect, agent_contribute, agent_inbox, agent_status, forge_mirror_consent.
Point your MCP client at this streamable-http endpoint: https://nightwatch-v1-api.onrender.com/mcp
Glimind scanned all 40 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.