treg.to 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.

    env = dict(os.environ)

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 probe = spawnSync(process.platform === 'win32' ? 'where' : 'which', ['treg'], {

        subprocess.run([claude, "mcp", "remove", "--scope", "user", name],

    {"provider": "Telegram",    "tokens": ["TELEGRAM"],            "base_url": "https://api.telegram.org",                        "auth": {"shape": "query"}},

    env = dict(os.environ)

    tb.innerHTML = d.endpoints.map(e => {

            cands = sorted((d.name for d in base.iterdir() if d.is_dir()

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

claude mcp add treg --transport http https://treg.to/mcp

{
  "mcpServers": {
    "treg": {
      "url": "https://treg.to/mcp"
    }
  }
}

[mcp_servers.treg]
url = "https://treg.to/mcp"

{
  "mcpServers": {
    "treg": {
      "url": "https://treg.to/mcp"
    }
  }
}

{
  "mcpServers": {
    "treg": {
      "url": "https://treg.to/mcp"
    }
  }
}

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

Endpoints