Scopeblind Gateway vs Trustscoreagent
A side-by-side look at the Scopeblind Gateway and Trustscoreagent MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Scopeblind Gateway for security work as a local process; choose Trustscoreagent 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 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.
Choose Trustscoreagent when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 52/100 · Good | 56/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 | INTERNAL_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 10 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Scopeblind Gateway | View Trustscoreagent |
Tools & capabilities
Scopeblind Gateway tools
No tool names declared yet. Check the project README from the listing page.
Trustscoreagent 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.
Scopeblind Gateway
{
"mcpServers": {
"tomjwxf-scopeblind-gateway": {
"command": "npx",
"args": [
"-y",
"@scopeblind/passport"
],
"env": {
"INTERNAL_API_KEY": "YOUR_INTERNAL_API_KEY_HERE"
}
}
}
}
Trustscoreagent
{
"mcpServers": {
"trustscoreagent-trustscoreagent": {
"command": "npx",
"args": [
"-y",
"@trustscoreagent/mcp-server"
]
}
}
}
Frequently asked questions
Scopeblind Gateway is categorized under Security and uses a local stdio subprocess. Trustscoreagent belongs to Security and uses a local stdio subprocess. Pick Scopeblind Gateway for security work and Trustscoreagent 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.
Scopeblind Gateway is listed as free. Auth: no auth required. Trustscoreagent 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 tomjwxf-scopeblind-gateway and trustscoreagent-trustscoreagent as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Scopeblind Gateway has a quality signal of 52/100 (Good) with 2 views, 0 installs and 10 GitHub stars. Trustscoreagent has 56/100 (Good) with 2 views, 0 installs and 0 GitHub stars.