Privacy Notice
This describes what Clear Data Decisions LLC, operating MCP Checkup, collects about you and why.
What we collect
Your email address (sign-in), the times you signed in, and the targets (endpoint URLs or package names) you add. If you follow servers, we keep which ones you follow, when you followed each, and the language (English or Chinese) of the page you followed it from. There is no password to collect, because there is no password. If you pay for a subscription, Stripe handles and stores your payment details — we don't see or store card numbers. The first time you use account features, we ask you to agree to the Terms and keep a record of it: your account ID, the date of the Terms version you agreed to, the date of the Privacy Notice at that moment, and when you agreed. We keep this record for as long as your account exists and delete it when the account is deleted.
Usage records
When anyone calls our MCP endpoint, we record when it happened, the method and tool called, the outcome, how long it took, the name and version the client gives for itself, the first product token of the User-Agent header (such as python-httpx/0.27.0), and which server was asked about, with any user name, password, query or fragment removed from an address. These records leave out the rest of a call's arguments (including the address given to request_check), the text of a search, request headers (apart from that first product token, from which the client name may also come) and IP addresses. In place of an IP address we store a keyed one-way hash of it, so that repeat callers can be counted; some records have none. These records are deleted after 90 days. Daily totals — the number of calls per method, tool and outcome, the number of distinct callers, the number of calls and of sessions by kind of caller (our own checks, known monitoring services, connection checks, tool use, other; calls without a hash are counted apart), the number of tool-use calls per tool and of tool-use sessions by client name (names used by fewer than two callers on a day are counted together), and the number of on-demand checks by where they came from and outcome, of sign-ups, of accounts that signed in, of checkouts started and of completed checkouts — are kept without an end date; none of them holds a hash or an account, and a client name is kept only as the client gave it. When an on-demand check runs, from our website or through request_check, we record when, where it came from, the outcome, the host name of the address checked and the same kind of hash. We also keep the check's result, with the address checked unless that address contained a user name, password or query; its page is shown for 24 hours. Both are deleted after 30 days and are not moved to cold storage. When a lookup or a search finds nothing, we keep its text, cleaned the same way, for 90 days so we can add servers people ask about. For an account, apart from its last sign-in time, we keep a record of when you sign in (at most one in any 10 minutes) and of each time you start a checkout; these two kinds of record are deleted after 90 days. Database backups made from 2026-10-02 on leave all of these records out, except the daily totals. Backups made before that date may contain the on-demand check, lookup and search records described above, and some of those backups are kept without an end date.
Why
To sign you in, to run checks against the targets you've added, to keep the list of servers you follow, to send you the emails the service depends on (sign-in links, check results you've opted into), and to bill a paid subscription.
Who it's shared with
Supabase (database and authentication), Resend (delivers our emails: the sign-in email, via Supabase's own SMTP integration, and alert emails, which carry your email address, the names of the servers they are about, and what our checks recorded about them; you get emails about the servers you follow unless you turn them off on your account page or with the unsubscribe link in any of those emails, and follows over your plan's limit get none), and Cloudflare (hosting and storage). Sentry (error reporting). When a page in your browser or our server hits an unhandled error, a report goes to Sentry with the error stack, the page address with any tokens removed (non-credential query parameters such as the tested endpoint stay in it), the browser's user-agent header, and the identifier of the code release that was running. The report does not include cookies, authorization headers, other request headers, request or response bodies, or email addresses. Reports from a page are sent by your browser, so Sentry sees your connection's IP address in the course of receiving them; reports from our server are sent by our server. We do not attach your IP address to either. Once billing is live, Stripe processes payments. None of these processors receive more of your data than their role requires.
What's public regardless of an account
Check results against publicly reachable MCP servers are published as evidence, whether or not the server is claimed — see the Terms for what claiming does and doesn't change.
Retention
We keep account and check data for as long as the account is open. Check records (each check run, its results and its signed evidence) and tool-list history stay in our database for at least 30 days. After that, most of them are moved to cold storage, where they are kept without an end date, with their content and any signature unchanged; attestation links keep working. Each server's latest results, its current tool list, its recorded tool-list changes and its day-by-day record of whether it answered (the daily grid on its report page) stay in the database. Internal records of when checks were scheduled are deleted after 30 days and are not copied. Database backups made before a record was moved may still contain it. Deleting your account removes your email and claim relationships; published check evidence for servers you don't own outright may remain, since it documents what a publicly reachable server did, not something private to you.
Your choices
You can remove targets, change your email, or ask us to delete your account by writing to support@mcpcheckup.com.
Changes
We may update this notice; the date above reflects the last change.
Contact
support@mcpcheckup.com.