@gridinsoft/mcp-inspector
Related Servers
Alternatives to @gridinsoft/mcp-inspector
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA URL security scanner and MCP server that enables AI agents to analyze URLs for phishing, malware, and other threats before navigation, with optional intent alignment checks.6Apache 2.0

agentminds-mcpofficial
AlicenseAqualityDmaintenanceMCP server for AgentMinds collective intelligence platform, enabling AI agents to scan websites for security/SEO/performance issues, pull personalized recommendations, and share findings across the network.725 npmMIT- AlicenseNot gradedqualityCmaintenanceMCP server that provides tools to scan text and URLs for prompt injection attacks, protecting AI agents from adversarial inputs.1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides fact-checking capabilities and truth anchoring for AI agents using verified data sources.MIT
- AlicenseAqualityDmaintenanceAn MCP server for domain intelligence — WHOIS, DNS records, SSL certificate inspection, SPF/DMARC validation, security-header audits, and blacklist/reputation checks, callable by AI agents. Powered by domainintel.app; runs server-side, no local setup.749 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server providing domain name checking and other web tools, accessible via MCP, REST API, and CLI for AI assistants.MIT
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.