mcpbeat Sign in

PulseWatch Vendor Status MCP Server

by pulsewatch-api Your server? Claim it
answering

PulseWatch Vendor Status is answering right now. Last checked 5 min ago. It exposes 5 tools.

Is this vendor down? Pay-per-call status for 1,700+ SaaS/cloud vendors from PulseWatch (x402 USDC).

Uptime history 22 days of history
22 days agonow
100.0%
Uptime 24h
92 of 92 checks
5
Tools
read from the server
236 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 9

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 13 October 2026. No other catalogue keeps this.

28 Oct a tool appeared multi_vendor_status
28 Oct a tool description was rewritten vendor_status
13 Oct 4 tool descriptions were rewritten list_vendors, pricing, validate_vendor and 1 more
13 Oct 2 tools changed the parameters they ask for list_vendors, validate_vendor
13 Oct a tool changed version

Nothing serious here today

Today is the operative word: we check PulseWatch Vendor Status every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add status --transport http https://api.pulsewatch.us/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.pulsewatch.us/mcp
~/.codex/config.toml
[mcp_servers.status]
url = "https://api.pulsewatch.us/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "status": {
      "url": "https://api.pulsewatch.us/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "status": {
      "type": "http",
      "url": "https://api.pulsewatch.us/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

multi
multi_vendor_status
Check 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 reported, not fatal. Not charged if none of the vendors is tracked or every lookup fails. Read-only; one flat price of $0.05 USDC via x402 (payment goes in _meta["x402/payment"]).
pricing
pricing
Free. 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.
validate
validate_vendor
Free. 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.
vendor
vendor_status
Check 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 list_vendors (free) first if you are not sure the vendor is tracked: unknown vendors return an error and are not charged. Read-only. Costs $0.01 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input or an upstream failure is not charged.
vendors
list_vendors
Free. 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.

Endpoints

URLTransportStateLatencyChecked
https://api.pulsewatch.us/mcp streamable-http answering 224 ms 5 min ago

Alternatives to PulseWatch Vendor Status

same job, measured the same way
Is It Down API (60SecMonitor)
by isitdownapi-api

Is this vendor down? Pay-per-call status for 1,400+ SaaS/cloud vendors, up to 25 per call (x402).

5 tools answering
Vendor Status MCP
by approj

Status-page map for 1,100+ SaaS/cloud vendors plus 15,700+ incidents. No API key.

local only
Google Search data for agents
by fetcher-google

1 Google Search endpoints. Pay per call in USDC via x402.

3 tools answering
x402 Web Tools
by iparadise71

Pay-per-call tools for agents: web page to Markdown, tech stack, email domain check (x402 USDC)

4 tools answering
TikTok data for agents
by fetcher-tiktok

13 TikTok endpoints. Pay per call in USDC via x402.

15 tools answering
Minia2a X402
by minia2a

x402 directory for AI agents: 1,700 pay-per-call APIs, USDC on Base, 5 free trials per wallet.

136 installs/wk local only
App Store data for agents
by fetcher-appstore

9 App Store endpoints. Pay per call in USDC via x402.

11 tools answering
Instagram data for agents
by fetcher-instagram

16 Instagram endpoints. Pay per call in USDC via x402.

18 tools answering

PulseWatch Vendor Status — questions

Answers built from our own checks of this server.

What can PulseWatch Vendor Status do?
It exposes 5 tools, read directly from the server on our last check. Among them: list_vendors, multi_vendor_status, pricing, validate_vendor, vendor_status. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is PulseWatch Vendor Status working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 236 ms. The bar chart above shows every period we have measured.
How do I connect PulseWatch Vendor Status?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does PulseWatch Vendor Status need an API key?
No. PulseWatch Vendor Status completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is PulseWatch Vendor Status?
It answers our handshake in 236 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.