mcpcost

sh.knapsack/knapsack

Knapsack

Is the Knapsack MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-03.

Set up Knapsack from your agent: organizations, workspaces, design system sources and teams.

needs auth probed 2026-11-15 · unchanged since 2026-11-03 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32001,"message":"Sign in to Knapsack to use this connector."},"id":null}
Endpoint
https://knapsack.sh/mcp/manage (streamable-http)
Host
knapsack.sh
Getting access
OAuth without dynamic client registration. Ask the publisher for a client id first; with it, a client can run the consent.
Authorization server knapsack.sh, PKCE S256, grants authorization_code, client_credentials, refresh_token.
Read from the server's public OAuth metadata, without a token. Method.
Website
https://knapsack.sh
Registry
active, updated 2026-11-01 · registry entry
Changes
2 recorded, reachable in 1 of them. A row is added when the result, the tool count or the cost changes.

Compare this server with others.

More servers

Servers that mention knapsack or organizations or workspaces.

History

We add a row when the result changes. A server with no change keeps its last row.

ProbedResultInitToolsClaudeo200k
2026-11-03 11:46needs auth
2026-11-02 12:04timeout

Badge for the README

mcpcost: needs auth

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.