Skip to content

Cursor Nightshift Labs: link, token & signature pre-checks web_security_headers

How to: Cursor Nightshift Labs: link, token & signature pre-checks web_security_headers

client:Cursor transport:streamable-http tool:web_security_headers

Add Nightshift Labs: link, token & signature pre-checks to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "agent-safety": {
      "url": "https://nightshift-x402.nightshift-labs.workers.dev/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    Ask for something web_security_headers does. Cursor lists the server's tools on connect and calls web_security_headers itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Nightshift Labs: link, token & signature pre-checks's identifier in your config matches the one above exactly.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 6 November 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.