Andrew's Freebies

Where it sits in the directory's order

What can be seen from outside, weighed as the directory publishes.

Where it answers

• https://andrewsfreebies.com/api/mcpstreamable-http

The tools it lists (7, as of 5 days ago)

The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.

• search

  Use this when the user wants to find, compare, or answer a question about current U.S. free trials, rebates, bonuses, cash back, or other actionable savings. It returns citable answer guides and normalized records. Fetch the best returned id before giving detailed terms. Do not use it for purchases, account access, or guaranteed eligibility.

• fetch

  Use this after search returns a guide:SLUG, trial:SLUG, or entitlement:SLUG id and the user needs the complete answer, terms, evidence, verification state, or official action path. Do not guess ids, substitute a guide URL for an offer action, or use this for an id from another service.

• search_freebies

  Use this when the user needs explicit corpus scope, result limits, or a rich normalized list rather than the standard citable search/fetch flow. It is read-only: the default uses site-controlled actionable U.S. trials and savings, while only an explicit open-source scope reads public GitHub. Use public-benefits only for eligibility-based services. Do not use it for purchases, account access, or guaranteed eligibility.

• get_record

  Use this after search_freebies returns an exact trial or entitlement id and the user needs its complete normalized terms, conditions, sources, official action path, or latest verification state. Do not guess ids or treat a directory-only or inconclusive record as confirmed.

• get_verification

  Use this when the user asks how or when one exact Andrew’s Freebies record was checked, whether its terms matched, or what audit warnings exist. Catalog status and audit outcome are separate; blocked, unknown, and fetch errors never prove expiration, and audits never remove or change records.

• get_freshness

  Use this when the user asks about verification freshness for the actionable-candidate corpus, overdue coverage, scheduler liveness, records sharing an audit outcome, or whether one exact non-directory record is still inside cadence. Directory-only leads and public services remain inspectable elsewhere but are excluded from this denominator. For one record, provide both record_type and record_id; its audit outcome still proves only the fields checked. Blocked or unknown never means expired.