Privacy Policy

Last updated 3 August 2026

VerifyMCP is designed to need as little of your data as possible. This policy explains what we collect, why, and the choices you have.

Analytics

We use privacy-friendly, cookieless analytics (Datafast) to understand aggregate traffic: which pages are popular and roughly where visitors come from. It does not set advertising cookies, does not track you across other sites, and does not build a personal profile of you.

Accounts

You sign in with GitHub or Google; we never store a password. That provider tells us your name, your verified email address, your profile picture and your account id with them. We use the email address to identify your account and to send service messages you ask for. We do not read your repositories, and we never post anything on your behalf. The access token the provider issues is stored encrypted so we can confirm who you are, and it is deleted with your account. If you sign in with both providers using the same verified email address, they resolve to a single account. You can request deletion of your account and associated data at any time (see “Your rights” below).

Payments

Advertising placements are billed through Stripe. Stripe processes card details directly; we never see or store your full card number. Stripe's handling of that data is governed by its own privacy policy.

What we don't do

We don't sell your personal information, we don't run third-party advertising trackers, and the trust scores we publish are derived entirely from public data about MCP servers, not from anything about you.

Your rights

Depending on where you live, you may have the right to access, correct, or delete the personal data we hold about you, and to object to certain processing. To exercise any of these, email hello@verifymcp.io and we'll respond within a reasonable time.

Changes

We may update this policy as the site evolves; material changes will be reflected in the “last updated” date above.