Stateless 2026-07-28 read-only MCP server for aggregate HitKeep analytics and official docs.
io.github.PascaleBeier/hitkeep — Model Context Protocol (MCP) server
This stateless, 2026-07-28 read-only MCP server aggregates HitKeep analytics and serves official docs. It is provided as a single binary and is positioned for AI-native web analytics workflows, including privacy-focused and self-hosted use.
🛠️ Key Features
Stateless operation
Read-only MCP server
Aggregated HitKeep analytics access
Official documentation included
🚀 Use Cases
Analytics and analytics dashboard workflows
Conversion analytics tracking
Cookieless/privacy-friendly web analytics
AI visibility and AI-analytics use cases
Web and website analytics with custom domains, data sovereignty, and self-hosting
⚡ Developer Benefits
Works with Model Context Protocol
Supports a “single binary” distribution model
Topics cover analytics, Go, DuckDB, ecommerce analytics, and Google-analytics alternative contexts
⚠️ Limitations
Read-only by design
Stateless by design (does not retain server-side session state)
AI native, sovereign, privacy-first web analytics in one binary.
100% open source under MIT, HitKeep unifies traffic, conversions, Search Console, and AI visibility with custom tracking domains, SSO, open exports, and no separate database, queue, or cache.
100% open source. The complete product is MIT-licensed. Custom tracking domains and team SSO live in the same public codebase—not in a separate proprietary edition.
Full data sovereignty. Self-host one Go binary with embedded DuckDB and NSQ, or export your data in open formats. Complete takeout, APIs, webhooks, share links, and permissions keep the data useful outside HitKeep.
AI-native analytics. HitKeep treats AI as a first-class traffic channel: crawler fetches, AI-referred visits, and chatbot outcomes remain distinct. Ask AI uses cited aggregate evidence, while read-only MCP gives approved assistants governed analytics access.
Privacy by default. The browser tracker sets no analytics cookies, respects Do Not Track, and collects focused website analytics without building a cross-site identity.
Reporting that reaches the outcome. Follow acquisition through pages, automatic and custom events, goals, funnels, ecommerce revenue, UTM and QR campaigns, Search Console, and Web Vitals.
Self-host the complete open-source product, or use HitKeep Cloud in a managed EU or US region when you do not want to operate it yourself.
HitKeep is web-focused. It favors aggregate traffic and conversion evidence over visitor profiles, session replay, mobile SDKs, or built-in experimentation. The result is a smaller collection boundary and operating surface without stopping at a basic pageview counter.
Quick Start
On Apple silicon macOS or x86_64 Linux, install HitKeep with Homebrew:
Native Android passkeys are disabled by default. Browser passkeys keep the existing web origin, relying-party ID, user-verification, challenge expiry and MFA requirements.
To opt in, an operator needs the real release application ID and the SHA-256 fingerprint of its app-signing certificate. For Google Play distribution, use the Play app-signing certificate, not the upload key. Neither a debug certificate nor a package name alone establishes the release application's identity. HitKeep supplies no default package or certificate trust.
Configure both settings for the canonical HTTPS instance:
yaml
passkey-android-package-name:"<release application ID>"passkey-android-sha256-fingerprints:"<32 colon-separated hexadecimal bytes from the release certificate SHA-256>"
Their environment variables are HITKEEP_PASSKEY_ANDROID_PACKAGE_NAME and HITKEEP_PASSKEY_ANDROID_SHA256_FINGERPRINTS. Multiple explicitly approved release certificates, such as during signing-key rotation, are comma-separated. Wildcards, malformed fingerprints, missing paired settings and non-HTTPS public URLs are rejected. These placeholders are intentionally invalid; do not deploy them as values. Empty settings leave native Android passkeys off.
For each fingerprint, the backend accepts only the exact opaque origin android:apk-key-hash: followed by the unpadded URL-safe Base64 encoding of those 32 digest bytes. It does not add Android origins to the browser-origin list or relax passkey verification. Package metadata is bound to the certificate by Android's Digital Asset Links verification; the opaque WebAuthn origin itself contains the certificate digest, not the package name.
At each configured relying-party host, publish this public association document at https://<instance-host>/.well-known/assetlinks.json:
Use the same complete certificate list in the association and backend configuration. If verified app links are also required, their separate association may additionally grant delegate_permission/common.handle_all_urls. Serve the association as JSON over HTTPS without authentication or a redirect; do not return the dashboard HTML fallback. Keep Apple AASA associations separate.
For managed Cloud, both cloud.hitkeep.eu and cloud.hitkeep.com need their own matching association delivery before enabling the backend settings. Association delivery belongs to the operator/proxy deployment; these settings do not publish the file or deploy infrastructure. The official Play application ID and release signing fingerprint must be verified by the release owner before enabling production trust. Capability advertisement is enabled only for valid, nonempty configured Android origins; it cannot certify that a separately deployed association file or a real device is working.
Pageviews and supported automatic interaction events—outbound clicks, file downloads, and form submissions—start flowing immediately. Use the custom events guide for product-specific actions such as signups, purchases, or qualified leads.
Explore HitKeep
See AI visibility, ecommerce, Search Console, Ask AI, and Assistants
AI visibility
Ecommerce
Search Console
Ask AI
Assistants
Documentation, Community, and Support
Find answers in the documentation, report reproducible bugs through GitHub Issues, and disclose vulnerabilities privately through the security policy.
Contributor quick path
Run ./hk setup, then start seeded development with ./hk dev --seed or use ./hk dev --detach. Capture product proof with ./hk screenshot; inspect ./hk catalog commands --output json and ./hk catalog configuration --output json instead of copying mutable workflow facts. Validate with ./hk qa pr. The Compose stack and complete workflow live in CONTRIBUTING.md.
HitKeep includes the DuckDB extensions required for S3 backups and XLSX exports.
It does not download extensions at startup. On first use, bundled files are
extracted into HITKEEP_DATA_PATH/.duckdb/extensions; this directory must be
writable by the process running HitKeep and reside on a mount without noexec.
The cache is disposable and can be
recreated without network access. No HOME override or separate extension
installation is needed for binary, Homebrew, or container deployments.