Pearl MCP Server

What the code does

We read the source, 14 h ago · 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 child = spawn(command, args, { stdio: ['pipe', 'pipe', 'pipe'] });

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 child = spawn(command, args, { stdio: ['pipe', 'pipe', 'pipe'] });

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

claude mcp add pearl-agent-plugin --transport http https://agent.joinpearl.co/mcp

{
  "mcpServers": {
    "pearl-agent-plugin": {
      "url": "https://agent.joinpearl.co/mcp"
    }
  }
}

[mcp_servers.pearl-agent-plugin]
url = "https://agent.joinpearl.co/mcp"

{
  "mcpServers": {
    "pearl-agent-plugin": {
      "url": "https://agent.joinpearl.co/mcp"
    }
  }
}

{
  "mcpServers": {
    "pearl-agent-plugin": {
      "url": "https://agent.joinpearl.co/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints