---
title: "Privacy Policy | mcp.tc"
description: "What personal data mcp.tc processes, why, for how long, who else sees it and how to exercise your rights."
url: "https://mcp.tc/privacy"
markdown: "https://mcp.tc/privacy.md"
lang: "en"
---

# Privacy policy

What personal data mcp.tc handles, why, for how long, and what you can ask us to do about it.

Last updated 26 Oct 2026

## Who is responsible

The data controller is Marco Costantino, Italy. For anything about your data, write to [privacy@mcp.tc](mailto:privacy@mcp.tc?subject=Privacy%20request). No data protection officer has been appointed, because the law doesn’t require one for a project of this kind.

## What we process and why

| What | Data | Why, and on what basis | How long |
| --- | --- | --- | --- |
| Visiting the site | Every request passes through Cloudflare, which sees your IP address and the request and answers most pages from its cache, so many visits never reach our server. Requests that do reach it are written to our web server’s logs: IP address, date and time, the page requested, response code, referring page and browser user agent. | Running the site and keeping it secure, including Cloudflare’s security checks and a limit on how many requests one address can send. Legitimate interest, GDPR art. 6(1)(f). | Our logs 14 days, then deleted |
| Visit statistics | When you open a page of the site, the page adds one to the site’s daily totals, together with which page it was (its address without the query string), the name of the site you came from, the country Cloudflare reports for your connection, the page’s language and the kind of device and operating system your browser reports. The first time you move the pointer, touch the screen, use the mouse wheel or press a key on a page, it sends a second request that says only that this happened, so we can tell people from automated programs. On a listing page we also add one to that listing’s daily totals when you open it or click one of its buttons (copy, add to a client, a setup tab, a link to the server’s homepage, repository or docs). We keep totals only, never linked to your IP address or to you. To count each visitor once a day, we keep a keyed hash of your IP address in memory, with the site you came from, your country, device and system, and which listings you opened and which of their buttons you used; it expires after 24 hours. The key changes every day, so the same address can’t be recognised from one day to the next, and the hash is never saved to our database, files or logs. The same hash, with a counter kept in memory for an hour, stops floods of these requests. The page sends the visit and each click in a small request of its own. It sets no cookies, stores nothing in your browser and doesn’t run on badges, cards or iframes on other sites. We don’t ask for consent for these counts: they are our own, kept as totals only, and use no cookie or identifier in your browser. | Knowing how the site is used and how much of its traffic comes from people rather than automated programs (Google Analytics sees only the visitors who accept it), showing a listing’s verified owner how it is used (sources and countries with only a few visits are grouped together), and ordering the directory. Legitimate interest, art. 6(1)(f). | The totals 13 months; the hash expires after 24 hours and is kept in memory only |
| An MCP client pointed at a quick link | Your MCP client connects to a listed server directly, without us. If a client is given a quick link instead, our server answers with an error that names the server’s own URL or install command, and passes nothing on to the listed server. These requests aren’t written to our access log; a failed request can appear in the error log with your IP address. | Telling the client where the server really is. Legitimate interest, art. 6(1)(f). | Nothing is kept. A failed request can appear in the error log, kept 14 days. |
| Seeing an mcp.tc badge, card or iframe on another site | Your browser fetches the file from mcp.tc, which sees your IP address like any web server. Cloudflare usually answers these requests from its cache, so many of them never reach our server. Requests for these files aren’t written to our access log, the files set no cookies, and the badge and card load nothing else. | Showing the embed the site’s owner added. Legitimate interest, art. 6(1)(f). | Nothing is kept. A failed request can appear in the error log, kept 14 days. |
| Reading the blog | The same as for any page (visiting the site, above). Posts have no comments, sign-up forms or share buttons and embed nothing from other sites; the Atom feed is a plain file that your feed reader downloads. | Publishing articles about MCP servers. Legitimate interest, art. 6(1)(f). Statistics as on every page (Google Analytics, below). | As for visiting the site |
| Suggesting a server | The URL you submit, your optional note, the time, and a keyed hash of your IP address. The URL and the note are checked automatically, including by an AI model, so please don’t put personal data in the note. A suggestion sent from a script as a JSON request is handled the same way, with the same data and checks. | Handling the suggestion and preventing abuse. Legitimate interest, art. 6(1)(f). | Up to 12 months, or as long as the listing it created exists |
| Being told when a server you suggested is listed | The email address you give in the optional “Email me when it’s listed” field, or as `notify_email` in a suggestion sent as JSON. It is kept with your suggestion, shown to no one and never sent to the AI check. | Sending the one email you asked for when the server is listed. Your request, art. 6(1)(b). | Until that email goes out. If the server isn’t listed (the suggestion is turned down, or it isn’t listed within 90 days), we delete the address without writing. The email we send is then kept like every other (see “Emails we send”) |
| Verifying a listing | The listing, the domain you picked, the time, what our DNS lookups found, and a keyed hash of your IP address. We keep a request only when we find the DNS record. | Handling the request and preventing abuse. Legitimate interest, art. 6(1)(f). | The IP hash 30 days; the request up to 12 months after it’s decided, or as long as the checkmark it granted stays |
| Rate limiting | A keyed hash of your IP address and a counter | Stopping floods of submissions, verification attempts, requests to our MCP server at `/mcp` and uses of the stop links in change emails. Legitimate interest, art. 6(1)(f). | Up to 2 days |
| Checking a suggestion with AI | The URL you submitted, your note, and public information about the server (its manifest, tool list, repository and package pages). Never your IP address. | Drafting and reviewing the listing. Legitimate interest, art. 6(1)(f). | Sent to the AI model’s provider only for the check; what the provider keeps follows its terms |
| Statistics (Google Analytics) | Without statistics cookies (in the EU, the EEA, the UK and Switzerland until you accept, and anywhere after you refuse): signals without cookies about the page you view (address without its query string, and title), the time, your browser and device, and your IP address, which Google uses for a rough location. With statistics cookies (if you accept, or outside those regions unless you refuse): also pseudonymous identifiers in cookies, the words you search for in the directory, links you follow to other sites and how far you scroll. | Counting visits to see what people use. Statistics cookies in the EU, the EEA, the UK and Switzerland: your consent, art. 6(1)(a) and art. 122 of the Italian Privacy Code. Signals without cookies, and statistics cookies elsewhere: legitimate interest in measuring how the site is used, art. 6(1)(f); you can refuse or object at any time in Cookie settings. | 14 months in Google Analytics; cookies as listed in the [cookie policy](https://mcp.tc/cookies) |
| Writing to us | Your email address and what you write. Mail to privacy@mcp.tc (data, reports, legal matters) and support@mcp.tc (help with the site) passes through Cloudflare’s email routing on its way to our mailbox at Google Workspace. | Answering you, and keeping a record of reports and requests. Legitimate interest, art. 6(1)(f), or a legal obligation for reports under the Digital Services Act, art. 6(1)(c). | As long as the conversation needs, then up to 24 months |

We back up the database once a day and keep each backup for 14 days on the same server, so data deleted from it (suggestions, rate-limit hashes, a deleted account with its sessions and claims) can stay in a backup for up to 14 more days.

Your cookie choice and the preferences you set (theme, the setup tab you last picked, the language note) are stored in your own browser, not on our server, and so are the sign-in cookies of accounts. The [cookie policy](https://mcp.tc/cookies) lists every item by purpose.

## People named in listings

Listings describe software, but they can include personal data: the name or username of a server’s maintainer, links to their repository or website, and similar details. We take these from public sources only: the server’s own MCP metadata and server card, the official MCP Registry, GitHub, npm and PyPI. We publish them because a directory has to say who makes a server (legitimate interest, art. 6(1)(f)). They stay as long as the listing does. You can ask us to correct or remove them at any time, and you can object to the processing; see [your rights](https://mcp.tc/privacy#rights).

## Accounts

You need an account only to follow listings or to manage the listing of a server you run. You sign in with a code sent by email or with GitHub; nobody else sees your account.

| What | Data | Why, and on what basis | How long |
| --- | --- | --- | --- |
| Your account | Your email address; if you use GitHub, your GitHub user id, username, display name and primary email address (we use that address for account notices, change emails and to fill in your settings); when you created the account and last signed in; the listings you claimed, how you proved each one and whether our daily check still finds that proof; the site language you last used on your account pages and, if you pick one in Settings, the language for your emails; both only choose the language of the emails we send you | Signing you in, letting you follow listings and manage your own: the service you asked for, art. 6(1)(b) | Until you delete the account |
| Following listings | The listings you follow and since when, your choice of change emails (as changes happen, a daily summary or none), when we last emailed you about changes and which changes that email covered | Emailing you when a listing you follow changes: the service you asked for, art. 6(1)(b) | Until you unfollow the listing or delete the account |
| Your edits | What you changed on a listing, the old and the new text, and when. Each saved change also appears in the listing’s public History as a change by the server owner, with no name or account; the History shows the text before and after (for setup notes, only that they changed). If we undo an edit, we hide its entry, and you can ask us to hide an entry, for example one that shows something you took off the listing. | Publishing your changes, undoing abusive ones and answering reports. Legitimate interest, art. 6(1)(f). | As long as the listing exists. When you delete your account, the edits stay without anything that links them to you. |
| Signing in | The sign-in cookie (we store only a hash of it) and, with each session, keyed hashes of your IP address and browser; for an email code, keyed hashes of your address and of the code; the domain checks you ran | Keeping you signed in and preventing abuse of sign-in and claims. Art. 6(1)(b) and (f). | Sessions: 30 days after your last visit to your account pages, one year at most. Codes: 24 hours. Domain checks: 90 days. |
| Emails we send | For each email: your address, which email it was (a sign-in code, an account notice, a change email or the notice that a server you suggested is listed) and its language, the subject and the text that filled it in (a sign-in code is stored as dots, never the code itself), when it was sent and Scaleway’s delivery status | Checking that our emails arrive and answering questions about them: legitimate interest, art. 6(1)(f) | 90 days. Deleting your account deletes these records at once, except the email that confirms the deletion, which we keep until its 90 days are up as a record that we told you |

**Email codes** are sent through Scaleway Transactional Email, run by Scaleway SAS in France, which receives your address and the code in order to deliver the email and processes them as our processor under its data processing agreement. Scaleway hosts and processes this data only in the European Union. We send account notices the same way: when your address or a sign-in method changes, when the account is deleted, and when a listing is added to it or editing one is paused. Scaleway then receives your address and the text of the notice. If you follow listings, we send change emails the same way, as changes happen or as a daily summary, as you choose: Scaleway then receives your address, the names of the listings that changed, a short summary of the changes, links to them and a personal link that stops these emails without signing in. **GitHub sign-in**: you sign in on GitHub (GitHub, Inc., United States), under GitHub’s own privacy statement, and GitHub sends us your user id, username, display name and primary verified email address. We use GitHub’s access token only to read those details and revoke it straight away. The section [Transfers outside the EU](https://mcp.tc/privacy#transfers) explains how data sent to GitHub is protected.

You can unfollow a listing or turn change emails off at any time on your Following page. You can delete your account yourself in its settings: the account, its sessions, codes, claims and follows go at once. The changes you made to listings stay public as listing text and in the listings’ History.

## Who else sees data

- OVH SAS (France) hosts the server that runs mcp.tc, in its data centre in Roubaix, France.
- Cloudflare, Inc. sits in front of the site as a content delivery network, cache and firewall, so it sees every request, including your IP address. It also receives the reports your browser may send about failed connections to mcp.tc, and forwards email sent to privacy@mcp.tc and support@mcp.tc to our mailbox.
- Scaleway SAS (France) sends the sign-in codes, account notices and change emails from the European Union; GitHub, Inc. signs in people who choose GitHub. See [accounts](https://mcp.tc/privacy#accounts).
- Google Ireland Ltd and Google LLC receive statistics data as our processors under Google’s data processing terms: in the EU, the EEA, the UK and Switzerland only signals without cookies until you accept statistics, elsewhere also statistics cookies unless you refuse them. Google signals and ad personalization are turned off for our property. Google Ireland Ltd also provides, as our processor, the Google Workspace mailbox where we read the email you send us.
- The provider of the AI model that checks suggested servers receives, for that check only, the URL, the note and public information about the server (see the table above), never your IP address. It also translates listings, which are already public text.
- Better Stack, Inc. checks from outside whether mcp.tc is up, which involves no visitor data, and hosts our status page, status.mcp.tc. We chose Better Stack’s EU data region, and Better Stack says it processes personal data primarily in the EU. We have switched analytics off in the status page’s settings, but the page still loads Better Stack’s own Google Analytics and Google Ads tags, which set cookies that mcp.tc doesn’t use; the [cookie policy](https://mcp.tc/cookies#others) lists them.

We don’t sell data or share it with advertisers.

## Transfers outside the EU

Cloudflare, Google, GitHub and the provider of the AI model that checks suggestions are based in the United States or share data with US companies. Those transfers rely on the EU-US Data Privacy Framework (Commission decision 2023/1795) for certified companies, and on the European Commission’s standard contractual clauses otherwise. Our Google Workspace mailbox is covered by Google’s Cloud Data Processing Addendum, which relies on the same two mechanisms. Scaleway, which sends our emails, processes them only in the European Union.

The server that runs mcp.tc is in France, in the EU. Better Stack keeps our status page and uptime checks in its EU region; if personal data leaves the EEA, Better Stack says it relies on an adequacy decision or on safeguards such as standard contractual clauses.

## Automated decisions

Whether a suggested server is listed is decided partly by automated checks and the AI reviewer, with a person reviewing anything they can’t confirm. The decision is about software, not about you, and has no legal or similarly significant effect on anyone, so art. 22 GDPR doesn’t apply. You can still ask a person to look at any decision.

## Your rights

You can ask to see the personal data we hold about you, have it corrected or deleted, restrict how we use it, or receive it in a portable format. You can object to processing based on legitimate interest, and you can withdraw your consent to statistics, or refuse them, at any time with the Cookie settings link in the footer; withdrawing doesn’t affect what happened before. Write to [privacy@mcp.tc](mailto:privacy@mcp.tc?subject=Privacy%20request). We answer within one month.

If you think we got something wrong, you can complain to the Italian data protection authority, the [Garante per la protezione dei dati personali](https://www.garanteprivacy.it), or to the authority where you live or work.

## What you have to give us

Nothing. You can use the site without giving us any personal data. The submit form needs only a server URL; the note is optional. Don’t include personal data in the note: the URL and the note are checked automatically, including by an AI model. You need an account, with an email address or a GitHub account, only to follow listings or to manage the listing of a server you run.

## Changes to this policy

When we change how we handle data, we update this page and the date at the top. If a change means we need your consent again, the cookie window asks for it.

---
Source: https://mcp.tc/privacy. Markdown version for AI agents (ask for `text/markdown` or add `.md` to the address). Site overview: https://mcp.tc/llms.txt
