Returns every profile you are currently monitoring, with its handle, platform, follower count, refresh cadence, next scheduled crawl time, when it was last checked for updates, and any paused reason (e.g. paused for insufficient credits). Free to call. Use it to audit what is being refreshed and what it is costing, or to grab a profileId for untrack_profile.
See everything you are currently monitoring in one free call: each profile's handle and platform, follower count, refresh cadence, next scheduled crawl time, when it was last checked, and any paused reason. It is the dashboard behind track_profile, the view an agent uses to audit what is being refreshed and what it is costing.
Connect the Viral Outliers MCP server once and the list_tracked_profiles tool becomes available to your agent alongside all other skills:
claude mcp add --transport http viral-outliers https://viraloutliers.com/api/mcp \
--header "Authorization: Bearer so_live_YOUR_KEY"In Claude.ai or ChatGPT, add a custom connector pointing at https://viraloutliers.com/api/mcp. Your agent then calls list_tracked_profiles on its own whenever the task needs it.
It returns every profile under active monitoring with the details that matter for managing them: platform and handle, follower count, refresh cadence (daily, every 3 days or weekly), the next scheduled crawl time, the last time it was checked for updates, and a pausedReason where applicable (for example, paused for insufficient credits).
It is free and read-only. Each monitored profile costs 10 credits per scheduled refresh, so the cadence column doubles as a cost view: multiply by the refresh frequency to see roughly what each profile spends per month.
Use it to audit recurring spend and to grab a profileId for untrack_profile: list what is being refreshed, surface cadences and next-due times to the user, and cancel the accounts that are no longer worth refreshing. It is the first half of every budget-control loop.
It is also how you diagnose gaps: if a monitored profile is not producing new posts, the pausedReason tells you whether monitoring stalled on an empty balance (it resumes automatically after a top-up) rather than leaving you guessing why updates stopped.
This skill is free and never spends credits.
Call list_tracked_profiles. It returns each monitored profile with its cadence, next scheduled refresh time and paused status (free), so an agent can audit recurring spend and decide what to keep or untrack.
The list shows a pausedReason for each profile. When a scheduled crawl cannot be charged the row is flagged paused for insufficient credits; it resumes automatically once you top up, so no re-tracking is needed.
Each scheduled refresh costs 10 credits, so multiply by the cadence shown for each profile: weekly is roughly 40 credits a month, every 3 days roughly 100, and daily roughly 300. Summing across the list gives a running estimate of recurring monitoring spend before you decide what to untrack.
Also available as a REST API endpoint.
Related topics: monitored profiles dashboard · scheduled crawl status · recurring API spend · monitoring cost audit