Ext Ops Panel
Open dashboard
Comparison

dev.mcpgrade/mcp vs io.github.CallMarcus/securityscorecard-mcp

dev.mcpgrade/mcp is an MCP server published by mcpgrade.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.CallMarcus/securityscorecard-mcp is an MCP server published by CallMarcus. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacedev.mcpgrade/mcpio.github.CallMarcus/securityscorecard-mcp
Official MCP Registry Listed
Version: 0.1.1
Downloads/month (npm): 151
Downloads/week (npm): 32
Not marked · First seen
Listed
Version: 2.0.0
Downloads/month (npm): 503
Downloads/week (npm): 63
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

dev.mcpgrade/mcp vs io.github.CallMarcus/securityscorecard-mcp
Factdev.mcpgrade/mcpio.github.CallMarcus/securityscorecard-mcp
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub1
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@mcpgrade/mcp)On your machine (@callmarcus/securityscorecard-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/jeremyrx7/mcpgradegithub.com/callmarcus/security-scorecard-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

dev.mcpgrade/mcp

In its own words, on Official MCP Registry:

Security grades (A-F) for MCP servers. Check one before you install or trust it. mcpgrade.dev

io.github.CallMarcus/securityscorecard-mcp

In its own words, on Official MCP Registry:

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

How to run each

dev.mcpgrade/mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio dev-mcpgrade-mcp -- npx -y @mcpgrade/mcp

io.github.CallMarcus/securityscorecard-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "SECURITY_SCORECARD_API_TOKEN=<YOUR_SECURITY_SCORECARD_API_TOKEN>" --transport stdio securityscorecard-mcp -- npx -y @callmarcus/securityscorecard-mcp

Requires: SECURITY_SCORECARD_API_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of dev.mcpgrade/mcp publish no settings it asks for, so we do not compare settings.

What it can do: dev.mcpgrade/mcp · What it can do: io.github.CallMarcus/securityscorecard-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built