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 与二维码活动、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 集成