io.github.Rckl88/clawbackai-mcp
NPM · CLAWBACKAI-MCP · SCANNED SEP 20
LLM cost optimization. Audit your calls, prove savings, route to the cheapest quality model. BYOK.
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 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- 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 156 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 463 tokens (~57/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 84% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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 io.github.Rckl88/clawbackai-mcp server?
io.github.Rckl88/clawbackai-mcp runs locally as an npm package, launched with npx -y clawbackai-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 · clawbackai-mcp
claude mcp add rckl88-clawbackai-mcp -- npx -y clawbackai-mcp
{
"mcpServers": {
"rckl88-clawbackai-mcp": {
"command": "npx",
"args": [
"-y",
"clawbackai-mcp"
]
}
}
} {
"servers": {
"rckl88-clawbackai-mcp": {
"command": "npx",
"args": [
"-y",
"clawbackai-mcp"
]
}
}
} codex mcp add rckl88-clawbackai-mcp -- npx -y clawbackai-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rckl88-clawbackai-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"clawbackai-mcp"
],
"enabled": true
}
}
} openclaw mcp add rckl88-clawbackai-mcp --command npx --arg -y --arg clawbackai-mcp
mcp_servers:
rckl88-clawbackai-mcp:
command: "npx"
args: ["-y", "clawbackai-mcp"] {
"McpServers": {
"rckl88-clawbackai-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"clawbackai-mcp"
]
}
}
} assistant mcp add rckl88-clawbackai-mcp -t stdio -c npx -a -y clawbackai-mcp
{
"mcpServers": {
"rckl88-clawbackai-mcp": {
"command": "npx",
"args": [
"-y",
"clawbackai-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.
- 19 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.
- 17 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 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.
- 12 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.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
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/clawbackai-mcp@1.0.0
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 95 packages
| Packages resolved | 95 |
|---|---|
| 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 →
activate_routing ~49
Activate smart routing after reviewing audit results. Only call after get_audit_status shows a completed report.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your API key |
| strategy | string | – | Routing strategy |
No output schema declared.
No examples provided.
check_savings ~35
Check monthly and all-time routing value (price difference captured per routed call).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your API key |
No output schema declared.
No examples provided.
get_audit_status ~51
Check audit progress. Returns calls logged, report URL when ready, routing recommendations, and next steps. Share the report URL with a human decision maker.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your API key |
No output schema declared.
No examples provided.
get_frontier ~37
Get the efficient frontier — best quality per dollar by task type. No API key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| task_type | string | – | Task type |
No output schema declared.
No examples provided.
get_model_recommendation ~70
Get the recommended model for a task type without making an API call. No key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| max_cost_per_million | number | – | Max cost per million tokens |
| min_quality | number | – | Minimum quality score (0-100) |
| task_type | string | – | Task type |
No output schema declared.
No examples provided.
optimize_llm_call ~81
Route a completion to the best model. Requires routing to be activated first via the audit flow.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your provider API key |
| max_tokens | integer | – | – |
| messages | array | yes | OpenAI-format messages array |
| model | string | yes | The model you would normally use |
| temperature | number | – | – |
No output schema declared.
No examples provided.
set_agent_budget ~66
Set per-agent monthly budget. Requires routing to be active.
| Name | Type | Req | Description |
|---|---|---|---|
| action_on_exceed | string | – | – |
| agent_name | string | yes | Agent name |
| api_key | string | yes | Your API key |
| monthly_budget_usd | number | yes | Monthly budget in USD |
No output schema declared.
No examples provided.
start_audit ~74
Start a free Clawback audit. Registers your API key for traffic observation. Route 50+ calls through clawback.run/v1 to trigger the audit automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your provider API key (hashed for identification, never stored raw) |
| string | – | Optional email for report delivery |
No output schema declared.
No examples provided.
What is the io.github.Rckl88/clawbackai-mcp server?
io.github.Rckl88/clawbackai-mcp is listed in the public MCP registry as io.github.Rckl88/clawbackai-mcp. LLM cost optimization. Audit your calls, prove savings, route to the cheapest quality model. BYOK. This page covers its npm package (clawbackai-mcp).
Is the io.github.Rckl88/clawbackai-mcp server safe to use?
io.github.Rckl88/clawbackai-mcp scores 76 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 io.github.Rckl88/clawbackai-mcp server expose?
io.github.Rckl88/clawbackai-mcp exposes 8 tools: start_audit, get_audit_status, activate_routing, optimize_llm_call, get_frontier, and 3 more. Their descriptions and schemas cost roughly 463 tokens of context every time the server is loaded.
Is the io.github.Rckl88/clawbackai-mcp server still maintained?
io.github.Rckl88/clawbackai-mcp 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 io.github.Rckl88/clawbackai-mcp server under?
io.github.Rckl88/clawbackai-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.