Supply Chain Guard vs Scopeblind Gateway
A side-by-side look at the Supply Chain Guard and Scopeblind Gateway MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Supply Chain Guard for security work as a local process; choose Scopeblind Gateway for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Supply Chain Guard when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Scopeblind Gateway when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
INTERNAL_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 51/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | INTERNAL_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | 11 |
| Directory activity | 4 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Supply Chain Guard | View Scopeblind Gateway |
Tools & capabilities
Supply Chain Guard tools
No tool names declared yet. Check the project README from the listing page.
Scopeblind Gateway tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Supply Chain Guard
{
"mcpServers": {
"supply-chain-guard": {
"command": "npx",
"args": [
"-y",
"supply-chain-guard"
]
}
}
}
Scopeblind Gateway
{
"mcpServers": {
"tomjwxf-scopeblind-gateway": {
"command": "npx",
"args": [
"-y",
"@scopeblind/passport"
],
"env": {
"INTERNAL_API_KEY": "YOUR_INTERNAL_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Supply Chain Guard is categorized under Security and uses a local stdio subprocess. Scopeblind Gateway belongs to Security and uses a local stdio subprocess. Pick Supply Chain Guard for security work and Scopeblind Gateway for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Supply Chain Guard is listed as free. Auth: no auth required. Scopeblind Gateway is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add supply-chain-guard and tomjwxf-scopeblind-gateway as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Supply Chain Guard has a quality signal of 51/100 (Good) with 4 views, 0 installs and 7 GitHub stars. Scopeblind Gateway has 53/100 (Good) with 4 views, 0 installs and 11 GitHub stars.