TollWire Evidence MCP Server

What the code does

We read the source, 1 h ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

  doas: { short: "uC", long: [] },

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

      "reason": "Reading credential stores in the home directory (.ssh, .aws, .gnupg, .kube, .azure, .netrc, .npmrc, .pypirc, .config/gh, .config/gcloud) is not allowed (audit F-01)."

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add evidence-mcp -- npx -y @tollwire/evidence-mcp

{
  "mcpServers": {
    "evidence-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tollwire/evidence-mcp"
      ]
    }
  }
}

[mcp_servers.evidence-mcp]
command = "npx"
args = ["-y", "@tollwire/evidence-mcp"]

{
  "mcpServers": {
    "evidence-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tollwire/evidence-mcp"
      ]
    }
  }
}

{
  "servers": {
    "evidence-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@tollwire/evidence-mcp"
      ]
    }
  }
}