Shellward vs Pre Trip compliance scanner
A side-by-side look at the Shellward and Pre Trip compliance scanner MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Shellward for security work as a local process; choose Pre Trip compliance scanner for security over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Shellward 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:
SHELLWARD_MODE, SHELLWARD_LOCALE, SHELLWARD_THRESHOLD, SHELLWARD_BASELINE_PATH.
PChoose Pre Trip compliance scanner when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | P Pre Trip compliance scanner | |
|---|---|---|
| Category | Security | Security |
| Quality signal | 61/100 · Good | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | OAuth 2.0 |
| Pricing | Free | Not declared |
| Required env vars | SHELLWARD_MODESHELLWARD_LOCALESHELLWARD_THRESHOLDSHELLWARD_BASELINE_PATH | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 139 | — |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Shellward | View Pre Trip compliance scanner |
Tools & capabilities
Shellward tools
No tool names declared yet. Check the project README from the listing page.
Pre Trip compliance scanner 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.
Shellward
{
"mcpServers": {
"jnmetacode-shellward": {
"command": "npx",
"args": [
"-y",
"shellward"
],
"env": {
"SHELLWARD_MODE": "YOUR_SHELLWARD_MODE_HERE",
"SHELLWARD_LOCALE": "YOUR_SHELLWARD_LOCALE_HERE",
"SHELLWARD_THRESHOLD": "YOUR_SHELLWARD_THRESHOLD_HERE",
"SHELLWARD_BASELINE_PATH": "YOUR_SHELLWARD_BASELINE_PATH_HERE"
}
}
}
}
Pre Trip compliance scanner
{
"mcpServers": {
"pre-trip-compliance-scanner": {
"command": "npx",
"args": [
"-y",
"pre-trip-compliance-scanner"
]
}
}
}