Privacy — MCP Liveness

Who holds it

Your data is held by TrainedBooks, an independent software business in California, United States, which operates the agentwares products. Questions and deletions: https://agentwares.vercel.app/contact.

Data is stored in the United States. If you are in the EEA or the UK, that is a transfer outside your region, and using the tool is you asking us to provide it from there.

No account, no cookies

MCP Liveness needs no account, key or signup. It sets no cookie, stores nothing in your browser and does not follow you to other sites.

When an AI assistant calls it as an MCP tool, it receives the arguments of that call and nothing else: not your conversation, your files or your account with the assistant.

What it counts

Each call is counted, so that we know whether the tool is used and how it answers:

• liveness_check: one row per check, holding which surface it arrived on (the web API or the MCP server), the one-word outcome it answered (such as usable, needs_credential or unreachable), and whether the caller was one of our own scripts.
• Each page you open here sends one page view: this site's host and the page's path (never its query string), the host of the page that linked you here if there was one, and two yes-or-no flags — whether the browser looks like a crawler and whether it is one of ours. The browser's user-agent is read to set those flags and then discarded. No cookie, no fingerprint, no network address.

A counted call never holds the name, URL or site you asked about, your network address or your user-agent: what you looked up and who you are are not part of it.

What it keeps about your request

Nothing beyond the count. The server name or URL you ask about is used to answer you and is not written to our database or to any log of ours.

To keep one client from turning the tool into a crawler, your network address is held in the server's memory for up to a minute to count your requests. It is never written to storage.

An answer may be served again from our host's cache for up to 75 minutes, so that a second caller asking about the same server does not cause another probe. The cached copy is keyed by the question, not by who asked.

If you write to us through the contact form, that message is covered by the privacy note at https://agentwares.vercel.app/privacy.

Who it talks to

To answer, it makes requests to the MCP server you name — one connection with no credential, and on a 401 the discovery documents it publishes — and to the official MCP registry to look a name up. Those requests come from us and say so in their user-agent; they carry nothing of yours.

Who else touches it

• Vercel, which hosts it in the United States. Vercel keeps its own log of each request — its path and query string (so the name or URL in a check made over the web API), the requesting network address and the user-agent — for one day on our plan, and we read it only to fix faults. The arguments of an MCP tool call travel in the request body, which we do not log.
• Neon, which holds the counted rows, in the United States.

How long we keep it

• Counted rows identify nobody, so they are kept without an expiry date, as the running tally of how the tool is used.
• Vercel's request log: one day.

What we do not do

We do not sell data, set cookies, build profiles, or use anything you send to train models. We share nothing except with the processors above, and only to run the tool.

Your rights

Ask and you get a copy of anything we hold about you, a correction, or its deletion — whether or not the law where you live requires it of us. Ask at https://agentwares.vercel.app/contact. We aim to answer within 30 days.