MCP Bastion vs Trustscoreagent
A side-by-side look at the MCP Bastion 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 MCP Bastion 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 MCP Bastion when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
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 | 45/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP Bastion | View Trustscoreagent |
Tools & capabilities
MCP Bastion 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.
MCP Bastion
{
"mcpServers": {
"mcp-bastion": {
"command": "npx",
"args": [
"-y",
"mcp-bastion"
]
}
}
}
Trustscoreagent
{
"mcpServers": {
"trustscoreagent-trustscoreagent": {
"command": "npx",
"args": [
"-y",
"@trustscoreagent/mcp-server"
]
}
}
}
Frequently asked questions
MCP Bastion is categorized under Security and uses a local stdio subprocess. Trustscoreagent belongs to Security and uses a local stdio subprocess. Pick MCP Bastion 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.
MCP Bastion has no declared pricing — check the project's own site. 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 mcp-bastion and trustscoreagent-trustscoreagent as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Bastion has a quality signal of 45/100 (Fair) with 1 views, 0 installs and 7 GitHub stars. Trustscoreagent has 56/100 (Good) with 2 views, 0 installs and 0 GitHub stars.
