ClawPipe
NPM · CLAWPIPE-MCP-SERVER · SCANNED AUG 3
Cost-optimized LLM pipeline + 6 AI security skills (reasoning, triage, remediation, compliance).
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. 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 105 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 555 tokens (~46/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 29% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · clawpipe-mcp-server
claude mcp add finsavvyai-clawpipe-mcp-server -- npx -y clawpipe-mcp-server
codex mcp add finsavvyai-clawpipe-mcp-server -- npx -y clawpipe-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"finsavvyai-clawpipe-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"clawpipe-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add finsavvyai-clawpipe-mcp-server --command npx --arg -y --arg clawpipe-mcp-server
mcp_servers:
finsavvyai-clawpipe-mcp-server:
command: "npx"
args: ["-y", "clawpipe-mcp-server"] {
"mcpServers": {
"finsavvyai-clawpipe-mcp-server": {
"command": "npx",
"args": [
"-y",
"clawpipe-mcp-server"
]
}
}
} 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.
- 2 Aug 26 +42
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → pass ▲ functional
- Schema quality: unverified → fair ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 +13
- Tool coverage: unverified → 100 ▲ functional
- 31 Jul 26 −19
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 37
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
clawpipe_analyze_cost ~51
Estimate the cost of a prompt without sending it. Shows token count, estimated cost per model, and potential savings from Booster and Packer.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | The prompt text to analyze |
No output schema declared.
No examples provided.
clawpipe_booster_check ~60
Check if a prompt can be resolved by the Agent Booster without calling an LLM. Returns the result if resolvable, or indicates that an LLM call is needed.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | The prompt to check against booster rules |
No output schema declared.
No examples provided.
clawpipe_prompt ~102
Send a prompt through the ClawPipe pipeline (Booster -> Pack -> Cache -> Route -> Call -> Learn). Returns the response text and pipeline metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | — | Override model selection (e.g. gpt-4o) |
| prompt | string | yes | The prompt text to send through the pipeline |
| provider | string | — | Override provider (e.g. openai, anthropic) |
| system | string | — | Optional system message |
No output schema declared.
No examples provided.
clawpipe_report_to_jira ~66
Create a Jira issue. Use for budget breaches, cost spikes, or agent anomalies.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | — |
| issue_type | string | — | — |
| project_key | string | yes | — |
| severity | string | — | — |
| summary | string | yes | — |
No output schema declared.
No examples provided.
clawpipe_report_to_notion ~64
Append a page to a Notion database. Use for cost digests, weekly summaries, incident logs.
| Name | Type | Req | Description |
|---|---|---|---|
| body_markdown | string | — | — |
| database_id | string | yes | — |
| properties | object | — | — |
| title | string | yes | — |
No output schema declared.
No examples provided.
clawpipe_skill_compliance ~34
Write SOC 2 / ISO 27001 / HIPAA / GDPR evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | — |
No output schema declared.
No examples provided.
clawpipe_skill_incident ~27
Reconstruct attack chain + recommend containment steps.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | — |
No output schema declared.
No examples provided.
clawpipe_skill_reasoning ~28
Root-cause + risk-score a security finding.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | — |
No output schema declared.
No examples provided.
clawpipe_skill_remediation ~27
Generate a fix plus rollback for a vulnerability.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | — |
No output schema declared.
No examples provided.
clawpipe_skill_threat_intel ~35
Enrich CVE / IOC with NVD/CIRCL-style context.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | — |
No output schema declared.
No examples provided.
clawpipe_skill_triage ~29
Prioritize a batch of security findings by actual risk.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | — |
No output schema declared.
No examples provided.
clawpipe_stats ~32
Get current session telemetry: total requests, tokens, cost, cache hit rate, top models, and average latency.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.