NeuroDock Chronometric MCP Server

What the code does

We read the source, 3 d ago · rules 995398eba69f

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

        "HKCU\\Software\\Microsoft\\Windows\\CurrentVersion\\Run",

    subprocess.run(

    const out = execFileSync(cmd, args as string[], {

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 neurodock-mcp-chronometric -- uvx neurodock-mcp-chronometric

{
  "mcpServers": {
    "neurodock-mcp-chronometric": {
      "command": "uvx",
      "args": [
        "neurodock-mcp-chronometric"
      ]
    }
  }
}

[mcp_servers.neurodock-mcp-chronometric]
command = "uvx"
args = ["neurodock-mcp-chronometric"]

{
  "mcpServers": {
    "neurodock-mcp-chronometric": {
      "command": "uvx",
      "args": [
        "neurodock-mcp-chronometric"
      ]
    }
  }
}

{
  "servers": {
    "neurodock-mcp-chronometric": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "neurodock-mcp-chronometric"
      ]
    }
  }
}