io.github.driedtoast/superheropw
superhero.pw
Is the superhero.pw MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-06.
MCP server for superhero.pw: comic series, projects, scripts, pages, notes, and palettes.
needs auth probed 2026-11-14 · unchanged since 2026-11-06 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized","message":"Provide a superhero.pw session token as `Authorization: Bearer <token>`. Ob- Endpoint
- https://api.superhero.pw/api/mcp (streamable-http)
- Host
- api.superhero.pw
- Getting access
- A key or token from the publisher, sent in the Authorization header (Bearer). The server publishes no OAuth metadata. Store the key once: npx mcpcost auth https://api.superhero.pw/api/mcp --header "Authorization: Bearer …".
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/driedtoast/superheropw
- Registry
- active, updated 2026-11-04 · registry entry
- Changes
- 2 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 superhero.
- Agent Exchange com.agenticsuperhero/agent-exchange · not found
- Superhero io.github.pipeworx-io/superhero · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-06 11:25 | needs auth | ||||
| 2026-11-05 11:26 | needs auth |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
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
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.