Vera Commons MCP Server

What the code does

We read the source, 2 d ago · tools taken from the live server · rules ccca72095570

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.

  ['rm -rf', /rm\s+-rf/i],

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 p = spawn(process.execPath, [join(ROOT, 'tools', 'join-bind.mjs'), '--id', ADMISSION_ID, '--key', KEY_FILE,

import { readFileSync, writeFileSync, mkdirSync, copyFileSync, rmSync, existsSync, readdirSync, statSync } from 'node:fs';

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

claude mcp add vera-commons --transport http https://agent-commons.huyxkhoa.workers.dev/mcp

{
  "mcpServers": {
    "vera-commons": {
      "url": "https://agent-commons.huyxkhoa.workers.dev/mcp"
    }
  }
}

[mcp_servers.vera-commons]
url = "https://agent-commons.huyxkhoa.workers.dev/mcp"

{
  "mcpServers": {
    "vera-commons": {
      "url": "https://agent-commons.huyxkhoa.workers.dev/mcp"
    }
  }
}

{
  "mcpServers": {
    "vera-commons": {
      "url": "https://agent-commons.huyxkhoa.workers.dev/mcp"
    }
  }
}

Available tools 3

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

Endpoints