ClawPipe
NPM · CLAWPIPE-MCP-SERVER
Cost-optimized LLM pipeline + 6 AI security skills (reasoning, triage, remediation, compliance).
Available components
Last scanned (4 hours ago)
Scores higher than 42% of npm servers
Category Security
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
- 30 of 93 dependencies flagged as unhealthy. 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 199 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability59
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "clawpipe_prompt" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 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
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 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.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 16 Oct 26 −2
- Stability: pass → 0.83 functional
- 15 Oct 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 5 Nov 2026 · Analysed npm/clawpipe-mcp-server@3.2.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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
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.
How do I install the ClawPipe MCP server?
ClawPipe runs locally as an npm package, launched with npx -y clawpipe-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · clawpipe-mcp-server
claude mcp add finsavvyai-clawpipe-mcp-server -- npx -y clawpipe-mcp-server
What is the ClawPipe MCP server?
ClawPipe is an MCP server listed in the public MCP registry as io.github.finsavvyai/clawpipe-mcp-server. Cost-optimized LLM pipeline + 6 AI security skills (reasoning, triage, remediation, compliance). This page covers its npm package (clawpipe-mcp-server).
Is the ClawPipe MCP server safe to use?
ClawPipe scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 ClawPipe MCP server expose?
ClawPipe exposes 12 tools: clawpipe_prompt, clawpipe_analyze_cost, clawpipe_stats, clawpipe_booster_check, clawpipe_report_to_jira, and 7 more. Their descriptions and schemas cost roughly 555 tokens of context every time the server is loaded.
Is the ClawPipe MCP server still maintained?
ClawPipe is still listed as active in the MCP registry. We last reached this channel on 5 November 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 ClawPipe MCP server under?
ClawPipe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.