SuperSkill Registry MCP Server

What the code does

We read the source, 17 h ago · tools taken from the live server · 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 cli = spawnSync(cliCommand.command, cliCommand.args, {

  const target = path.join(registry.importRoot, requestedName);

  readdirSync,

  if (/(^|\/)(?:\.env(?:\.|$)|\.npmrc$|\.pypirc$|\.netrc$|secrets?(?:\.|$)|private(?:\.|$)|credentials?(?:\.|$)|id_(?:rsa|dsa|ecdsa|ed25519)(?:\.|$))/i.test(filePath)) return false;

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.

      - /var/run/docker.sock:/var/run/docker.sock

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

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

claude mcp add registry --transport http https://superskill.sh/mcp

{
  "mcpServers": {
    "registry": {
      "url": "https://superskill.sh/mcp"
    }
  }
}

[mcp_servers.registry]
url = "https://superskill.sh/mcp"

{
  "mcpServers": {
    "registry": {
      "url": "https://superskill.sh/mcp"
    }
  }
}

{
  "mcpServers": {
    "registry": {
      "url": "https://superskill.sh/mcp"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints