Settings

Display timezone and recurring Node scans

Display timezone

CURRENT · —

Times are stored in UTC and displayed in this timezone across the app. Scan schedules keep their own timezone — this only changes how times are shown.

TIMEZONE

MCP server

0 active keys

Connect an AI assistant to the scan corpus over the Model Context Protocol. The server is read-only and exposes two paged tools; both take the same filters the web UI has.

scan_resultsScanned port-443 endpoints: probe state, HTTP status/title/server, TLS certificate, region, matched program.

findingsHosts that matched a bug-bounty rule: label, program, confidence, triage status.

KEY NAME

Loading keys…

CLIENT CONFIGURATION

{
  "mcpServers": {
    "nodescan": {
      "type": "http",
      "url": "/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_MCP_KEY>"
      }
    }
  }
}

Endpoint: /mcp · JSON-RPC 2.0 over HTTP POST · authenticate with Authorization: Bearer (an X-MCP-Key header works too). Replace the placeholder with a key you generated above.

A schedule creates a Node-scan request at its local wall clock, at most once per interval. “Run now” creates the request immediately and rolls the next run forward; pausing keeps the row but stops it from firing.

Node scan schedules

0 schedules

Fired by the orchestrator scheduler

						MACHINES

Previewing 0 of 0 rows · Page 1 of 1

Rows per page

A schedule fires as a queued Node-scan request; it is dispatched to machines like any other request from the Jobs page.