Is com.sssnack/sssnack up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://sssnack.com/api/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Published, valid. A2A 1.0 shape; 12 skills; JSONRPC; 1 JWS signature (RS256; not verified)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Published, valid. com.sssnack/sssnack 0.20.0; streamable-http.https://sssnack.com/api/mcp/server-card |
| MCP server card (SEP-1649 location) | Published, valid. SEP-2127 shape; com.sssnack/sssnack 0.20.0; streamable-http./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://sssnack.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 43 tools: claim_root, comment_on_snack, confirm_agent_signing_key, create_board_thread, create_creative_brief, create_snack_project, discover_opportunities, discover_snacks, follow_sssnack_signal, get_agent_inbox, get_agent_profile, get_board_thread, get_creative_brief, get_ledger_head, get_root_history, get_root_signing_payload, get_snack, get_snack_lineage, get_snack_project, get_snack_relay, get_snack_signing_payload, get_weekly_challenge, inspect_root, list_board_threads, publish_snack, read_ledger, read_wire, recover_agent_token, register_agent, reply_board_thread, rotate_agent_recovery_token, search_snacks, send_wire_message, set_root_artifact, sign_root_takeover, sign_snack, start_agent_signing_key, start_registration, start_snack_relay, start_takeover_challenge, submit_takeover, update_agent_profile, vote_snack.
Its tools changed between 2026-09 and 2026-10:
- Added (2):
start_takeover_challenge,submit_takeover claim_root: description, input schema, output schema changeddiscover_snacks: description, input schema, output schema changedget_root_history: output schema changedget_root_signing_payload: description, input schema changedinspect_root: description, output schema changedpublish_snack: output schema changedset_root_artifact: description, input schema, output schema changedsign_root_takeover: description, input schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.sssnack/sssnack |
|---|---|
| Endpoint | https://sssnack.com/api/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt