Serverdex live check · status history
Release pack changelog seal rollback — Atom MCP server status
● Needs sign-inchecked Nov 22, 2026, 11:08 UTC
Release pack changelog seal rollback — Atom is up: at the last check (Nov 22, 2026, 11:08 UTC) the endpoint answered but asked for a key or an OAuth sign-in before the handshake, which is normal for a hosted server with accounts.
Uptime, 30 days
0%
1 days on record
Uptime, 90 days
0%
1 days on record
Answering since
—
Needs sign-in
Tools now
—
no change on record
Status history
1 change on record · only changes are stored, not every check- First checked: needs sign-in
http 401
Questions
- Is Release pack changelog seal rollback — Atom down right now?
- Release pack changelog seal rollback — Atom is up: at the last check (Nov 22, 2026, 11:08 UTC) the endpoint answered but asked for a key or an OAuth sign-in before the handshake, which is normal for a hosted server with accounts.
- How is Release pack changelog seal rollback — Atom checked?
- Serverdex calls the server's hosted endpoint about once a day with a plain MCP initialize followed by tools/list, with no credentials, and records only changes: a status flip or a change in the tool list. Uptime is time-weighted from those changes, so a server checked for less than a day shows no percentage.
- What does "needs sign-in" mean for Release pack changelog seal rollback — Atom?
- The endpoint is reachable and speaks HTTP, but returns 401 or 403 until a key or OAuth sign-in is supplied. The server is up; the Serverdex check cannot read its tools without an account.
Back to the Release pack changelog seal rollback — Atom listing · test any endpoint yourself with the MCP server health check · what changed across the registry today: MCP server changelog.