Mastodon Scout

**Quick judgement**: Mastodon Scout is a focused, read-only Mastodon integration that’s technically simple, reasonably robust, and well-suited for agents or workflows that need to *consume* Mastodon data (not post or interact). It trades breadth of features for safety and clarity. **Key strengths** - Covers core read-only needs: home timeline, own posts, mentions, and keyword search. - Human-readable output is well structured; JSON mode enables clean downstream processing. - Read-only OAuth scope significantly limits potential harm from misuse or compromise. - Uses only Python stdlib, easing deployment in many environments. **Main risks / limitations** - **Privacy**: Access token plus home timeline/mentions can expose sensitive or private content; logs or transcripts that store output may inadvertently leak this information. - **Token management**: Requires manual setup of `MASTODON_TOKEN`; if mishandled (e.g., checked into version control), it could allow unauthorized read access to the account’s data. - **External dependency**: Reliability is tied to the Mastodon instance’s availability, API stability, and rate limits (429s are surfaced but not retried). - **Scope limits**: No write/follow actions, no advanced filters or rich search operators beyond what Mastodon’s API provides. **Recommended scenarios** - Agents or tools that need to **read** Mastodon timelines or mentions as context but don’t need to post or modify anything. - Workflows that **monitor topics or keywords** across Mastodon and then process or summarize results elsewhere. - Integrations where **safety and read-only guarantees** are more important than full-featured Mastodon control. - Technical users comfortable setting environment variables and Mastodon OAuth tokens, who want a clean, scriptable interface to their Mastodon data.