SecurityScorecard MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG_MODE | No | Set 'true' for verbose logging | |
| COMPANY_DOMAIN | No | Default domain for queries | |
| REQUEST_INTERVAL_MS | No | Interval in milliseconds | |
| REQUEST_CACHE_TTL_MS | No | Cache TTL in milliseconds | |
| REQUESTS_PER_INTERVAL | No | Number of requests per interval | |
| SECURITY_SCORECARD_API_TOKEN | Yes | Your SecurityScorecard API token |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| security_dashboardC | 📊 SECURITY STATUS: Get comprehensive security score, grade, and key metrics with intelligent response modes. Supports minimal responses for quick queries and detailed analysis for comprehensive security overviews. |
| analyze_security_risksC | 🚨 SECURITY RISKS: Comprehensive security risk analysis with intelligent prioritization. Analyzes critical vulnerabilities, risk patterns, and provides actionable remediation guidance with flexible response modes. |
| create_improvement_planB | 🎯 IMPROVEMENT PLAN: Generate security improvement recommendations. INTELLIGENT RESPONSES: Use 'minimal' for simple questions like 'what should I fix first?' (50-100 tokens). Use 'standard' for improvement summary (300-500 tokens). Use 'detailed' for full roadmap. |
| discover_assetsB | 🔍 ASSET INVENTORY: Discover domains and IPs with security context and data completeness validation. INTELLIGENT RESPONSES: Use 'minimal' for simple questions like 'how many assets?' (20-50 tokens). Use 'standard' for asset overview (200-400 tokens). Use 'detailed' for comprehensive inventory. |
| analyze_email_securityA | 📧 EMAIL SECURITY: Analyze SPF, DMARC, DKIM issues with domain-by-domain breakdown and cross-validation. INTELLIGENT RESPONSES: Use 'minimal' for simple counts like 'how many SPF missing?' (10-30 tokens). Use 'standard' for email security overview (200-400 tokens). Use 'detailed' for comprehensive email analysis. |
| api_discoveryB | Search and discover SecurityScorecard API endpoints. Returns both human-readable summary and structured JSON for programmatic use. |
| analyze_issue_typesA | 🔍 ISSUE BREAKDOWN: Get detailed breakdown of security issues by specific types (SPF, DMARC, patching, etc.). INTELLIGENT RESPONSES: Use 'minimal' for specific counts (20-50 tokens). Use 'standard' for issue type summary (200-300 tokens). Use 'detailed' for comprehensive breakdown. |
| validate_data_completenessB | ✅ DATA VALIDATION: Cross-validate tool results for accuracy and completeness. INTELLIGENT RESPONSES: Use 'minimal' for validation status (25 tokens). Use 'standard' for validation summary (200-400 tokens). Use 'detailed' for full data audit. |
| query_security_dataC | Direct API access with smart endpoint validation. Uses API discovery to validate endpoints, suggest alternatives, and provide parameter hints. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Several tools have overlapping analytical purposes: security_dashboard and analyze_security_risks both provide security status and risk overviews; analyze_email_security and analyze_issue_types both cover SPF/DMARC issues. While descriptions differentiate them, an agent may still struggle to pick the right one for a broad query.
Seven of nine tools follow a clear verb_noun pattern (e.g., analyze_security_risks, discover_assets), and all names use snake_case. Two tools (security_dashboard, api_discovery) are noun phrases, which is a minor deviation but still readable.
Nine tools is well-scoped for a SecurityScorecard integration, covering core workflows without redundancy. Each tool appears to earn its place, with no excessive or trivial additions.
The tool set covers security scoring, risk analysis, improvement planning, asset discovery, email security, issue breakdown, validation, and direct API access. Minor gaps exist, such as historical trend analysis or detailed remediation tracking, but core lifecycle operations are present.