OSA Procurement Guard MCP Server

What the code does

We read the source, 1 d ago · tools taken from the live server · rules 995398eba69f

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.

  timeout 300 runuser -u "$HARVEST_USER" -- env PSYCHIATRY_CASE_CORPUS_DIR="$CASE_DIR" /usr/bin/node "$LIB_DIR/case-harvester.mjs" 1000 1000

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(cmd, args, { stdio: ['ignore', 'pipe', 'pipe'] });

  const id = stableItemId(item); const dir = path.join(outbox, id); await fs.mkdir(dir, { recursive: true });

    p=subprocess.run(

const TELEGRAM_API = 'https://api.telegram.org';

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

claude mcp add osa-procurement-guard --transport http https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp

https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp

[mcp_servers.osa-procurement-guard]
url = "https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp"

{
  "mcpServers": {
    "osa-procurement-guard": {
      "url": "https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp"
    }
  }
}

{
  "servers": {
    "osa-procurement-guard": {
      "type": "http",
      "url": "https://pkctqxeydfuiupadaoov.supabase.co/functions/v1/procurement-mcp"
    }
  }
}

Available tools 1

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

Endpoints