mcpbeat Sign in

Chainsaw package firewall MCP Server

answering

Chainsaw package firewall is answering right now. Last checked 14 min ago.

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

Uptime history 63 hours of history
63 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
353 ms
Response time
average over 24h
authentication required
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Chainsaw package firewall every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add chainsaw --transport http https://chain305.com/chainproxy/mcp
Settings → Connectors → Add custom connector, then paste this address
https://chain305.com/chainproxy/mcp
~/.codex/config.toml
[mcp_servers.chainsaw]
url = "https://chain305.com/chainproxy/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "chainsaw": {
      "url": "https://chain305.com/chainproxy/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "chainsaw": {
      "type": "http",
      "url": "https://chain305.com/chainproxy/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://chain305.com/chainproxy/mcp streamable-http needs auth 389 ms 14 min ago

Alternatives to Chainsaw package firewall

same job, measured the same way
Package Version Check MCP
by mshekow

Returns the latest package / dependency / tool versions for Python, NPM, Go, Docker, Helm, etc.

908 installs/wk local only
Docker MCP Server
by hypnosis

Docker for AI agents — containers, compose stacks, logs and databases, locally or over SSH.

349 installs/wk local only
Komodo MCP Server
by mp-tool

MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI

342 installs/wk local only
Docker Hub MCP
by mrfentmen

Look up Docker images, tags, and pull counts from Docker Hub. No key required.

130 installs/wk local only
x402 Micro Tollgate
by kevin2003050666-coder

x402 HTTP 402 + MCP paywall: charge USDC per agent call. Self-host via npx or Docker.

70 installs/wk local only
Execkit
by blinkingbit-oss

Stateful, structured, safe shell sessions for AI agents over local, SSH, and Docker.

198 installs/wk local only
Latex MCP
by sepinetam

Enable AI agents to compile TeX files with LaTeX inside a Docker container.

85 installs/wk local only
lastseen mortality
by lastseen

Check whether an npm package, GitHub Action, MCP server or Docker image is dead or abandoned.

119 installs/wk local only

Chainsaw package firewall — questions

Answers built from our own checks of this server.

Why is there no tool list for Chainsaw package firewall?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Chainsaw package firewall working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 353 ms. The bar chart above shows every period we have measured.
How do I connect Chainsaw package firewall?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does Chainsaw package firewall need an API key?
Yes. Every time we knock, Chainsaw package firewall answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Chainsaw package firewall?
It answers our handshake in 353 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.