PulseWatch Vendor Status MCP Server
us.pulsewatch.api/statusv1.1.0
Is this vendor down? Pay-per-call status for 1,700+ SaaS/cloud vendors from PulseWatch (x402 USDC).
context tax
~596 tok/turn4 tools
security
100/100
cold start
hosted
freshness
Active6d ago
Our reading of PulseWatch Vendor Status, from the data
PulseWatch Vendor Status is an MCP server, listed in the official MCP Registry.
Its 4 tools add about 596 tokens to every model turn (measured 2026-10-19).
Maintenance is active: the last public signal was 6 days ago (2026-10-13).
It runs as a hosted endpoint, so there is nothing to install.
Install PulseWatch Vendor Status MCP server
Install in Claude Code
claude mcp add --transport http us-pulsewatch-api-status https://api.pulsewatch.us/mcpInstall in Cursor
{
"mcpServers": {
"us-pulsewatch-api-status": {
"url": "https://api.pulsewatch.us/mcp"
}
}
}Install in Claude Desktop
{
"mcpServers": {
"us-pulsewatch-api-status": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.pulsewatch.us/mcp"
]
}
}
}Or add it as a custom connector under Settings → Connectors. The config above bridges via mcp-remote.
Install in VS Code
{
"servers": {
"us-pulsewatch-api-status": {
"type": "http",
"url": "https://api.pulsewatch.us/mcp"
}
}
}Install in Windsurf
{
"mcpServers": {
"us-pulsewatch-api-status": {
"serverUrl": "https://api.pulsewatch.us/mcp"
}
}
}Remote endpoints
- streamable-http
https://api.pulsewatch.us/mcp
Context tax
Connecting this server adds ~596 tokens of tool definitions to every model turn (lean, 4 tools). Measured 2026-10-19 via its hosted endpoint; o200k tokenizer, worst case for clients that load all tools up front. How we measure
| Model | Per 1,000 turns | With prompt caching |
|---|---|---|
| Claude Opus 5.5 | $2.38 | $0.119 |
| Claude Sonnet 5.5 | $1.19 | $0.119 |
| Claude Haiku 5.5 | $0.060 | — |
Input prices as of 2026-10-06. Excludes your own prompt and output.
Tools (4)
vendor_status193 tokCheck 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. 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.
list_vendors145 tokFree. 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_vendor119 tokFree. 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.
pricing69 tokFree. 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.
Security signals
100/100 — no known issues found as of 2026-10-19, from the checks below. This is not a guarantee of safety; review what a server can do before connecting it.
Deductions
No findings from the checks that ran.
Checks
- ✓Tool descriptions (prompt-injection and hidden-text heuristics)
- ○Repository hygiene (archived, activity, license, security policy) — pending
- ○Package metadata (install scripts, provenance) — pending
- ○Source scan (secrets, CVEs, risky code) by vectra-guard — pending
Scan it yourself before installing with vectra-guard, the open-source agent security CLI. Scoring rules
Freshness
Active — last maintenance signal 6d ago. The newest of the signals below sets the band.
Last commit (default branch)
no data · GitHub
Latest release
no data · GitHub
Package published
no data · npm/PyPI
Registry entry updated
2026-10-13 · 6d ago · official registry · v1.1.0
FAQ
›How do I install the PulseWatch Vendor Status MCP server in Claude Code?
Run: claude mcp add --transport http us-pulsewatch-api-status https://api.pulsewatch.us/mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.
›Does PulseWatch Vendor Status require an API key?
No required environment variables are declared in its published metadata.
›Can I use PulseWatch Vendor Status as a remote (hosted) MCP server?
Yes. It is a hosted MCP server; connect to its URL with any client that supports remote MCP.
›Is PulseWatch Vendor Status in the official MCP registry?
Yes, as us.pulsewatch.api/status.
›How many tokens does PulseWatch Vendor Status add to my context?
Its tool definitions total about 596 tokens, resent on every turn.
Sources and method
- Official MCP Registry entry
- updated 2026-10-13
- Tool list (tools/list), measured by us
- 2026-10-19
- Security signals, computed by us
- 2026-10-19
- Last checked against all sources
- 2026-10-19
The description, packages and links come from the maintainer's own published metadata. Token cost, security signals, freshness and the reading above are MCPSkillHub's own measurements; see the methodology. Editorial standards are owned by Ramachandra Vikas Chamarthi, Founder & AI HPC Architect. Spot an error? Request a correction or claim the listing.