Is this vendor down? Pay-per-call status for 1,700+ SaaS/cloud vendors from PulseWatch (x402 USDC).
Connect Remote server
claude mcp add --transport http status https://api.pulsewatch.us/mcp
{
"mcpServers": {
"status": {
"url": "https://api.pulsewatch.us/mcp"
}
}
}
{
"servers": {
"status": {
"type": "http",
"url": "https://api.pulsewatch.us/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.pulsewatch.us/mcp
Tools 5 found in our last check
list_vendorsFree. List or search the vendors PulseWatch tracks (slug, name, category), paged. Use it before paying to confirm a vendor is tracked and to get its exact slug. Read-only; one request to PulseWatch, no payment.
validate_vendorFree. Check that a vendor name, slug or domain is well-formed and see how it will be matched. Format only and offline (no network request, no payment); use list_vendors to confirm the vendor is actually tracked.
pricingFree. Return the price of every paid tool, the payment network (Base), the receiving address and the data source. No input, no network request, no payment.
vendor_statusCheck whether one SaaS or cloud vendor (e.g. Stripe) is down right now: current status, confidence, active incidents, 30-day uptime and how fresh the data is, read live from PulseWatch. Use it for one vendor; use multi_vendor_status for up to 25 vendors at a flat price. Call lis…
multi_vendor_statusCheck the status of up to 25 SaaS or cloud vendors in one call, for "is my stack down?" questions: per-vendor status and a list of the ones not operational, read live from PulseWatch. Use vendor_status when you need incident detail for a single vendor. Untracked names are report…
Details
| Endpoint | https://api.pulsewatch.us/mcp (Streamable HTTP) |
| First published | 13 Oct 2026 |
| Last updated | 13 Oct 2026 |
| Registry name | us.pulsewatch.api/status |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
