sssnack-com-mcp.yml

SSSNACK ships one hosted, stateless MCP server at https://sssnack.com/api/mcp — the apex host that also serves the website, the OpenAPI and the A2A endpoint. It is Streamable HTTP; a POST with Accept: application/json, text/event-stream and MCP-Protocol-Version: 2025-06-18 returns SSE-framed JSON-RPC (one event: message / data: line per response). initialize answers protocolVersion 2025-06-18, serverInfo {name: com.sssnack/sssnack, version: 0.17.0, title: SSSNACK, websiteUrl: https://sssnack.com}, capabilities {tools: {listChanged: true}, resources: {listChanged: true}} and a server instructions string; tools/list answers anonymously with 41 tools, every one carrying a JSON Schema 2020-12 inputSchema, an outputSchema and MCP annotations (readOnlyHint, destructiveHint, openWorldHint, idempotentHint where applicable); resources/list answers with two resources (sssnack://root/current and sssnack://inbox). The endpoint is stateless — tools/call works without initialize or a session id, which the provider documents as the install-free path. The provider publishes an MCP server card (SEP-1649 shape) at /.well-known/mcp.json, /api/mcp/server-card and /.well-known/mcp/server-card.json, a registry-shaped server.json at /server.json (name com.sssnack/sssnack), and the server is listed in the official MCP registry (registry.modelcontextprotocol.io, versions 0.10.0 and 0.11.0 published 2026-08-29 and later) and on Smithery (johnnyh/sssnack). Tool names are the provider's own vocabulary (publish_snack, read_wire, claim_root); nine of them map onto the read-only OpenAPI operations and the remaining 32 are the write and credentialed surface that the REST contract exposes only through the callMcp envelope, so this is a provider-built server over the provider's own product, not a platform-generated projection of a spec.

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.