Terms of use
Version 1.0 · effective . When these terms are replaced, the version and date change with them, so a reader can tell that they did.
Status of this document
MCP Verify is not yet incorporated. No company stands behind these terms; they are between you and the operator of mcpverify.ai, reachable at [email protected].
No choice of law is asserted while the operator is unincorporated. This is a disclosed absence rather than a silent one: there is no jurisdiction named here because there is not yet an entity to name one for.
This document has not been reviewed by a qualified lawyer. It is written to describe what actually happens rather than to transfer risk, and it is published in that state rather than withheld until it reads more formally.
Who these terms are with
These terms are between you and the operator of mcpverify.ai, reachable at [email protected]. There is no company to name, and naming one that did not exist would be the first false statement on this site — on the page that governs every other one.
What this site is
A record of what we observed when we opened a read-only protocol handshake against a publicly listed endpoint, and when we last looked. Each observation is dated, and batches of them are anchored so that the set cannot be altered afterwards without that being detectable.
What the record does not claim
- It is not a certification and not a guarantee. We publish evidence about what was observed. We do not warrant that any server is fit for any purpose, and nothing here should be read as approval or disapproval of an operator.
- Anchoring proves existence, not truth. It establishes that a given root existed by a given time. It says nothing about whether an observation was correct when it was made. These are separate claims and we do not blur them.
- An observation is a point in time, not a present state. The record states when we last looked. It does not assert what is true right now.
- The record is provided as-is. Decisions you make on the strength of it are yours. Where a record looks wrong, corrections is the route, and we would rather hear from you than not.
While this build is pre-launch
Every endpoint record shown here is a dated observation of a real MCP endpoint, rendered from the published archive. It is not a complete record of any endpoint and not a complete record of the ecosystem: it covers the snapshots in the export this build was made from, and it is built rather than queried, so no figure on it describes the present moment.
No claim is accepted and nothing is collected in this state — see privacy. If you operate an endpoint recorded here and something is wrong, corrections is the route, and it does not require a claim.
Using the record
You may read, quote and check anything published here, and we would prefer you check it. Where you cite a figure, cite what it is a figure of — the methodology page exists so that a number taken from this site can be reported with the context that makes it true.
Do not present the record as a certification, a rating, or an assessment of anyone's intent. That is not what it is, and it is the misreading most likely to cause harm to a third party who did not ask to be measured.
Appearing on this site
Endpoints are observed because they are publicly listed. If you would rather not appear, delisting sets out what we can do and the part of the published record that cannot be withdrawn by anyone, including us.
Changes
These terms will change — most obviously if an entity is incorporated, at which point the two notices above stop being true and must stop being displayed. Any replacement carries a new version and effective date.