Tripwire Guard — evidence First injection scanner vs Semgrep
A side-by-side look at the Tripwire Guard — evidence First injection scanner and Semgrep MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Tripwire Guard — evidence First injection scanner for security work as a local process; choose Semgrep 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 Tripwire Guard — evidence First injection scanner when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You want tools like
tripwire_scan.
Choose Semgrep 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 | 55/100 · Good | 48/100 · Fair |
| 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 | 0 | 17,253 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Tripwire Guard — evidence First injection scanner | View Semgrep |
Tools & capabilities
Tripwire Guard — evidence First injection scanner tools 1
tripwire_scanLocally inspect untrusted text for known prompt-injection and agent-hijack signals before using it as agent context. Returns evidence and an allow, review, or recommend-block decision; it does not enforce the decision.
Semgrep 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.
Tripwire Guard — evidence First injection scanner
{
"mcpServers": {
"tripwire-guard-evidence-first-injection-scanner": {
"command": "npx",
"args": [
"-y",
"tripwire-guard"
]
}
}
}
Semgrep
{
"mcpServers": {
"semgrep-semgrep": {
"command": "uvx",
"args": [
"semgrep"
]
}
}
}
Frequently asked questions
Tripwire Guard — evidence First injection scanner is categorized under Security and uses a local stdio subprocess. Semgrep belongs to Security and uses a local stdio subprocess. Pick Tripwire Guard — evidence First injection scanner for security work and Semgrep 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.
Tripwire Guard — evidence First injection scanner has no declared pricing — check the project's own site. Semgrep 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 tripwire-guard-evidence-first-injection-scanner and semgrep-semgrep as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Tripwire Guard — evidence First injection scanner has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Semgrep has 48/100 (Fair) with 1 views, 0 installs and 17,253 GitHub stars.