Inspector MCP Server

Domain and URL security analysis by GridinSoft. Detect phishing and malware threats.

Local serverstdio

What is the Inspector MCP server?

Domain and URL security analysis by GridinSoft. Detect phishing and malware threats. Exposed over MCP by the inspector mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

MCP (Model Context Protocol) server for domain and URL security analysis powered by GridinSoft Inspector.

Its toolset

Everything the assistant can do here goes through one of these:

  • inspect_domain — Comprehensive domain security profile. Returns reputation (0-100), vendor verdicts, hosting/IP info, registrar history, and detailed security tags
  • scan_url — Deep forensic URL analysis. Extracts metadata, effective URL, full redirect chain, DNS/SSL details, and forensic data (screenshots, network traffic
  • get_balance — Check your remaining credits and current subscription status

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at @gridinsoft/mcp-inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Configuration

You will need one environment variable: GRIDINSOFT_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Among the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Inspector's toolset — inspect_domain, scan_url, get_balance — is a fair guide to whether it matches your workflow. It is maintained by gridinsoft; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Inspector's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the inspector mcp server does with a few real requests.

Available tools

ToolWhat it does
inspect_domainComprehensive domain security profile. Returns reputation (0-100), vendor verdicts, hosting/IP info, registrar history, and detailed security tags.
scan_urlDeep forensic URL analysis. Extracts metadata, effective URL, full redirect chain, DNS/SSL details, and forensic data (screenshots, network traffic, cookies, console logs for paid plans).
get_balanceCheck your remaining credits and current subscription status.

How to install the Inspector MCP server

{
  "mcpServers": {
    "gridinsoft": {
      "command": "npx",
      "args": ["-y", "@gridinsoft/mcp-inspector"],
      "env": {
        "GRIDINSOFT_API_KEY": "your_api_key_here"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
GRIDINSOFT_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Inspector to inspect domain.
  • Use Inspector to scan url.
  • Use Inspector to get balance.

Frequently asked questions

It connects Inspector to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (inspect_domain, scan_url, get_balance) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Inspector directly.