ANSWERS ONE QUESTION: has this listing been answering Sato Hub's daily checks, and has its tool inventory moved? Returns a bounded 30-day shape from the listing's observed record — days observed, share of OUR checks that succeeded, current state and streak — plus the MCP tool-inventory changes in the window (date, count after the change, added, removed) and the current Sato Score.

RULE ENFORCED: success_rate_pct is the share of Sato Hub's own checks that succeeded, never "uptime" — a failure can be on our side. At most 30 entries; the daily rows are not returned (rule 24: shape, not rows). Absence of a record is unknown, not down.

Pass score_days to add score_series: the daily Sato Score readings we captured for this listing, up to 90 days without a key (a longer request is clamped, never refused, and score_series_window says what was served; the 180-day chart is on the listing's /verify//history page). A day nobody measured is ABSENT from the array rather than carried forward — a gap is a gap — and every move is labelled project or methodology, the latter meaning Sato Hub revised the scoring rubric that day and the movement is ours.

Returns (json): { slug, days, observed: { days_observed, window_days, success_rate_pct, rate_days, rate_window_start, current_state, current_streak_days, last_check }, tool_history: [{ date, count, added, removed }], tools_now, tools_peak, trust_score, trust_tier, score_series, score_series_window, rules, sato_url }. Read-only.

Example: { slug: "jupiter-mcp", days: 30, score_days: 90 }