@gridinsoft/mcp-inspector
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GRIDINSOFT_API_KEY | Yes | Your API key for GridinSoft Inspector. Obtain from https://inspector.gridinsoft.com/profile |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspect_domainA | Domain reputation assessment. Returns the available reputation score (0-100), security verdict, categories, and report link. Unknown means no assessment is available, not that the domain is safe. Use this tool when users ask about site reliability, trust, or safety. |
| check_domain_safetyA | Semantic alias for inspect_domain. Quick check if a website is safe, malicious, or a scam. Returns reputation score and security verdict. |
| get_domain_reputationA | Semantic alias for inspect_domain. Get the trust and reputation score (0-100) for a domain. |
| scan_urlA | Deep forensic URL analysis. Detects phishing, malware, and fraudulent redirects. Use this to verify specific links, login pages, or suspicious URLs. Returns page metadata and available security signals; additional analysis depends on the subscription plan. |
| get_balanceA | Check remaining API credits and subscription plan status |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| check-website-safety | Comprehensive safety check for any website. Use this prompt to get a full security verdict, including phishing detection and malware scanning. |
| verify-domain-trust | In-depth trust report for a domain. Check reputation, history, and reliability before using a service or making a purchase. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| GridinSoft Threat Categories Reference | Reference for security and content categories used in GridinSoft verdicts |
TDQS
Scored across 5 tools
Three of the five tools (inspect_domain, check_domain_safety, get_domain_reputation) perform the same operation; the descriptions admit they are 'semantic aliases' of each other, which helps an agent but doesn't remove the redundancy. Only scan_url and get_balance are genuinely distinct actions.
All names follow a clean snake_case verb_noun pattern (inspect_domain, check_domain_safety, get_domain_reputation, scan_url, get_balance) with no mixing of conventions.
Five tools is a reasonable raw count, but two of them are pure aliases, leaving an effective surface of three operations — thin for the advertised scope and inflated by duplication.
The core workflow is covered: domain reputation lookup, deep URL/link forensics, and credit/plan status. Minor gaps exist (no batch/bulk domain or IP reputation check, no way to distinguish plan-limited results beyond a text note), but agents can work around them.