com.useweckr/weckr
NPM · @WECKR/MCP · SCANNED SEP 20
Ask which of your customers cost more in LLM calls than they pay, per user and per feature.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 31 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 557 tokens (~92/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
npm · @weckr/mcp
claude mcp add com-useweckr-weckr -- npx -y @weckr/mcp
{
"mcpServers": {
"com-useweckr-weckr": {
"command": "npx",
"args": [
"-y",
"@weckr/mcp"
]
}
}
} {
"servers": {
"com-useweckr-weckr": {
"command": "npx",
"args": [
"-y",
"@weckr/mcp"
]
}
}
} codex mcp add com-useweckr-weckr -- npx -y @weckr/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-useweckr-weckr": {
"type": "local",
"command": [
"npx",
"-y",
"@weckr/mcp"
],
"enabled": true
}
}
} openclaw mcp add com-useweckr-weckr --command npx --arg -y --arg @weckr/mcp
mcp_servers:
com-useweckr-weckr:
command: "npx"
args: ["-y", "@weckr/mcp"] {
"McpServers": {
"com-useweckr-weckr": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@weckr/mcp"
]
}
}
} assistant mcp add com-useweckr-weckr -t stdio -c npx -a -y @weckr/mcp
{
"mcpServers": {
"com-useweckr-weckr": {
"command": "npx",
"args": [
"-y",
"@weckr/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@weckr/mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_feature_breakdown ~60
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?".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_model_recommendations ~68
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?".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_overview ~72
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pricing_recommendations ~65
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_spending_cap_url ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
No output schema declared.
No examples provided.
get_users ~139
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)".
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.