{"id":"ai-saltapp-salt","name":"ai.saltapp/salt","title":"Salt","description":"Your agent asks humans on Salt and gets answers: messages, tap-to-answer cards, invoices.","category":"communication","categories":["communication","finance-and-payments","agents-and-memory"],"flags":[],"users_30d":0,"health":{"status":"auth_required","latency_ms":593,"tool_count":null,"auth":"oauth","checked_at":"2026-10-15T16:20:12.697Z"},"remote":true,"pending":false,"install_link":"https://toolfindr.dev/add?server=ai.saltapp%2Fsalt&ref=tool-finder","details_url":"https://toolfindr.dev/servers/ai-saltapp-salt","health_error":"initialize: HTTP 401","repo_url":"https://github.com/0000F8/salt-mcp","website_url":"https://saltapp.ai","version":"0.2.7","remotes":[{"type":"streamable-http","url":"https://mcp.saltapp.ai/mcp","headers":[{"description":"OAuth 2.1 bearer token (\"Bearer sat_...\"), for a keyless Salt agent the connecting human owns/authorizes via saltapp.ai's OAuth flow. This is now the RECOMMENDED way to connect -- no header is required up front; an MCP client that supports OAuth discovers the flow automatically from this endpoint's 401 response (RFC 9728 Protected Resource Metadata at /.well-known/oauth-protected-resource/mcp, naming https://saltapp.ai as the authorization server). See README.md's \"Hosted server\" section.","isSecret":true,"name":"Authorization"},{"description":"LEGACY: a pre-existing Salt agent's own API key, for the small api-key-only tool set (list_salt_agents, list_products, create_product). Sent per-request; never stored by the hosted server. Superseded by the OAuth bearer flow above for new integrations, but still supported unchanged.","isSecret":true,"name":"X-Salt-Api-Key"},{"description":"LEGACY: paired with X-Salt-Api-Key above; the agent's numeric/user id, sent verbatim.","isSecret":true,"name":"X-Salt-App-Id"}]}]}