Securityscorecard Mcp

io.github.CallMarcusPublished by GitHub account CallMarcusv2.0.0Updated Oct 26, 2026

Community-built, comprehensive MCP server for the SecurityScorecard API (unofficial).

Overview

AI-generated overview

Unofficial MCP server that lets an assistant query SecurityScorecard security ratings, risks, assets and email security for a company domain.

What you can do
  • Read security posture: scores, grades, key metrics and issue-type breakdowns
  • Analyze risks and build remediation improvement plans
  • Inventory assets and check SPF/DMARC/DKIM email security
  • Search the SecurityScorecard API reference and run direct API queries
  • Verify data completeness across tools, with minimal, standard or detailed response modes
When to use it
Useful when you want an assistant to pull third-party security ratings and risk context for a company domain, review email authentication posture, or draft remediation priorities without leaving the chat client.
Requirements
Runs locally over stdio via npx, so Node.js 20+ is needed. Requires a SecurityScorecard API token in SECURITY_SCORECARD_API_TOKEN; COMPANY_DOMAIN is an optional default domain. Network access to the SecurityScorecard API is required.
Before you install
The API token is a secret placed in the client config file, so keep that file protected. It is an independent project not affiliated with SecurityScorecard, and you must comply with SecurityScorecard's terms of service. Queries send company domains to SecurityScorecard's API; results are read-only lookups.

Installation

In SourceWeft

  1. Open Securityscorecard Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

Option A — Install from npm (recommended)

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:

json
{  "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:

ClientConfig 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:

bash
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:

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)

bash
# Clone the repositorygit clone https://github.com/CallMarcus/security-scorecard-mcp.gitcd security-scorecard-mcp
# Install dependenciesnpm 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, …):

json
{  "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.)

Available Tools

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

ToolPurpose
security_dashboardScore, grade, and key security metrics
analyze_security_risksIssue prioritization and risk analysis
create_improvement_planActionable remediation roadmaps
discover_assetsAsset inventory with security context
analyze_email_securitySPF/DMARC/DKIM analysis
api_discoverySearch 535 API endpoints with hybrid semantic/keyword search
analyze_issue_typesGranular issue type breakdowns
validate_data_completenessCross-tool data verification
query_security_dataDirect 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

VariableRequiredDescription
SECURITY_SCORECARD_API_TOKENYesYour API token
COMPANY_DOMAINNoDefault domain for queries
DEBUG_MODENoSet true for verbose logging

Optional rate limiting and caching:

REQUEST_CACHE_TTL_MS=300000REQUESTS_PER_INTERVAL=5REQUEST_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:

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

Development

Build Commands

bash
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 systemdocs/api/                # Self-contained API reference  index.jsonl            # Endpoint index (535 endpoints)  index-embeddings.json  # Semantic search embeddingsbuild/                   # Compiled JavaScript

Testing

bash
npm test             # Run test suite

Troubleshooting

Build fails with out of memory

Use the fast build instead:

bash
npm run build:fast

"Cannot find module" errors

Reinstall dependencies:

bash
rm -rf node_modulesnpm installnpm 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

Links

Source: README.md at commit af4fad8

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v2.0.0LatestOct 4, 2026
  2. v1.2.0Sep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.