mcpcost

work.thetoolshed/toolshed

ToolShed

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

A persistent workspace where your AI builds and runs automations, with an encrypted key vault.

needs auth probed 2026-11-14 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized"}
Endpoint
https://mcp.thetoolshed.work/v2 (streamable-http)
Host
mcp.thetoolshed.work
Getting access
OAuth without dynamic client registration. Ask the publisher for a client id first; with it, a client can run the consent.
Scopes shed.exec shed.jobs shed.read shed.write.
Read from the server's public OAuth metadata, without a token. Method.
Website
https://mcp.thetoolshed.work
Registry
active, updated 2026-11-11 · registry entry
Changes
3 recorded, reachable in 2 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 automations or persistent.

History

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

ProbedResultInitToolsClaudeo200k
2026-11-14 11:22needs auth
2026-11-13 12:10refused
2026-11-12 12:13needs auth

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.