io.github.usesequential/sequential

Sequential session replay

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

Session replay and product analytics. Read cases, sessions, verdicts and funnels.

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

Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthenticated","message":"Send Authorization: Bearer <project access token>"}

Endpoint: https://api.usesequential.com/mcp (streamable-http)
Host: api.usesequential.com
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 api.usesequential.com, PKCE S256, grants authorization_code, refresh_token.
Scopes findings:read sessions:read releases:write sessions:explore findings:link findings:verify ask:use analytics:read insights:propose feedback:write changes:read changes:read_sensitive changes:propose findings:review sessions:review.
Read from the server's public OAuth metadata, without a token. Method.
Repository: https://github.com/usesequential/mcp
Website: https://www.usesequential.com/features/connect-your-agent
Registry: active, updated 2026-11-11 · registry entry

More servers

Other registry entries on api.usesequential.com.

Servers that mention sequential.

com.decionis/mcp · needs auth
Help Us Agree com.helpusagree/conciliation · needs auth
Consequential Analytics io.consequential/mcp · needs auth
DecRec io.decrec/decrec · needs auth
InterAI Risk Oracle io.github.InterAILabs/ai-risk-oracle · alive
Hermes Plant — Agent Commerce Assurance io.github.JesseGdotIO/hermes-plant · alive
Durable Thinking io.github.linxule/durable-thinking · needs your URL
TookEffect io.github.tookeffect/tookeffect · 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.

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.