# capx café (npm · capx-cafe)

Agent-native X (Twitter) posting as one MCP server; every post clears a server-side guardrail.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `capx-cafe`: 86/100 (this document), [markdown](https://verifymcp.io/servers/vb-tyagi-capx-cafe/capx-cafe.md), [page](https://verifymcp.io/servers/vb-tyagi-capx-cafe/capx-cafe)

## Channel facts

- Registry: `npm`
- Package: `capx-cafe`
- Version: `0.1.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to vb-tyagi/capx-cafe).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 16 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 798 tokens (~72/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_loop" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the capx café MCP server?

capx café runs locally as an npm package, launched with npx -y capx-cafe. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add vb-tyagi-capx-cafe -- npx -y capx-cafe
```

### Cursor

```json
{
  "mcpServers": {
    "vb-tyagi-capx-cafe": {
      "command": "npx",
      "args": [
        "-y",
        "capx-cafe"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "vb-tyagi-capx-cafe": {
      "command": "npx",
      "args": [
        "-y",
        "capx-cafe"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add vb-tyagi-capx-cafe -- npx -y capx-cafe
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vb-tyagi-capx-cafe": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "capx-cafe"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vb-tyagi-capx-cafe --command npx --arg -y --arg capx-cafe
```

### Hermes

```yaml
mcp_servers:
  vb-tyagi-capx-cafe:
    command: "npx"
    args: ["-y", "capx-cafe"]
```

### Netclaw

```json
{
  "McpServers": {
    "vb-tyagi-capx-cafe": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "capx-cafe"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add vb-tyagi-capx-cafe -t stdio -c npx -a -y capx-cafe
```

### Other

```json
{
  "mcpServers": {
    "vb-tyagi-capx-cafe": {
      "command": "npx",
      "args": [
        "-y",
        "capx-cafe"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 82, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-03 (score 78)

First indexed and scored.

## MCP tools (11)

### `connect_x` (~69 tokens)

Connect (or confirm) your X account via the capx chokepoint. Call once for a consent URL; after authorizing in the browser, call again with { confirm: true }.

Input parameters:

- `clientId` (string)
- `confirm` (boolean)
- `lane` (string)

### `whoami` (~23 tokens)

Show the connected X account and its status (via the chokepoint).

### `post_now` (~163 tokens)

Post text to X now. Every post passes the casserole guardrail at the chokepoint; blocked/held posts are never sent, and the token never touches this machine. Set aiGenerated only if the user wants this post labelled AI-assisted (default off — it is the user's choice). Pass inReplyToId with a prior post's platformPostId to chain a native reply/thread.

Input parameters:

- `aiGenerated` (boolean): label this post AI-assisted — the USER decides; default false
- `idempotencyKey` (string)
- `inReplyToId` (string): platformPostId of the post this replies to (for threads)
- `mediaIds` (array): media ids from upload_media to attach to this post
- `text` (string, required)

### `preview` (~75 tokens)

Dry-run a draft through the casserole guardrail WITHOUT posting: returns whether it would pass, be held, or be blocked, and why. Use it to fix a draft before posting or scheduling. This is a linter, never a way to bypass the guard.

Input parameters:

- `aiGenerated` (boolean)
- `text` (string, required)

### `audit` (~56 tokens)

Show the durable history of what capx has posted or attempted on your behalf (most recent first, with delivery state). A trust feature — read-only, your own handle only.

Input parameters:

- `limit` (number): max rows (default 50)

### `upload_media` (~100 tokens)

Upload a local image or video (produced by your own media tool) so it can be attached to a post. Reads the file, streams the bytes to the chokepoint, and returns a media id to pass to post_now as mediaIds. Media is not moderated by casserole — you set the AI-content label per the media skills.

Input parameters:

- `path` (string, required): local file path to the image/video, e.g. ./out/hero.png

### `create_loop` (~187 tokens)

Schedule recurring posts. YOU (the agent) must write the posts and pass them in `posts` — capx never generates content, so at fire time it only ships text you already wrote. When the queue empties the loop pauses and asks for more. Requires a verified X account at least 30 days old.

Input parameters:

- `aiGenerated` (boolean): label this loop's posts AI-assisted — the USER decides; default false
- `daysOfWeek` (array, required): 0=Sunday .. 6=Saturday, e.g. [1,3,5]
- `posts` (array, required): the posts YOU wrote; one is sent per fire, in order
- `time` (string, required): local time, HH:MM, e.g. "09:00"
- `timezone` (string): IANA zone (defaults to this machine's), e.g. Asia/Kolkata

### `list_loops` (~25 tokens)

List your scheduled loops, their next-post queue, and whether any are paused.

### `pause_loop` (~35 tokens)

Pause or resume a loop.

Input parameters:

- `id` (string, required)
- `paused` (boolean): false to resume; defaults to true

### `top_up_loop` (~45 tokens)

Add more posts YOU wrote to a loop's queue. Resumes a loop that paused because it ran out.

Input parameters:

- `id` (string, required)
- `posts` (array, required)

### `delete_loop` (~20 tokens)

Delete a loop permanently.

Input parameters:

- `id` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/vb-tyagi-capx-cafe/capx-cafe#diagnostics

## Score history

- 2026-09-20: 86
- 2026-09-19: 86
- 2026-09-18: 85
- 2026-09-17: 85
- 2026-09-16: 84
- 2026-09-15: 84
- 2026-09-14: 83
- 2026-09-13: 83
- 2026-09-12: 82
- 2026-09-11: 82
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 78
- 2026-09-07: 78
- 2026-09-06: 78
- 2026-09-05: 78
- 2026-09-04: 78
- 2026-09-03: 78

## Common questions

### What is the capx café MCP server?

capx café is an MCP server listed in the public MCP registry as io.github.vb-tyagi/capx-cafe. Agent-native X (Twitter) posting as one MCP server; every post clears a server-side guardrail. This page covers its npm package (capx-cafe).

### Is the capx café MCP server safe to use?

capx café scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the capx café MCP server expose?

capx café exposes 11 tools: connect_x, whoami, post_now, preview, audit, and 6 more. Their descriptions and schemas cost roughly 798 tokens of context every time the server is loaded.

### Is the capx café MCP server still maintained?

capx café is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the capx café MCP server under?

capx café declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/capx-cafe
- Socket report: https://socket.dev/npm/package/capx-cafe
- Repository: https://github.com/vb-tyagi/capx-cafe
- Website: https://capx-cafe.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/vb-tyagi-capx-cafe/capx-cafe.xml
- Changelog JSON feed: https://verifymcp.io/servers/vb-tyagi-capx-cafe/capx-cafe.json
- HTML version of this page: https://verifymcp.io/servers/vb-tyagi-capx-cafe/capx-cafe