Jev Filter MCP Server

What the code does

We read the source, 23 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.

        self.process = subprocess.Popen(

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.

        self.process = subprocess.Popen(

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 jev-filter -e 'TYPESAFE_API_KEY=<TYPESAFE_API_KEY>' -- npx -y @apixly/jev-filter

{
  "mcpServers": {
    "jev-filter": {
      "command": "npx",
      "args": [
        "-y",
        "@apixly/jev-filter"
      ],
      "env": {
        "TYPESAFE_API_KEY": "<TYPESAFE_API_KEY>"
      }
    }
  }
}

[mcp_servers.jev-filter]
command = "npx"
args = ["-y", "@apixly/jev-filter"]
env = { TYPESAFE_API_KEY = "<TYPESAFE_API_KEY>" }

{
  "mcpServers": {
    "jev-filter": {
      "command": "npx",
      "args": [
        "-y",
        "@apixly/jev-filter"
      ],
      "env": {
        "TYPESAFE_API_KEY": "<TYPESAFE_API_KEY>"
      }
    }
  }
}

{
  "servers": {
    "jev-filter": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@apixly/jev-filter"
      ],
      "env": {
        "TYPESAFE_API_KEY": "<TYPESAFE_API_KEY>"
      }
    }
  }
}

Put your own value in place of <TYPESAFE_API_KEY> (Your TypeSafe Jev API key. Inference calls are billable; do not publish the key). The author’s registry entry marks it as required.