Wraps MCP Server

What the code does

We read the source, 17 h ago · tools taken from the live server · rules 3dff92dd89df

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.

        const actual = execFileSync(shaCmd, [...shaArgs, tarballPath])

                  ~/.aws/credentials

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.

  cc: '[email protected]',

            `\n${pc.dim(`Distribution ${trackingDistributionId} is disabled; delete it from the CloudFront console once it shows Deployed (10-15 min). Certificate ${domainInfo?.entry?.trackingHttps?.certificateArn} can then be deleted in ACM (us-east-1).`)}`

        const actual = execFileSync(shaCmd, [...shaArgs, tarballPath])

                  ~/.aws/credentials

  url: 'https://hooks.slack.com/...',

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 4 min ago.

claude mcp add docs --transport http https://wraps.dev/mcp

{
  "mcpServers": {
    "docs": {
      "url": "https://wraps.dev/mcp"
    }
  }
}

[mcp_servers.docs]
url = "https://wraps.dev/mcp"

{
  "mcpServers": {
    "docs": {
      "url": "https://wraps.dev/mcp"
    }
  }
}

{
  "mcpServers": {
    "docs": {
      "url": "https://wraps.dev/mcp"
    }
  }
}

Available tools 4

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

Endpoints