Chainsaw package firewall

com.chain305Published by chain305.comOfficial publisherv1.0.0Updated Oct 29, 2026

Package firewall for agents: route npm, pip and docker installs through Chainsaw.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that acts as a package firewall, routing an assistant's npm, pip and docker installs through Chainsaw.

What you can do
  • Route npm, pip and docker package installs through the Chainsaw package firewall.
  • No tool list is published, so the exact operations an assistant can call are not documented here; the stated purpose is gating package installs for agents.
  • Access is tied to a bearer token obtained through a device-code sign-in flow.
When to use it
Worth considering when an agent installs packages during its work and you want those npm, pip and docker installs screened or routed through a firewall service rather than going straight to public registries.
Requirements
A remote MCP endpoint at chain305.com over streamable HTTP; no local package to install. Requires a bearer token in the Authorization header, obtained through the provider's device-code authentication flow. Network access to the provider's service is needed.
Before you install
The Authorization bearer token is a required secret; keep it out of logs and shared configs. Because the service sits in the path of package installs, it can see which packages are requested, and installs may fail or be blocked if the service is unavailable or denies a package. No tool list or documentation is published, so review behavior before relying on it.

Installation

In SourceWeft

  1. Open Chainsaw package firewall in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.chain305%2Fchainsaw/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "chainsaw-package-firewall": {
      "type": "http",
      "url": "https://chain305.com/chainproxy/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

56% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.