Securityscorecard Mcp

io.github.CallMarcus由 GitHub 账号 CallMarcus 发布v2.0.0更新于 Oct 26, 2026

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

已验证STDIO仅桌面安全与监控商业与电商

概览

AI 生成的概览

非官方 MCP 服务器,让助手查询 SecurityScorecard 的企业安全评分、风险、资产与邮件安全信息。

可以做什么
  • 读取安全态势:评分、等级、关键指标与问题类型细分
  • 分析风险并生成整改改进计划
  • 盘点资产并检查 SPF/DMARC/DKIM 邮件安全
  • 检索 SecurityScorecard API 参考并直接发起 API 查询
  • 跨工具校验数据完整性,支持精简、标准、详细三种响应模式
适用场景
适合需要让助手获取某企业域名的第三方安全评分与风险背景、检查邮件认证配置,或在聊天客户端内梳理整改优先级的场景。
运行要求
通过 npx 以 stdio 在本机运行,需要 Node.js 20 以上。需要 SecurityScorecard API 令牌,放在 SECURITY_SCORECARD_API_TOKEN 中;COMPANY_DOMAIN 为可选的默认域名。需要能访问 SecurityScorecard API 的网络。
安装前请注意
API 令牌是密钥,会写入客户端配置文件,请妥善保护该文件。该项目为独立社区项目,与 SecurityScorecard 公司无关联,使用须遵守其服务条款。查询会把企业域名发送给 SecurityScorecard API;工具本身为只读查询。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Securityscorecard Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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

来源:README.md,提交 af4fad8

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

2
  1. v2.0.0最新Oct 4, 2026
  2. v1.2.0Sep 16, 2026

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。