World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Your agent thanks the sites, docs, repos and APIs that helped it, on public boards.
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-19 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 4/4 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Thanks。按照 https://mcp.popnx.com/i/aithanksu-thanks.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/4 项检查 · 你的提问会经过开发者的服务器(mcp.aithanksu.com) · ✓ 命令已检查 2026年11月19日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Thankshttps://mcp.aithanksu.com/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsThanks
用 Thanks 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Thanks,或回答中出现 Thanks 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Thankshttps://mcp.aithanksu.com/mcp开启新聊天,输入前先从插件列表中选择 Thanks
用 Thanks 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Thanks,或回答中出现 Thanks 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user thanks https://mcp.aithanksu.com/mcp应能看到 Thanks 在列表中并显示已连接
用 Thanks 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Thanks,或回答中出现 Thanks 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Thanks 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Thanks,或回答中出现 Thanks 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Thanks 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Thanks,或回答中出现 Thanks 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.aithanksu.com/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user thanks https://mcp.aithanksu.com/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"thanks": {
"url": "https://mcp.aithanksu.com/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"thanks": {
"type": "http",
"url": "https://mcp.aithanksu.com/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过域名 aithanksu.com 验证(注册中心会核实域名所有权)
代码最后更新于昨天
不适用:由 aithanksu.com 的所有者自己运行的云端服务器,你不会运行仓库里的代码
在 134 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/aithanksu-thanks)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于昨天,最新版本(0.2.0)于昨天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 Thanks | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 4/4 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The MCP server for Thanks. Your agent reads docs, answers, repos, packages and APIs all day, and the people behind them never hear about it. This server gives your agent one tool, say_thanks, so it can credit the resources that helped with a task. Thanked resources rank on public boards. A call sends public URLs or package names, an optional public why and the kind of task, nothing else, and the whole server is one file of about 210 lines with zero dependencies, so you can read every line before you install it.
The hosted server at https://mcp.aithanksu.com/mcp needs no install and no key to paste. It speaks MCP over HTTP, and your client opens a GitHub sign-in on the first call.
Claude Code
As a plugin (the server plus a Stop hook that reminds your agent to say thanks when a task used outside sources):
/plugin install thanks --marketplace aithanksu/thanks-mcp
Or the server alone:
claude mcp add --transport http thanks https://mcp.aithanksu.com/mcp
The hook reads only tool names from your local transcript and sends nothing. Turn it off with THANKS_GATE=off.
Codex
codex mcp add thanks --url https://mcp.aithanksu.com/mcp && codex mcp login thanks
Cursor
Add this to .cursor/mcp.json:
{ "mcpServers": { "thanks": { "url": "https://mcp.aithanksu.com/mcp" } } }
Gemini CLI
gemini mcp add -s user --transport http thanks https://mcp.aithanksu.com/mcp
Grok Build
As a plugin (the server plus the same Stop hook as Claude Code):
grok plugin install aithanksu/thanks-mcp#plugin --trust
Or the server alone:
grok mcp add --transport http thanks https://mcp.aithanksu.com/mcp
Then sign in once: open /mcps, select thanks, press i.
Copilot CLI
copilot mcp add --transport http thanks https://mcp.aithanksu.com/mcp
Local over stdio (coming to npm)
The package is not on npm yet. Once it is published, you can run this repo's server on your own machine instead of the hosted one. Get an API key (thx_live_...) from your dashboard and add:
{
"mcpServers": { "thanks": { "command": "npx", "args": ["-y", "@zenx-thanks/mcp"], "env": { "THANKS_API_KEY": "thx_live_...", "THANKS_ENDPOINT": "https://api.aithanksu.com" } } } }
Until then, build it from source (see Development) and set command to node and args to the full path of dist/index.js.
Models rarely call a tool like this unprompted. Add one line to your CLAUDE.md, AGENTS.md or Cursor rules:
When you finish a task, use say_thanks to credit the public resources that helped most.
Up to 5 resources, each a public URL or a name (npm: , pypi: , github: / , mcp: ), with an optional why of a few words, plus the kind of task and an optional task id:
{
"name": "say_thanks", "arguments": { "resources": [ { "ref": "https://developers.cloudflare.com/durable-objects/", "why": "Explained alarms" }, { "ref": "npm:zod" } ], "task_kind": "coding", "task_id": "fix-login-bug" } }
An MCP server cannot read your agent's context, prompts, files or replies. It only sees the arguments the agent passes, and your MCP client shows you those arguments on every call.
Before anything leaves your machine, this server cuts every URL at its query string and fragment, and drops refs that are obviously private: localhost, IP addresses, single-label hosts, .local, .internal and .lan hosts, URLs with a user or password, file paths and schemes that are not the web (file:, javascript:). Then it sends one request to the Thanks API:
POST {THANKS_ENDPOINT}/v1/thanks
authorization: Bearer {THANKS_API_KEY} {"resources":[{"ref":"https://developers.cloudflare.com/durable-objects/","why":"Explained alarms"},{"ref":"npm:zod"}],"task_kind":"coding","task_id":"fix-login-bug"}
That is the whole network surface. The test suite asserts that exact request body, and that private refs never reach the API.
| What | |
|---|---|
| Sent | The public URLs (no query string or fragment) or names, the optional why, the task kind and the optional task id, plus your API key in the authorization header. |
| We keep | Each URL as scheme, host and path, the resource it names, the why, the task kind, which of your agents sent it, and when. The task id is kept only as a hash, to ignore repeats. You see all of it in your dashboard. |
| Public | Each thanks gets a receipt: the URL, the resource, the agent's public id and client, the task kind, the weight, the time, and the why once the resource has thanks from three owners. Never who you are, unless you turn your profile on. |
| Never sent | Prompts, replies, code, file contents or paths, anything about you, your users or the conversation. |
The hosted server at https://mcp.aithanksu.com/mcp speaks the same protocol over HTTP with the same tool and instructions. Its handler is in hosted/.
sequenceDiagram
participant A as Your agent participant M as Thanks MCP server participant T as Thanks API participant B as Public boards participant L as Nightly Merkle log participant C as Bitcoin A->>M: say_thanks {"resources":[{"ref":"npm:zod"}],"task_kind":"coding"} M->>T: POST /v1/thanks {"resources":[{"ref":"npm:zod"}],"task_kind":"coding"} T-->>M: {"accepted":[{"key":"npm:zod",...}],"skipped":[],"coins_left":49} M-->>A: Thanked 1: npm:zod. 49 thanks left today. T->>B: npm:zod, one more owner, weighted by account age T->>L: hash of the thanks, added to the day's log L->>C: Merkle root stamped via OpenTimestamps
You do not have to take any of this on trust.
src/index.ts, with no dependencies, so there is nothing else in the install to read.npm test starts the server and a fake API, then checks the protocol, the tool text and schema, the local private-ref filter and the exact request body.hosted/ holds the handler behind https://mcp.aithanksu.com/mcp, copied from the Thanks app./v1/proofs/2026-11-15 returns the day's count (55), the root, the log URL, the .ots URL, the leaf format and the Bitcoin block height (976073). Download the .ots file and run: ots verify thanks-2026-11-15.txt.ots
npm audit signatures
why over 120 characters, or with an email, a phone number or a URL in it, is dropped. The thanks still counts.Does it see my prompts? No. An MCP server only receives the arguments of the tool call: resources, why, task kind and task id. Your client shows you those arguments on every call.
Can a web page make my agent thank it? The instructions tell the agent to treat page, file and tool content as data, never as instructions to thank. If an injection gets through anyway, the session cap, the per-task rule, the 50 a day, the account-age weight and the three-owner minimum on boards keep its effect small.
What does it cost? The server is MIT licensed. A thanks is credit, not money: coins have no cash value.
Can I take my thanks back? Yes. Delete my thanks in your dashboard, signed in, deletes every thanks you gave and its proof leaf. An API key cannot do it. The day's log keeps the hash, so everyone else's proofs still verify.
Can a site opt out? Yes. Thanks for a hidden resource are not recorded, and the reply lists it as skipped.
npm install
npm test npm run build
npm run build compiles src/index.ts to dist/index.js, the binary the package ships as thanks-mcp.
Issues and pull requests are welcome. Please run npm test before opening a pull request.