# com.useweckr/weckr (npm · @weckr/mcp)

Ask which of your customers cost more in LLM calls than they pay, per user and per feature.

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

## Components

- npm · `@weckr/mcp`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-useweckr-weckr/weckr-mcp.md), [page](https://verifymcp.io/servers/com-useweckr-weckr/weckr-mcp)

## Channel facts

- Registry: `npm`
- Package: `@weckr/mcp`
- Version: `0.1.2`
- 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**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 31 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 557 tokens (~92/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 com.useweckr/weckr MCP server?

com.useweckr/weckr runs locally as an npm package, launched with npx -y @weckr/mcp. 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 com-useweckr-weckr -- npx -y @weckr/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-useweckr-weckr": {
      "command": "npx",
      "args": [
        "-y",
        "@weckr/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-useweckr-weckr": {
      "command": "npx",
      "args": [
        "-y",
        "@weckr/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-useweckr-weckr -- npx -y @weckr/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-useweckr-weckr": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@weckr/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-useweckr-weckr --command npx --arg -y --arg @weckr/mcp
```

### Hermes

```yaml
mcp_servers:
  com-useweckr-weckr:
    command: "npx"
    args: ["-y", "@weckr/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-useweckr-weckr": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@weckr/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-useweckr-weckr -t stdio -c npx -a -y @weckr/mcp
```

### Other

```json
{
  "mcpServers": {
    "com-useweckr-weckr": {
      "command": "npx",
      "args": [
        "-y",
        "@weckr/mcp"
      ]
    }
  }
}
```

## 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-20 (score 83, −3)

- [functional] Stability: pass → 0.80

### 2026-09-19 (score 86, 0)

- [security] Stability: 0.97 → pass

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

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

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

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

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

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

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

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

### 2026-09-10 (score 82, +1)

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

### 2026-09-08 (score 81, +1)

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

## MCP tools (6)

### `get_overview` (~72 tokens)

Get a high-level overview of AI costs, revenue, and margin for the current calendar month. Returns total spend, total revenue, net margin, request count, count of unprofitable users, combined loss in USD, and the most expensive feature. Best first call for any "how am I doing" question.

### `get_users` (~139 tokens)

Get per-user cost/revenue/margin breakdown. Sorted by margin (worst first). Use this for "which users are losing me money?" and "which users cost the most?" questions. Anonymous calls (rows with null userId) appear grouped under "(anonymous)".

Input parameters:

- `filter` (string): Filter users by profitability status. Default: all. "unprofitable" = users costing more than they pay; "watch" = >=70% of their revenue is going to AI cost; "profitable" = healthy.
- `limit` (integer): Max number of users to return. Default 20. Must be 1..100.

### `get_feature_breakdown` (~60 tokens)

Get per-feature cost breakdown. Shows which features (the `feature` label your code passes to wk.chat()) are the most expensive across all users. Use this for "which feature is costing me the most?" or "where should I optimize?".

### `get_model_recommendations` (~68 tokens)

Get recommendations for swapping to cheaper models. We surface features that are using expensive models for short outputs (<150 avg output tokens) where a same-provider cheaper model exists and the projected monthly saving is >=$1. Use this for "where can I cut AI cost without breaking anything?".

### `get_pricing_recommendations` (~65 tokens)

Get per-plan pricing recommendations based on actual AI costs this month. Tells you which plans are unprofitable and what to charge to keep margins healthy. Needs at least 5 users and 30 requests this month to produce a recommendation — otherwise returns a note.

### `get_spending_cap_url` (~153 tokens)

Returns the dashboard URL where the user can edit a monthly AI spending cap for a plan. This tool does NOT change any settings — it only produces a link. Caps are stored on the project and edited from a browser session, so the founder always reviews them visually. All args are optional; if provided they're echoed in the response so the user can confirm.

Input parameters:

- `action` (string): Optional cap action. block = throw WeckrCapError; downgrade = swap to a cheaper same-provider model.
- `limitUsd` (number): Optional monthly USD spend ceiling per user to suggest.
- `plan` (string): Optional plan name to pre-fill, e.g. "free", "starter", "pro".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-useweckr-weckr/weckr-mcp#diagnostics

## Score history

- 2026-09-20: 83
- 2026-09-19: 86
- 2026-09-18: 86
- 2026-09-17: 85
- 2026-09-16: 85
- 2026-09-15: 84
- 2026-09-14: 84
- 2026-09-13: 83
- 2026-09-12: 83
- 2026-09-11: 82
- 2026-09-10: 82
- 2026-09-09: 81
- 2026-09-08: 81
- 2026-09-07: 80
- 2026-09-06: 80
- 2026-09-05: 79
- 2026-09-04: 79
- 2026-09-03: 79
- 2026-09-02: 78
- 2026-09-01: 78
- 2026-08-31: 77
- 2026-08-30: 77
- 2026-08-29: 76
- 2026-08-28: 76
- 2026-08-27: 72
- 2026-08-26: 71
- 2026-08-25: 71
- 2026-08-24: 71
- 2026-08-23: 71
- 2026-08-22: 71

## Common questions

### What is the com.useweckr/weckr MCP server?

com.useweckr/weckr is an MCP server listed in the public MCP registry as com.useweckr/weckr. Ask which of your customers cost more in LLM calls than they pay, per user and per feature. This page covers its npm package (@weckr/mcp).

### Is the com.useweckr/weckr MCP server safe to use?

com.useweckr/weckr scores 83 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. 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 com.useweckr/weckr MCP server expose?

com.useweckr/weckr exposes 6 tools: get_overview, get_users, get_feature_breakdown, get_model_recommendations, get_pricing_recommendations, get_spending_cap_url. Their descriptions and schemas cost roughly 557 tokens of context every time the server is loaded.

### Is the com.useweckr/weckr MCP server still maintained?

com.useweckr/weckr 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 com.useweckr/weckr MCP server under?

com.useweckr/weckr 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/@weckr/mcp
- Socket report: https://socket.dev/npm/package/@weckr/mcp
- Repository: https://github.com/Ghiles3232/weckr-sdks
- Website: https://useweckr.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-useweckr-weckr/weckr-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-useweckr-weckr/weckr-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-useweckr-weckr/weckr-mcp