io.github.authn8/mcp-server

Authn8

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

Shared 2FA for teams: let AI agents get TOTP codes for the accounts your Authn8 token can see.

needs auth probed 2026-11-15 · HTTP 401

Streamable HTTP error: Error POSTing to endpoint:

Endpoint: https://api.authn8.com/mcp (streamable-http)
Host: api.authn8.com
Package: The publisher's package npm:@authn8/mcp-server did not list its tools in the container: needs network, MCP error -32000: Connection closed Error: Failed to connect to Authn8 API. Please check AUTHN8_API_URL (https://api.authn8.com). Error: fetch failed.
Getting access: The server answers HTTP 401 with no WWW-Authenticate header and no OAuth metadata, so the publisher's documentation is the only guide.
Read from the server's public OAuth metadata, without a token. Method.
Repository: https://github.com/authn8/mcp-server
Website: https://authn8.com
Registry: active, updated 2026-11-05 · registry entry

More servers

Servers that mention accounts or shared.

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

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

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.