ClawPipe

io.github.finsavvyaiPublished by GitHub account finsavvyaiv3.2.0Updated Oct 24, 2026

Cost-optimized LLM pipeline + 6 AI security skills (reasoning, triage, remediation, compliance).

VerifiedSTDIODesktop onlySecurity & MonitoringAI & ML

Overview

AI-generated overview

ClawPipe is a local MCP server that gives an assistant a cost-optimized LLM pipeline plus six AI security skills for reasoning, triage, remediation, and…

What you can do
ClawPipe runs as a local stdio process and exposes a cost-optimized LLM pipeline together with six AI security skills. According to its registry description, those skills cover reasoning, triage, remediation, and compliance work. The manifest does not list individual tool names, so the exact tool surface is not documented here.
When to use it
Consider it when you want an assistant to route LLM work through a cost-optimized pipeline, or to help with security reasoning, incident triage, remediation guidance, and compliance tasks. It is a desktop-only local process, so it suits individual workstation use rather than shared or hosted deployments.
Requirements
A local runtime able to run the npm package clawpipe-mcp-server over stdio, plus network access to reach the ClawPipe service. A ClawPipe API key is required and supplied through the environment variable CLAWPIPE_API_KEY. The optional environment variable CLAWPIPE_PROJECT_ID sets the project used for analytics and rate limiting.
Before you install
The server requires the secret CLAWPIPE_API_KEY, which is sent to the ClawPipe service; treat it as a credential and keep it out of shared configuration. The optional CLAWPIPE_PROJECT_ID is used for analytics and rate limiting, so usage data is associated with that project. The manifest declares no authentication beyond the API key and lists no tools, so review what the security skills can actually change before relying on them.

Installation

In SourceWeft

  1. Open ClawPipe in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v3.2.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.