Threat intelligence
through MCP.

1. Set your key in this terminal

   Before registering the server, run export GRIDINSOFT_API_KEY="YOUR_GRIDINSOFT_API_KEY" with your own key. Keep it available whenever you launch Claude.

2. Register the server

   Run the command below. User scope makes Inspector available across projects. The saved configuration reads the key from Claude’s environment.

3. Start a fresh Claude session

   Open /mcp and confirm that gridinsoft is connected. Existing entry? Remove it with claude mcp remove gridinsoft before registering again.

claude mcp add-json --scope user gridinsoft '{
  "command": "npx",
  "args": [
    "-y",
    "@gridinsoft/[email protected]"
  ],
  "env": {
    "GRIDINSOFT_API_KEY": "${GRIDINSOFT_API_KEY}"
  },
  "type": "stdio",
  "timeout": 120000
}'

The 120,000 ms tool timeout accommodates URL scans. On Windows, use the JSON below in a project’s .mcp.json, set $env:GRIDINSOFT_API_KEY="YOUR_GRIDINSOFT_API_KEY" in PowerShell, then start Claude there.

{
  "mcpServers": {
    "gridinsoft": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "-y",
        "@gridinsoft/[email protected]"
      ],
      "env": {
        "GRIDINSOFT_API_KEY": "${GRIDINSOFT_API_KEY}"
      },
      "type": "stdio",
      "timeout": 120000
    }
  }
}

1. Open your personal Codex configuration

   Create ~/.codex/config.toml if it does not exist. On Windows, use %USERPROFILE%\.codex\config.toml.

2. Add the server

   Merge the block below into the file and replace the API key placeholder locally. Update an existing mcp_servers.gridinsoft block instead of duplicating it.

3. Reload the connection

   Start a new CLI session or restart the server in the app’s MCP settings. The CLI, desktop app and IDE use the configuration on their execution host.

[mcp_servers.gridinsoft]
command = "npx"
args = ["-y", "@gridinsoft/[email protected]"]
startup_timeout_sec = 60
tool_timeout_sec = 120

[mcp_servers.gridinsoft.env]
GRIDINSOFT_API_KEY = "YOUR_GRIDINSOFT_API_KEY"

The startup timeout allows for the first npm download. The separate 120-second tool timeout covers a slow URL scan.

[mcp_servers.gridinsoft]
command = "cmd"
args = ["/c", "npx", "-y", "@gridinsoft/[email protected]"]
startup_timeout_sec = 60
tool_timeout_sec = 120

[mcp_servers.gridinsoft.env]
GRIDINSOFT_API_KEY = "YOUR_GRIDINSOFT_API_KEY"

1. Open your Hermes configuration

   Use ~/.hermes/config.yaml on macOS, Linux or WSL2; %LOCALAPPDATA%\hermes\config.yaml on native Windows. If you set HERMES_HOME, use that directory. Merge under the existing mcp_servers section.

2. Add Inspector and your key

   Replace the placeholder in the private local config. Explicitly passing env matters: Hermes filters the environment inherited by MCP subprocesses.

3. Reload MCP

   Start hermes chat or run /reload-mcp in the current session. The same configuration works on native Windows; Hermes resolves npx through its managed runtime.

mcp_servers:
  gridinsoft:
    command: npx
    args: ["-y", "@gridinsoft/[email protected]"]
    env:
      GRIDINSOFT_API_KEY: "YOUR_GRIDINSOFT_API_KEY"
    timeout: 120
    connect_timeout: 60

Hermes timeouts are in seconds. If you keep secrets in the private .env file beside config.yaml, use GRIDINSOFT_API_KEY: "${GRIDINSOFT_API_KEY}" in the config instead. Native Windows guide ↗

1. Open your user-level MCP file

   Use ~/.cursor/mcp.json on macOS or Linux; %USERPROFILE%\.cursor\mcp.json on Windows.

2. Merge the server entry

   Add gridinsoft under mcpServers and replace the API key placeholder in this personal file.

3. Enable the tools

   Restart Cursor, enable Inspector in its MCP settings and check Available Tools. Start an Agent chat so it can use the tools.

{
  "mcpServers": {
    "gridinsoft": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@gridinsoft/[email protected]"
      ],
      "env": {
        "GRIDINSOFT_API_KEY": "YOUR_GRIDINSOFT_API_KEY"
      }
    }
  }
}

Cursor does not document a configurable MCP tool timeout. Domain checks and balance are a good first test; a long URL scan may hit the host’s limit.

{
  "mcpServers": {
    "gridinsoft": {
      "type": "stdio",
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "-y",
        "@gridinsoft/[email protected]"
      ],
      "env": {
        "GRIDINSOFT_API_KEY": "YOUR_GRIDINSOFT_API_KEY"
      }
    }
  }
}

1. Open the local server config

   In Claude Desktop, go to Settings → Developer → Edit Config. This is the chat app’s local MCP configuration.

2. Add Inspector

   Merge the entry into claude_desktop_config.json and replace the API key placeholder locally. On macOS the file is in ~/Library/Application Support/Claude/; on Windows, %APPDATA%\Claude\.

3. Quit and reopen Claude

   Fully quit the application, reopen it and check the local connector status. Start a new chat with Inspector enabled.

{
  "mcpServers": {
    "gridinsoft": {
      "command": "npx",
      "args": [
        "-y",
        "@gridinsoft/[email protected]"
      ],
      "env": {
        "GRIDINSOFT_API_KEY": "YOUR_GRIDINSOFT_API_KEY"
      }
    }
  }
}

Claude Desktop does not document an adjustable host tool timeout. For long URL scans, use a client with the 120-second setting shown here. Linux desktop users can choose Claude Code.

{
  "mcpServers": {
    "gridinsoft": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "-y",
        "@gridinsoft/[email protected]"
      ],
      "env": {
        "GRIDINSOFT_API_KEY": "YOUR_GRIDINSOFT_API_KEY"
      }
    }
  }
}

1. Open your personal settings

   Use ~/.gemini/settings.json (Windows: %USERPROFILE%\.gemini\settings.json). Keep any existing settings and servers.

2. Add the server

   Merge the entry under mcpServers, then replace the API key placeholder locally. Leave normal tool approval settings enabled.

3. Reload discovery

   In Gemini, run /mcp reload followed by /mcp list. Or restart Gemini after saving the file.

{
  "mcpServers": {
    "gridinsoft": {
      "command": "npx",
      "args": [
        "-y",
        "@gridinsoft/[email protected]"
      ],
      "env": {
        "GRIDINSOFT_API_KEY": "YOUR_GRIDINSOFT_API_KEY"
      },
      "timeout": 120000
    }
  }
}

The timeout is in milliseconds. The explicit env entry supplies the key even when the client filters sensitive environment variables.

{
  "mcpServers": {
    "gridinsoft": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "-y",
        "@gridinsoft/[email protected]"
      ],
      "env": {
        "GRIDINSOFT_API_KEY": "YOUR_GRIDINSOFT_API_KEY"
      },
      "timeout": 120000
    }
  }
}

1. Use the portable Copilot config

   Open ~/.copilot/mcp-config.json (Windows: %USERPROFILE%\.copilot\mcp-config.json). In current VS Code, choose MCP: Add Server → Command (stdio) → Global → Copilot Global.

2. Merge the entry

   Add Inspector under mcpServers and replace the key locally. This format is shared with Copilot CLI. Keep normal tool approvals enabled.

3. Restart the connection

   Start a new Copilot CLI session, or in VS Code use MCP: List Servers → gridinsoft → Restart Server. Remote sessions need Node and the key on their execution host.

{
  "mcpServers": {
    "gridinsoft": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@gridinsoft/[email protected]"
      ],
      "env": {
        "GRIDINSOFT_API_KEY": "YOUR_GRIDINSOFT_API_KEY"
      },
      "tools": [
        "*"
      ],
      "timeout": 120000
    }
  }
}

This is the current Copilot format. Older VS Code Local sessions use .vscode/mcp.json with a servers wrapper instead; follow the VS Code format reference for that mode.

{
  "mcpServers": {
    "gridinsoft": {
      "type": "stdio",
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "-y",
        "@gridinsoft/[email protected]"
      ],
      "env": {
        "GRIDINSOFT_API_KEY": "YOUR_GRIDINSOFT_API_KEY"
      },
      "tools": [
        "*"
      ],
      "timeout": 120000
    }
  }
}