HitKeep

io.github.HitKeep由 GitHub 帳號 HitKeep 發布v2.17.0更新於 Nov 17, 2026

Stateless 2026-07-28 read-only MCP server for aggregate HitKeep analytics and official docs.

發布方自己的服務:Keep

已驗證Streamable HTTP可網頁執行網頁搜尋與抓取資料與分析

概覽

AI 產生的概覽

唯讀的遠端 MCP 端點,讓助理在受管控的前提下存取 HitKeep 網站的彙總分析資料與官方文件。

可以做什麼
  • 查詢 HitKeep 彙總分析:流量、轉換、目標、漏斗、電商營收、UTM 與 QR 活動、Search Console 和 Web Vitals
  • 檢視 AI 可見度資料,例如爬蟲抓取、來自 AI 的造訪與聊天機器人成果
  • 在分析證據之外檢索 HitKeep 官方文件
  • 以附引用的彙總證據作答,而非個別訪客輪廓
適用情境
當你自行架設或使用 HitKeep 執行個體,希望讓經過核准的助理回答網站流量與轉換問題,或查閱 HitKeep 文件,又不想給它分析帳戶的寫入權限時適用。
執行需求
需要一個可連線的 HitKeep 執行個體(自架或 HitKeep Cloud),在你的 HitKeep 主機上提供 MCP 端點,透過 streamable HTTP 連線。必須驗證:在 Authorization 標頭中提供限定範圍的 HitKeep API 用戶端 bearer 權杖;相容的執行個體也接受針對所設定 MCP 資源的 OAuth 存取權杖。
安裝前請注意
Authorization 中的 bearer 權杖屬於機密,可存取你的分析資料;應盡量縮小其權限範圍,並避免出現在共用日誌中。此伺服器被描述為唯讀且無狀態,但在依賴這點前請向你的執行個體確認。分析資料來自你的 HitKeep 主機,助理會看到該執行個體所保存的內容。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 HitKeep,將其新增到工作區。
  2. 連接 Authorization token 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

[HitKeep]

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.

Self-host · Documentation · Cloud · Website

[Latest release] [Continuous integration status] [MIT license] [Docker pulls] [OpenSSF Best Practices badge]

[HitKeep dashboard showing traffic metrics, a 30-day comparison chart, and analytics navigation]

Why HitKeep

  • 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:

bash
brew install HitKeep/hitkeep/hitkeephitkeep --version

Follow the Homebrew installation guide to configure and start HitKeep. On Linux ARM64, use the published ARM64 binary or Docker instead.

For a production-oriented self-hosted setup, download the Docker Compose file and environment template:

bash
mkdir hitkeep && cd hitkeepcurl -fsSLo compose.yml https://raw.githubusercontent.com/HitKeep/hitkeep/main/examples/compose.ymlcurl -fsSLo .env https://raw.githubusercontent.com/HitKeep/hitkeep/main/examples/.env.example

Open .env and replace paste-the-generated-value-here with a long random value from your password manager. Then start HitKeep:

bash
docker compose up -d

Open http://localhost:8080 and create the first account. Keep .env private and retain the same secret across restarts.

Before exposing an instance publicly, follow the Docker Compose guide for HTTPS and trusted proxies, then review backups and the configuration reference. For a native Linux service, download an AMD64 or ARM64 binary from GitHub Releases and follow the binary installation guide.

Authentication

Native apps sign in through the system browser. Native Android passkeys are disabled until the operator configures the release app's signing certificate and verified domain association.

See the security reference, social sign-in setup, and native Android passkey setup.

Track Your First Site

Create a site in the dashboard, then add the tracker to your pages:

html
<script async src="https://analytics.example.com/hk.js"></script>

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

[HitKeep AI visibility report separating crawler fetches, AI referrals, and related activity]

Ecommerce

[HitKeep ecommerce analytics showing revenue KPIs, trends, top products, and revenue sources]

Search Console

[HitKeep Search Console report showing clicks, impressions, click-through rate, position, and query trends]

Ask AI

[HitKeep Ask AI answer with completed analytics tools, cited evidence, a table, and a safe dashboard action]

Assistants

[HitKeep Assistants setup showing the MCP endpoint, connection guides, and OAuth access controls]

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.

License

HitKeep is distributed under the MIT License.

DuckDB extensions

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.

Contributor instructions for DuckDB upgrades are in the extension bundle documentation.

來源:README.md,提交 33018b9

工具

0
該伺服器需要 API 金鑰等憑證,因此 SourceWeft 無法在沒有憑證的情況下讀取其工具,也未收錄。

版本歷史

1
  1. v2.17.0最新Nov 17, 2026

評分

已滿足適用檢查項的 60%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Keep 整合