# PulseWatch Vendor Status (remote · api.pulsewatch.us)

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

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.pulsewatch.us`: 78/100 (this document), [markdown](https://verifymcp.io/servers/us-pulsewatch-api-status/api.md), [page](https://verifymcp.io/servers/us-pulsewatch-api-status/api)

## Channel facts

- Endpoint: `https://api.pulsewatch.us/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 599 tokens (~119/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the PulseWatch Vendor Status MCP server?

PulseWatch Vendor Status is a hosted endpoint at https://api.pulsewatch.us/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http us-pulsewatch-api-status 'https://api.pulsewatch.us/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "us-pulsewatch-api-status": {
      "url": "https://api.pulsewatch.us/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "us-pulsewatch-api-status": {
      "type": "http",
      "url": "https://api.pulsewatch.us/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.us-pulsewatch-api-status]
url = "https://api.pulsewatch.us/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "us-pulsewatch-api-status": {
      "type": "remote",
      "url": "https://api.pulsewatch.us/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add us-pulsewatch-api-status --url 'https://api.pulsewatch.us/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  us-pulsewatch-api-status:
    url: "https://api.pulsewatch.us/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "us-pulsewatch-api-status": {
      "Transport": "http",
      "Url": "https://api.pulsewatch.us/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add us-pulsewatch-api-status -t streamable-http -u 'https://api.pulsewatch.us/mcp'
```

### Other

```json
{
  "mcpServers": {
    "us-pulsewatch-api-status": {
      "type": "http",
      "url": "https://api.pulsewatch.us/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 75, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “vendor_status” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 439 → 599
- [functional] Schema quality: good → excellent
- [functional] New tool “multi_vendor_status”

### 2026-10-27 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `list_vendors` (~98 tokens)

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.

Input parameters:

- `page` (integer): Page number, starting at 1 (default 1)
- `search` (string): Optional name or slug filter, e.g. 'stripe' or 'aws'

### `validate_vendor` (~81 tokens)

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.

Input parameters:

- `vendor` (string, required): Vendor name, slug or domain, e.g. 'Stripe', 'stripe' or stripe.com

### `pricing` (~41 tokens)

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.

### `vendor_status` (~163 tokens)

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.

Input parameters:

- `vendor` (string, required): Vendor name, slug or domain, e.g. 'Stripe', 'stripe' or stripe.com

### `multi_vendor_status` (~136 tokens)

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"]).

Input parameters:

- `vendors` (array, required): 1-25 vendor names, slugs or domains

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/us-pulsewatch-api-status/api#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 74
- 2026-10-27: 74
- 2026-10-26: 73
- 2026-10-25: 73
- 2026-10-24: 72
- 2026-10-23: 72
- 2026-10-22: 72
- 2026-10-21: 71
- 2026-10-20: 71
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 69
- 2026-10-16: 69
- 2026-10-15: 68
- 2026-10-14: 68
- 2026-10-13: 67
- 2026-10-12: 57

## Common questions

### What is the PulseWatch Vendor Status MCP server?

PulseWatch Vendor Status is an MCP server listed in the public MCP registry as us.pulsewatch.api/status. Is this vendor down? Pay-per-call status for 1,700+ SaaS/cloud vendors from PulseWatch (x402 USDC). This page covers its hosted endpoint (https://api.pulsewatch.us/mcp).

### Is the PulseWatch Vendor Status MCP server safe to use?

PulseWatch Vendor Status scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the PulseWatch Vendor Status MCP server expose?

PulseWatch Vendor Status exposes 5 tools: list_vendors, validate_vendor, pricing, vendor_status, multi_vendor_status. Their descriptions and schemas cost roughly 519 tokens of context every time the server is loaded.

### Does the PulseWatch Vendor Status MCP server require authentication?

No. We connected to PulseWatch Vendor Status without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the PulseWatch Vendor Status MCP server still maintained?

PulseWatch Vendor Status is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.pulsewatch.us/mcp
- Website: https://api.pulsewatch.us/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/us-pulsewatch-api-status/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/us-pulsewatch-api-status/api.json
- HTML version of this page: https://verifymcp.io/servers/us-pulsewatch-api-status/api