Talk to the SecurityScorecard API in natural language from Claude and other MCP clients
FAQ (answers come from our records)
How do I install it?
The repository provides this install command: npx -y @callmarcus/securityscorecard-mcp. It comes from the repository itself; we cannot guarantee it runs as-is in your client.
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository CallMarcus/security-scorecard-mcp;first catalogued 2026-10-10;last seen 2026-10-10。There is no official certification or quality rating here — we record sources and dates only.
SSC MCP Server
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
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:
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:
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:
Option B — Run from source (for development)
Then point your MCP client at the local build. For clients that use the mcpServers format (Claude Desktop, Cursor, …):
**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:
| 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 517 API endpoints with hybrid semantic/keyword search |
| analyze_issue_types | Granular issue type breakdowns |