Skip to main content
Glama
SecurityScorecard MCP Server

SecurityScorecard MCP Server

by CallMarcus

SSC MCP Server

npm version License: MIT

A community-built, comprehensive Model Context Protocol (MCP) server that integrates with the SecurityScorecard API. It runs over stdio, so it works with any MCP-compatible client — Claude Desktop, Claude Code, Cursor, VS Code, and others. It serves MCP protocol revision 2026-07-28 and stays compatible with 2025-era clients.

Published on npm as @callmarcus/securityscorecard-mcp and listed in the MCP Registry as io.github.CallMarcus/securityscorecard-mcp.

Disclaimer: This is an independent, community-built open-source project. It is not affiliated with, endorsed by, sponsored by, or associated with SecurityScorecard, Inc. in any way. It is built solely against SecurityScorecard's publicly available API documentation. "SecurityScorecard" and all related names, marks, and logos are trademarks of SecurityScorecard, Inc. and are used here for identification purposes only. You must supply your own API credentials and comply with SecurityScorecard's terms of service.

Quick Start

Prerequisites

  1. Node.js 20+ - Download

  2. SecurityScorecard API Token - Get from your SecurityScorecard dashboard

No clone or build required. The server runs over stdio via npx, so any MCP-compatible client can launch it. npx -y always fetches the latest published version.

Most clients — Claude Desktop, Cursor, Cline, Windsurf, and others — share the same mcpServers JSON. Add this block to the client's MCP config:

{
  "mcpServers": {
    "security-scorecard": {
      "command": "npx",
      "args": ["-y", "@callmarcus/securityscorecard-mcp"],
      "env": {
        "SECURITY_SCORECARD_API_TOKEN": "your-api-token-here",
        "COMPANY_DOMAIN": "example.com"
      }
    }
  }
}

Where that config file lives:

Client

Config file

Claude Desktop (Windows)

%APPDATA%\Claude\claude_desktop_config.json

Claude Desktop (macOS)

~/Library/Application Support/Claude/claude_desktop_config.json

Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (project)

Replace the credentials with your own, then restart the client.

Claude Code — add it from the CLI instead:

claude mcp add security-scorecard \
  --env SECURITY_SCORECARD_API_TOKEN=your-api-token-here \
  --env COMPANY_DOMAIN=example.com \
  -- npx -y @callmarcus/securityscorecard-mcp

On Windows, wrap the launcher in cmd /c: ... -- cmd /c npx -y @callmarcus/securityscorecard-mcp.

VS Code (Copilot) — uses a servers key with an explicit type, in .vscode/mcp.json:

{
  "servers": {
    "security-scorecard": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@callmarcus/securityscorecard-mcp"],
      "env": {
        "SECURITY_SCORECARD_API_TOKEN": "your-api-token-here",
        "COMPANY_DOMAIN": "example.com"
      }
    }
  }
}

Option B — Run from source (for development)

# Clone the repository
git clone https://github.com/CallMarcus/security-scorecard-mcp.git
cd security-scorecard-mcp

# Install dependencies
npm install

# Build (use build:fast to avoid memory issues)
npm run build:fast

Then point your MCP client at the local build. For clients that use the mcpServers format (Claude Desktop, Cursor, …):

{
  "mcpServers": {
    "security-scorecard": {
      "command": "node",
      "args": ["/path/to/security-scorecard-mcp/build/index.js"],
      "env": {
        "SECURITY_SCORECARD_API_TOKEN": "your-api-token-here",
        "COMPANY_DOMAIN": "example.com"
      }
    }
  }
}

Important: Replace the path and credentials with your actual values, then restart your MCP client. (For Claude Code, run claude mcp add security-scorecard --env SECURITY_SCORECARD_API_TOKEN=your-api-token-here -- node /path/to/security-scorecard-mcp/build/index.js.)

Related MCP server: scorecard_mcp

Available Tools

The server (index.js) provides 9 specialized tools:

Tool

Purpose

security_dashboard

Score, grade, and key security metrics

analyze_security_risks

Issue prioritization and risk analysis

create_improvement_plan

Actionable remediation roadmaps

discover_assets

Asset inventory with security context

analyze_email_security

SPF/DMARC/DKIM analysis

api_discovery

Search 535 API endpoints with hybrid semantic/keyword search

analyze_issue_types

Granular issue type breakdowns

validate_data_completeness

Cross-tool data verification

query_security_data

Direct API access with discovery

Response Modes

Each tool supports three response modes for token efficiency:

  • minimal - Quick answers (15-50 tokens)

  • standard - Overview with context (200-300 tokens)

  • detailed - Comprehensive analysis (800+ tokens)

Environment Variables

Variable

Required

Description

SECURITY_SCORECARD_API_TOKEN

Yes

Your API token

COMPANY_DOMAIN

No

Default domain for queries

DEBUG_MODE

No

Set true for verbose logging

Optional rate limiting and caching:

REQUEST_CACHE_TTL_MS=300000
REQUESTS_PER_INTERVAL=5
REQUEST_INTERVAL_MS=1000

API Discovery

The server includes hybrid search (semantic + keyword) for finding SecurityScorecard API endpoints:

Use api_discovery to search for "email security"

This searches 535 indexed endpoints and returns matching paths with confidence scores, required parameters, and curl examples.

To update the API reference after changes:

npm run api:embed    # Regenerate semantic embeddings
npm run api:update   # Regenerate docs + embeddings

Development

Build Commands

npm run build:fast   # Recommended - uses esbuild (~130ms)
npm run build        # TypeScript compiler (may OOM on some systems)
npm test             # Run tests

Project Structure

src/
  index.ts               # MCP server (9 tools)
  api/client.ts          # SecurityScorecard API client
  integration/           # API discovery system
docs/api/                # Self-contained API reference
  index.jsonl            # Endpoint index (535 endpoints)
  index-embeddings.json  # Semantic search embeddings
build/                   # Compiled JavaScript

Testing

npm test             # Run test suite

Troubleshooting

Build fails with out of memory

Use the fast build instead:

npm run build:fast

"Cannot find module" errors

Reinstall dependencies:

rm -rf node_modules
npm install
npm run build:fast

Semantic search degrades to keyword-only (Windows + WSL)

Install for the platform that runs the server. Claude Desktop on Windows launches the server with Windows node, so if npm install ran under WSL the native modules (onnxruntime-node, sharp) only have linux binaries — the embeddings layer fails to load and api_discovery silently degrades to keyword-only search (results still come back, but confidence scoring is cruder). Run npm install && npm run build:fast from PowerShell or cmd in the repo directory instead — or keep two clones, one per platform.

Your client doesn't see the server

  1. Double-check the config file location for your client (see Quick Start)

  2. For a from-source install, verify the path to build/index.js is correct

  3. Restart the client completely

  4. Sanity-check that the server starts on its own: npx -y @callmarcus/securityscorecard-mcp (it should launch and wait silently on stdio)

API returns 401 Unauthorized

Your API token is invalid or expired. Get a new one from SecurityScorecard dashboard.

License

MIT

Available Tools

9 tools
analyze_email_securityEmail Security AnalysisA

📧 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.

Inputs: domain, response_mode.

analyze_issue_typesIssue Type AnalysisA

🔍 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.

Inputs: domain, focus_factor, response_mode.

analyze_security_risksSecurity Risk Analysis & PrioritizationC

🚨 SECURITY RISKS: Comprehensive security risk analysis with intelligent prioritization. Analyzes critical vulnerabilities, risk patterns, and provides actionable remediation guidance with flexible response modes.

Inputs: focus, domain, response_mode.

api_discoverySecurityScorecard API DiscoveryB

Search and discover SecurityScorecard API endpoints. Returns both human-readable summary and structured JSON for programmatic use.

Inputs: query (required), tag, limit, method, +1 more.

create_improvement_planSecurity 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.

Inputs: domain, timeline, target_grade, response_mode.

discover_assetsAsset DiscoveryB

🔍 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.

Inputs: domain, response_mode, include_risk_details.

query_security_dataSecurity Data QueryC

Direct API access with smart endpoint validation. Uses API discovery to validate endpoints, suggest alternatives, and provide parameter hints.

Inputs: endpoint (required), domain, method, fetch_all, +1 more.

security_dashboardSecurity Dashboard OverviewC

📊 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.

Inputs: domain, response_mode.

validate_data_completenessData Completeness ValidationB

✅ 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.

Inputs: domain, response_mode, expected_asset_count.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 9 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to interact with SentinelOne's cybersecurity platform for security analysis, threat investigation, and asset management through natural language queries. Provides read-only access to alerts, vulnerabilities, misconfigurations, and inventory data.
      33
      104
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables asking natural language questions about OpenSSF Scorecard security assessments for open source projects.
      4
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides search, detail lookup, and gap listing tools for a security control inventory, enabling natural language queries about control status and gaps.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes BitSight Security Ratings as tools for AI assistants, enabling queries on company security scores, company search, details, vulnerabilities, portfolio, risk vectors, and alerts.
      MIT