Privacy Policy

Last updated: 2026-11-18

This site (“Valksor MCP servers”, at https://mcp.valksor.tools) is a free, public index of Valksor's MCP servers. It also offers a passthrough: one MCP endpoint and one JSON API that forward your requests to the Valksor dictionary servers, to margrave and to the Paņem brīvdienu calendar. It is a valksor.com service. Each of these servers has its own privacy policy on its own site: margrave at margrave.valksor.tools/privacy, and the calendar at panembrivdienu.lv/privacy-policy (in Latvian: /privatuma-politika).

1. Who is responsible

The controller is SIA Valksor (registration number 40203690663), Mores iela 36-1, Riga, LV-1034, Latvia. For any question or request about your data, write to [email protected].

2. No accounts, ads, or tracking

There are no user accounts and no logins. We do not run advertisements, use analytics or tracking tools, or build profiles, and we never sell or share data for marketing. The application sets no cookies of its own. Cloudflare, which sits in front of the service (see “Recipients”), may set a technical security cookie (for example cf_clearance).

3. What we process

Your requests. The static pages store nothing of yours. When you use the passthrough endpoints (/mcp and the JSON API under /api), the hub forwards your request — the tool or API call with its arguments, such as the word you look up — to the server you address, and returns the answer unchanged. The hub reuses public tool and prompt definitions for up to 15 seconds. It contacts servers when it refreshes those definitions, answers the dictionaries tool, or looks up a suggestion for an unknown tool name. These checks can contact every sibling, including margrave and the calendar. The hub keeps no copy of your queries or the answers. Depending on the query, a dictionary server may in turn send the query text to its own upstream dictionary source, as its privacy policy describes (for example Wikimedia's en.wiktionary.org, or livonian.tech). Please do not put personal or sensitive information into queries.

The calendar's latvia_leave_entitlement tool can take a birth date. The hub forwards it to the calendar and neither keeps nor logs it.

Your IP address. The hub also passes your IP address to each server it contacts as described above, so that the server's rate limit applies to you rather than to all hub users together. The dictionary servers and margrave receive it in a CF-Connecting-IP header and use it only in memory for rate limiting, as described below. The calendar receives it in an X-Forwarded-For header. It uses it for rate limiting and also writes it, with the name of the tool called, to its own request log, which it keeps for the time its own privacy policy states.

4. Logs and your IP address

No access log. The web server does not write a log line per request, so your IP address, the words you look up and the query strings you send are not recorded in a request log. The application's own log keeps operational messages (start-up, errors and upstream failures). It does not record your queries or IP address, with one exception: a request to the disabled internal path /admin/metrics is logged with its connection details (IP address, user agent and similar headers), because that path is a probe for misuse. Each container's log is capped at about 30 MB and is normally cleared at the nightly restart of the service, so it is usually kept for no more than a day. The legal basis is our legitimate interest in running and securing the service (GDPR Article 6(1)(f)).

Rate limiting. To prevent overload, the server keeps your IP address (IPv6 addresses are reduced to their /64 network) and a request counter in memory. An entry is dropped once its limit has reset, typically within about a minute of your last request. It is never written to disk and is lost when the service restarts.

We also keep aggregate counters (requests, errors and timings) for reliability. They contain no IP address or query text.

5. Caching

The servers the hub forwards to cache dictionary responses, as their own policies describe.

6. Recipients and transfers

The dictionary servers, margrave and the calendar can also receive your IP address with a request for their tool or prompt list. The hub sends such requests when it refreshes its cached definitions, checks reachability for dictionaries, or looks up a suggestion for an unknown tool name.

We do not sell, rent, or share data with anyone for marketing.

7. Legal basis

We process this data on the basis of our legitimate interest in providing, securing and protecting the service (GDPR Article 6(1)(f)), limited to the minimum described above.

8. Your rights

Under the General Data Protection Regulation (GDPR) you have the right to access, correct and delete your data, to restrict its processing and to object to it. Because we keep no accounts, and the hub keeps no request log, there is normally nothing to retrieve or delete here; if you make a request, tell us the approximate time of your visit. The calendar does keep a request log. A request about that log goes to the calendar, through its own privacy policy. You also have the right to lodge a complaint with the Data State Inspectorate (Datu valsts inspekcija) in Latvia, or with the supervisory authority of your own country.

9. Changes

Changes to this policy are published on this page with a new “Last updated” date.