This site is a few pages of text and links, and one MCP endpoint. There is no account to make, no form to fill in, no cookie, no analytics script, no advertising and no third-party request of any kind — the pages, the stylesheet, the fonts and the one script all come from this domain.
What the pages store, and where
One thing: your colour theme, written to this browser’s local storage under this site’s own key. It never leaves the browser, it is not readable by any other site on the network, and clearing your site data removes it. If you never touch the theme picker, nothing is stored at all.
Server logs
Pages are served from a content-delivery network, which keeps the ordinary operational request logs any web server keeps. They are not joined to anything, not used to profile anyone, and not shared.
What a request to the endpoint carries
An AI client calls the endpoint at /mcp with an HTTP POST whose body is one JSON-RPC message: the name of a tool and its arguments — an instrument, a note, a chord or scale name, a chord symbol or a list of them, a number of semitones. When a client first connects it also sends, as the protocol asks, its own name and version; the endpoint reads only the protocol version from that message. Like any web request, each one also arrives with your IP address and the headers your client sends, such as its user agent. The endpoint asks for no account, no key and no cookie, starts no session, and refuses any request larger than 64 KiB without parsing it.
What the endpoint keeps: nothing
The endpoint answers each request from data built into the site and keeps nothing from it: it writes no database, no file, no cache and no analytics record, and it sends every answer marked not to be stored (Cache-Control: no-store). Every caller gets the same answer to the same question, so there is nothing about you for it to remember from one request to the next.
What the logs record
The endpoint’s own code writes nothing to any log — not your question and not its answer. The site runs on Cloudflare Workers with Cloudflare’s request logging switched on, which records details of each request and its response, such as the path, the response status and the country the request came from, and Cloudflare keeps those records for at most seven days. If the site itself fails while answering, it adds one error line naming the address that was requested and the error. As with the pages, these logs are not joined to anything, not used to profile anyone, and not shared.