Tripwire Guard — evidence First injection scanner vs Emilia Protocol

A side-by-side look at the Tripwire Guard — evidence First injection scanner and Emilia Protocol MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Tripwire Guard — evidence First injection scanner logoTripwire Guard — evidence First injection scannerSecurity · Local subprocess (stdio)Local read-only MCP scanner for known prompt-injection patterns with exact evidence and no network.55GoodAuth: not declaredEmilia Protocol logoEmilia ProtocolSecurity · Local subprocess (stdio)Human sign-off + trust receipts for AI agents: requires a named human's approval before an irreversible action (payment release, record change, deploy), then mints an offline-verifiable Ed25519 Trust Receipt. Also exposes trust profiles, receipt verification, disputes, and delegation. Apache-2.0; policy engine formally verified. Install: npx -y @emilia-protocol/mcp-server.71GreatAuth: no auth required

Verdict: choose Tripwire Guard — evidence First injection scanner for security work as a local process; choose Emilia Protocol for security as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Tripwire Guard — evidence First injection scanner logoChoose 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.
Explore Tripwire Guard — evidence First injection scanner

Emilia Protocol logoChoose Emilia Protocol 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 want tools like ep_guard_action, ep_check_signoff, ep_verify_receipt.
Explore Emilia Protocol

Feature & specification comparison

Rows where the two servers differ are marked.

SpecTripwire Guard — evidence First injection scanner logoTripwire Guard — evidence First injection scannerEmilia Protocol logoEmilia Protocol
CategorySecuritySecurity
Quality signal55/100 · Good71/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars0598
Directory activity 1 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
Tools13

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.

Emilia Protocol tools 3

  • ep_guard_actionRequest authorization before an irreversible action: payments, wire transfers, fund releases, deletions, record or account changes, or sending messages with real-world effect. Submits the exact action for policy evaluation and human authorization. This MCP tool does not itself sit at the executor choke point: even after approval, the executor MUST match the returned action_hash and atomically consume the receipt before effect. If BLOCKED, poll ep_check_signoff with the receipt_id.
  • ep_check_signoffPoll a pending authorization after ep_guard_action returns BLOCKED. Pass the receipt_id. Returns PENDING, APPROVED_PENDING_CONSUME, CONSUMED, or DENIED. Approval alone is not permission to execute: the executor must match action_hash and atomically consume the receipt at its own choke point.
  • ep_verify_receiptAsk the configured EMILIA service to verify a stored trust receipt and report its hash and anchor status. Read-only, but not an offline verifier: the result is the service response for the supplied receipt_id.

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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "tripwire-guard-evidence-first-injection-scanner": {
      "command": "npx",
      "args": [
        "-y",
        "tripwire-guard"
      ]
    }
  }
}

Emilia Protocol

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "emiliaprotocol-emilia-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "@emilia-protocol/mcp-server"
      ]
    }
  }
}

Frequently asked questions

Tripwire Guard — evidence First injection scanner is categorized under Security and uses a local stdio subprocess. Emilia Protocol belongs to Security and uses a local stdio subprocess. Pick Tripwire Guard — evidence First injection scanner for security work and Emilia Protocol 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. Emilia Protocol 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 emiliaprotocol-emilia-protocol 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. Emilia Protocol has 71/100 (Great) with 6 views, 0 installs and 598 GitHub stars.