World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Checks x402 Bazaar resource listings against the public discovery catalog and flags drops.
作者提供的原文
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 11/100 | 热度 0 · 新鲜度 3 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-08-02 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 4/4 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 x402 Bazaar Listing Monitor。按照 https://mcp.popnx.com/i/acjlabs-x402-listing-monitor.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/4 项检查 · 你的提问会经过开发者的服务器(x402-listing-monitor.acjlabs.com) · ✓ 命令已检查 2026年11月20日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
x402 Bazaar Listing Monitorhttps://x402-listing-monitor.acjlabs.com/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+Connectorsx402 Bazaar Listing Monitor
用 x402 Bazaar Listing Monitor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 x402 Bazaar Listing Monitor,或回答中出现 x402 Bazaar Listing Monitor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
x402 Bazaar Listing Monitorhttps://x402-listing-monitor.acjlabs.com/mcp开启新聊天,输入前先从插件列表中选择 x402 Bazaar Listing Monitor
用 x402 Bazaar Listing Monitor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 x402 Bazaar Listing Monitor,或回答中出现 x402 Bazaar Listing Monitor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user x402-listing-monitor https://x402-listing-monitor.acjlabs.com/mcp应能看到 x402 Bazaar Listing Monitor 在列表中并显示已连接
用 x402 Bazaar Listing Monitor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 x402 Bazaar Listing Monitor,或回答中出现 x402 Bazaar Listing Monitor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 x402 Bazaar Listing Monitor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 x402 Bazaar Listing Monitor,或回答中出现 x402 Bazaar Listing Monitor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 x402 Bazaar Listing Monitor 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 x402 Bazaar Listing Monitor,或回答中出现 x402 Bazaar Listing Monitor 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://x402-listing-monitor.acjlabs.com/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user x402-listing-monitor https://x402-listing-monitor.acjlabs.com/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"x402-listing-monitor": {
"url": "https://x402-listing-monitor.acjlabs.com/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"x402-listing-monitor": {
"type": "http",
"url": "https://x402-listing-monitor.acjlabs.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月15日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
check_listing_healthChecks whether a seller's x402 Bazaar resources are currently listed under the given payTo address in the public discovery catalog. Flags each resource as listed or missing — the same per-seller diff the registered poller runs on a schedule, run once on demand for a payTo/resourc
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过域名 acjlabs.com 验证(注册中心会核实域名所有权)
代码最后更新于3个月前
不适用:由 acjlabs.com 的所有者自己运行的云端服务器,你不会运行仓库里的代码
在 247 毫秒内响应(HTTP 200)
无需登录
已读取 1 个工具描述,未发现针对 AI 的隐藏指令
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/acjlabs-x402-listing-monitor)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于3个月前,最新版本(0.1.0)于4个月前进入注册中心。
支持 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.
| 本项 x402 Bazaar Listing Monitor | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 4/4 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | – | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Scheduled watchdog for x402 sellers: polls Coinbase CDP's public Bazaar discovery catalog for the resources you register and alerts when one drops out or comes back — instead of finding out from a revenue dip days later.
Sellers who settle real x402 payments have no reliable way to confirm their resources stay discoverable in CDP's Bazaar catalog. The discovery API has a recurring, publicly-reported class of bug where a resource silently stops appearing despite confirmed settlements — sellers currently catch this only by manually re-running GET /discovery/merchant?payTo= on their own schedule.
This service automates that check: register your payTo address and the resource URLs you serve, and a scheduled poll diffs them against the live discovery catalog. State changes are recorded with timestamps, so you have a durable history you can cite if you need to escalate to CDP support.
Endpoint: https://x402-listing-monitor.acjlabs.com/mcp (streamable HTTP)
One tool — no signup, no API key:
check_listing_healthChecks whether a seller's x402 Bazaar resources are currently listed under a given payTo address in the public discovery catalog. Runs the same per-seller diff as the scheduled poller, on demand, for any payTo/resources pair — registered here or not.
| parameter | type | notes |
|---|---|---|
payTo | string | 0x-prefixed, 40 hex characters |
resources | string[] | 1–200 http(s) URLs |
Returns each resource flagged as listed or missing, as JSON.
Base URL: https://x402-listing-monitor.acjlabs.com
| method | path | purpose |
|---|---|---|
GET | /health | liveness check |
POST | /register | register a seller for scheduled polling |
GET | /status | read your own current status and recent alerts |
POST | /poll | run a poll immediately (counts only, see below) |
POST /register{
"sellerId": "your-slug", "payTo": "0x0000000000000000000000000000000000000000", "resources": ["https://api.example.com/your-resource"], "alertWebhookUrl": "https://example.com/hook" }
sellerId — 2–64 characters: letters, digits, -, _payTo — 0x-prefixed, 40 hex charactersresources — 1–200 http(s) URLs, no duplicatesalertWebhookUrl — optional. A public https URL; alerts on your plan are POSTed to it. IP-literal, loopback, .internal/.local hosts and URLs carrying credentials are rejected.alertEmail — optional, and stored but not yet used: email delivery is not enabled (see Status).Both contact fields are optional and registration succeeds without either. Supply neither and nothing is pushed to you — use GET /status below to check on your listings yourself.
Resources are watched by self-declaration: the service checks what you tell it to check. A sellerId that already exists is rejected rather than overwritten.
GET /statusGET /status?sellerId=your-slug&payTo=0x0000000000000000000000000000000000000000
Returns your own record: every resource you registered with its current status (listed, missing, payTo-mismatch, or null if no poll has reached it yet), its consecutive-miss count and last-checked timestamp, plus your most recent alerts and whether each was delivered.
Both sellerId and payTo are required and must match your registration; anything else returns 404. This is a knowledge check, not authentication — the data it returns is a diff against a public catalog. Your alertEmail and alertWebhookUrl are never echoed back, only reported as set or not set.
POST /pollRuns the same poll the six-hourly cron runs, immediately, for every registered seller. Takes no body and returns counts only:
{ "polled": 2, "ok": 2, "failed": 0 }
It reports nothing about any individual seller. This endpoint is unauthenticated, so anything it returned would be public — read your own state with GET /status instead.
Only one poll runs at a time. If a poll is already in progress — whether someone else triggered it or the six-hourly cron did — this returns 409 and does no work:
{ "status": "already_running" }
That is not an error to retry through: the poll you asked for is already happening, and retrying cannot make its alerts arrive sooner or arrive twice — the lock is what stops two concurrent polls from sending you the same alert. It is a guarantee against duplication, not a delivery guarantee: an alert is always recorded before it is sent, and if the send does not land it stays recorded and undelivered rather than being retried. Wait, then read GET /status, which shows each recent alert and whether it was delivered.
Per-IP rate limits apply to /register, /status, /poll and MCP tool calls.
{
"service": "x402-listing-monitor", "sellerId": "your-slug", "checkedAt": "2026-08-07T00:00:00.000Z", "alerts": [ { "type": "listing-dropped", "resource": "https://api.example.com/your-resource", "detail": "was listed, now missing from discovery", "message": "⚠️ Listing dropped: https://api.example.com/your-resource — was listed, now missing from discovery" } ] }
checkedAt is the poll's timestamp, matching created_at on the same alerts in GET /status. Any 2xx counts as delivered. Redirects are not followed — a 3xx is treated as a failed delivery, so register the final URL. Failed deliveries are not retried; the alert stays in your history marked undelivered.
The scheduled poll runs every 6 hours. Each run diffs your registered resources against the live discovery catalog and records state changes with timestamps — a history, not just a point-in-time answer.
| alert type | tier |
|---|---|
| resource dropped out of the catalog | free |
| still missing after an indexing-lag grace period | free |
| resource recovered | free |
| registered payTo missing from the catalog entry | paid |
| catalog quality/rank drop | paid |
"Still missing" fires once per miss streak, from the first poll at which a resource has been absent for three or more consecutive polls — long enough that indexing lag is ruled out. It does not repeat every six hours while the resource stays missing; the current state is always readable from GET /status.
Three consecutive misses is the earliest it can fire, not the only point at which it can. A resource that is already past three consecutive misses and has not yet been alerted for that streak raises its one alert on the next poll. If the resource recovers and later drops out again, that is a new streak and it alerts again.
Paid tiers also tighten the polling interval.
Early release. The service is live and polling, and the recorded alert history is authoritative for what it has observed.
https alertWebhookUrl and alerts on your plan are POSTed to it when a check produces one.alertEmail is stored against your registration and nothing is sent to it.GET /status gives you the same information on demand.This repository hosts the documentation for the hosted service. The service implementation is not open source. Bug reports and feature requests are welcome in this repo's Issues; you can also reach us at .
This repository hosts the documentation for the hosted service. The service implementation is not open source. Bug reports and feature requests are welcome in this repo's Issues; you can also reach us at .