AIMentionTracker

ai.aimentiontracker由 aimentiontracker.ai 发布官方发布者v0.1.3更新于 Oct 24, 2026

How often ChatGPT, Claude, Gemini and Perplexity name and cite your brand, with the evidence.

已验证Streamable HTTP可网页运行数据与分析商业与电商

概览

AI 生成的概览

AIMentionTracker 是一个只读 MCP 服务器，用于查看 ChatGPT、Claude、Gemini、Perplexity 等 AI 助手提及并引用你品牌的频率。

可以做什么
查询密钥身份、套餐与报告阈值，并获取当前 UTC 日期及各工具回溯的时间窗口。列出工作区跟踪的品牌和问题，以及每个问题产生的答案数量。按引擎和品牌读取 AI 可见度、声量份额与情感计数。查看被提及的竞争对手、含提及与引用的已存答案，以及引擎回答前阅读的域名。查看提醒与排序后的建议，以及在启用集成时读取 Search Console 数据。
适用场景
当你需要衡量或解释品牌在 AI 生成答案中的出现情况（答案引擎优化）并与竞争对手比较时，或需要查看这些数字背后真实答案与来源作为依据时使用。
运行要求
可使用托管远程端点并以 OAuth 持有者令牌认证，或通过 npx 运行本地 npm 包，后者需要 Node.js 和 AMT_API_KEY 环境变量。API 密钥在 AIMentionTracker 应用中创建，且仅限一个组织。
安装前请注意
API 密钥是机密，通过 Authorization 头或 AMT_API_KEY 传递，请妥善保管。访问为只读，无法更改账单、团队或跟踪内容，服务器本身不保存机密。答案过少时数值可能为空，各引擎分别报告而不取平均。

安装

在 SourceWeft 中

  1. 打开 控制台中的 AIMentionTracker，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/ai.aimentiontracker%2Fmcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "aimentiontracker": {
      "type": "http",
      "url": "https://mcp.aimentiontracker.ai/mcp"
    }
  }
}

README

@aimentiontracker/mcp

Track how often ChatGPT, Claude, Gemini, Perplexity and Google AI Overviews name and cite your brand, from inside your MCP client. Twelve read-only tools over AI visibility, share of voice, sentiment, competitor mentions and what to do about them, with the answers they came from.

This is answer engine optimisation (AEO) data, not rank tracking: the unit is an answer an assistant gave a real question, and whether you were in it.

Hosted (no install)

bash
claude mcp add --transport http aimentiontracker https://mcp.aimentiontracker.ai \  --header "Authorization: Bearer amt_live_YOUR_KEY"

Local (stdio)

bash
claude mcp add aimentiontracker -e AMT_API_KEY=amt_live_... -- npx -y @aimentiontracker/mcp

Create a key at app.aimentiontracker.ai/api-keys. Keys are read-only and scoped to one organisation; they cannot change billing, the team, or what is tracked.

Tools

All read-only. v1 has no write endpoints, deliberately: adding a prompt expands a metered bill and triggering a run spends real vendor money.

ToolWhat it answers
get_meWho this key is, the plan, and the reporting thresholds. Call first.
get_current_dateToday in UTC, and the trailing windows every other tool counts back from. Call before reasoning about dates.
list_brandsWhich brands this key can read, and their ids
list_questionsThe questions this workspace runs, and how many answers each produced. Call before reading a disappointing number: it may be the wrong question, not poor visibility
get_visibilityPresence per engine and per brand over a window
get_share_of_voiceEach tracked brand's mentions as a share of the tracked set
get_sentimentRecommended, negative and neutral counts per brand, against the classified denominator
list_competitorsWho gets named instead of you, including answers that named them and never mentioned you
list_answersThe stored answers, with mentions and citations
list_sourcesDomains the engines read before answering
list_alertsFindings worth acting on
list_recommendationsWhat to do next, ranked, with the pages and answers behind each item. Check displayable: false means the corpus is too thin to rank, not that there is nothing to do

One further tool, list_search_console, registers only where the Google Search Console integration is enabled. A tool that always answers 404 is worse than an absent one: an agent picks it for a task it cannot do and spends a turn failing.

Three rules the tools enforce

  1. A null rate means "not enough answers yet", never zero. Rendering it as 0% reports a collapse that did not happen.
  2. Engines are never averaged. They disagree; a mean describes no real surface.
  3. An empty findings list does not mean nothing changed. list_alerts says so in the payload, not just the description.

Every tool that reports a measurement carries these rules in its own description, because an agent reads the tool, not the README.

Why the denominators are in the payload

get_share_of_voice returns brands_counted, and get_sentiment counts against classified rather than total mentions. A workspace tracking two competitors and one tracking twelve produce incomparable shares from identical answers, and the sentiment classifier abstains on listicle mentions where an engine named a brand without endorsing it. Both numbers are meaningless without the denominator beside them, so the tools return it rather than trusting the caller to ask.

Security

The hosted server holds no secrets. No database, no vendor credentials, no service account. Your key arrives in the Authorization header and is passed straight through to the API, which does all authentication, tenancy, entitlement and rate limiting. Each request gets a fresh, stateless server instance that is closed when the response ends.

More

MIT.

来源：README.md，提交 5d14262

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

2
  1. v0.1.3最新Oct 9, 2026
  2. v0.1.2Oct 1, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分