Scheduled watchdog for x402 sellers: polls Coinbase CDP's public Bazaar discovery catalog for your
registered resources and payTo address, flagging a drop or a recovery — instead of finding out from a
revenue dip days later.
**How it works:** register a payTo address and resource URLs once; a scheduled poll diffs them against
the live discovery catalog and alerts on a state change. The `check_listing_health` MCP tool runs the
same scoped diff on demand, whether or not a payTo/resources pair has been registered.
**Free tier:** 6-hour polling, drop/recovery detection with a durable alert history — no card required.
Paid tiers tighten the polling interval and add escalation/rank-drop alert types.
Docs & changelog: https://github.com/acjlabs/x402-listing-monitor
How do I install x402 Bazaar Listing Monitor in Claude Code?
Run: claude mcp add --transport http x402-bazaar-listing-monitor https://x402-listing-monitor--acjlabs.run.tools
Can I add x402 Bazaar Listing Monitor as a connector in ChatGPT or Claude.ai?
Yes — it’s a remote MCP server, so no local install is needed. ChatGPT: Settings → Connectors → Advanced → Developer mode → Add connector, then paste https://x402-listing-monitor--acjlabs.run.tools. Claude.ai: Settings → Connectors → Add custom connector, then paste the same URL.
Which registries list x402 Bazaar Listing Monitor?
Secureship MCP gives AI assistants access to a multi-carrier shipping API covering rate comparison, label generation, package tracking, pickup scheduling, address book management, shipment history, customs documents, and more — across carriers like UPS, FedEx, Purolator, Canpar, and others. Browse 150+ live endpoint schemas, parameters, and auth details — always current, never stale.
Secureship isn't just for shipping with one carrier — it's a multi-carrier shipping platform, and this MCP server gives AI assistants full access to the API documentation for every supported action: compare rates across carriers, generate shipping labels, track packages, schedule pickups, manage address books, review shipment history, produce customs documents, handle invoices, and even perform actions available on the Secureship web dashboard — all through a single API.
The MCP documentation server exposes live endpoint metadata pulled directly from the running application — not static docs that go stale. That means AI assistants always get the correct paths, parameters, request bodies, response schemas, and authentication requirements for 150+ endpoints.
Read-only, public, no API key needed to browse. Authentication for the actual shipping API uses a simple X-API-KEY header.
**Tools exposed:**
- SearchDocs — keyword search across all API endpoints
- GetEndpointDetail — full schema for a specific endpoint (params, request body, responses, auth)
- ListEndpoints — list all endpoints, optionally filtered by category
- GetAuthInfo — authentication instructions (X-API-KEY header)
**Categories:** Shipping, logistics, e-commerce, carriers, rates, labels, tracking, address book, customs documents, shipment history
