Countersign MCP Server

What the code does

We read the source, 22 h ago · rules 3dff92dd89df

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.

const emitted = (p) => path.join(root, ".dts", p);

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 countersign -- npx -y @countersign/mcp

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

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

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

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

This one needs environment variables set before it will start: COUNTERSIGN_URL (Base URL of the Countersign Core to govern (hosted or self-hosted).), COUNTERSIGN_API_KEY (API key for the Core (self-serve one at https://app.countersign.network/start or POST /signup).). The author declared them in the registry entry; get the values from the project itself.