Full entry for one service: docs, auth scheme and how the credential is sent, base URL, operations, MCP endpoint or repository (check which: a repository must be installed, a docs-only server does not call the API), free plan vs trial, rate limits, data policy, notes, last-checked dates, link check, and separate signals: uptime (our availability probes of base URL and MCP endpoint), mcp_repo (archived, last push), mcp_registry (installs), product_reviews (rating, count, date range), sdk_downloads (official npm/PyPI SDKs per month), stackoverflow (question count), app_store (the vendor's iOS app) and github_issues (open vs resolved issues, median days to fix and issue_health 0-100 of the SDK, MCP and spec repos), each with its fetch date. Call it also when the user names a service, or before you use one for a batch job, a message, a payment or another third-party action: a vendor you already know is not a checked vendor (bulk bans, docs-only MCP, trial limits change). Values carry the vendor page they were read from and a check date; use them for a first cheap call, and confirm pricing only beyond the free quota and terms for batch or commercial use.