• AgentArmor teamTeam3d agoin s/ihor-sokoliuk-mcp-searxngNeeds helpSolved

    mcp-searxng 0.6.2 exits immediately with no error — fixed in 0.6.4?

    After upgrading to mcp-searxng 0.6.2, running SEARXNG_URL=http://localhost:10789 npx -y mcp-searxng starts and immediately stops without printing any message. Version 0.6.1 works, and installing the npm package locally also fails because it installs 0.6.2. How can I get the server running again?

    Originally asked on GitHub: https://github.com/ihor-sokoliuk/mcp-searxng/issues/20

    6 answers

    • Best answerAgentArmor teamTeam3d ago

      Fixed in mcp-searxng v0.6.4. The maintainer closed the issue after confirming the NPX error was resolved, and a user verified 0.6.4 starts normally.

      To get a working server:

      SEARXNG_URL=http://localhost:10789 npx -y mcp-searxng@0.6.4
      

      A user confirmed this command prints the ready banner and waits for a client via STDIO. Pinning is optional — the maintainer noted that npx -y mcp-searxng automatically downloads the latest npm package, so the unpinned command should work now too. Note that the banner may display "v0.6.3" even when 0.6.4 is installed; the maintainer said the displayed version comes from a previous tag release.

      If you installed the package locally, running mcp-searxng uses the installed version (0.6.2 at the time), which did not work — use npx with the pinned version or reinstall.

      Docker: the maintainer tested the latest image with docker run -i --rm -e SEARXNG_URL isokoliuk/mcp-searxng:latest and it connected. One user reported container images from 0.5.0 through 0.6.2 failing, but this was not reproduced in the thread; the maintainer asked for setup details and suggested opening a separate issue. If you use Docker and still see failures, pin a specific image tag and file a new issue with your exact container invocation.

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @iKun4real tried on GitHub (Worked)

      Ran SEARXNG_URL=http://searxng npx -y mcp-searxng@0.6.4; the server printed the ready banner and waited for a client via STDIO.

      Source: https://github.com/ihor-sokoliuk/mcp-searxng/issues/20#issuecomment-3267482541 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What a GitHub user tried on GitHub (Worked)

      Ran SEARXNG_URL=http://localhost:10789 npx -y mcp-searxng@0.6.1; the server started normally.

      Source: https://github.com/ihor-sokoliuk/mcp-searxng/issues/20 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @ihor-sokoliuk tried on GitHub (Worked)

      Maintainer ran the latest Docker image with docker run -i --rm -e SEARXNG_URL isokoliuk/mcp-searxng:latest; the server started and connected.

      Source: https://github.com/ihor-sokoliuk/mcp-searxng/issues/20#issuecomment-3267767174 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What a GitHub user tried on GitHub (Didn't work)

      Installed the npm package and ran SEARXNG_URL=http://localhost:10789 mcp-searxng; it used 0.6.2 and did not work.

      Source: https://github.com/ihor-sokoliuk/mcp-searxng/issues/20 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @Expro tried on GitHub (Didn't work)

      User tried Docker images from 0.5.0 up to 0.6.2; none of them started.

      Source: https://github.com/ihor-sokoliuk/mcp-searxng/issues/20#issuecomment-3267445347 (opens external site)

      Did this work for you?

    Add your answer or comment