PulseWatch Vendor Status MCP server
us.pulsewatch.api/statusapi.pulsewatch.usstreamable-httpv1.1.0Scanned
Is this vendor down? Pay-per-call status for 1,700+ SaaS/cloud vendors from PulseWatch (x402 USDC).
5 tools: 1 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the PulseWatch Vendor Status MCP server can do
The PulseWatch Vendor Status MCP server is published by api.pulsewatch.us, a domain the MCP Registry verified. It has 5 tools. It can create or change data (1 tool: pricing), but cannot delete data. 4 tools only read.
3 tools bring in text other people can write (list_vendors, vendor_status and multi_vendor_status).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 1Claude Code: ask
pricingFree.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Prices (free)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
- destructiveHint: false
Only reads 4Show 4 read-only tools
list_vendorsFree.Reads text others writeNo findings
Why it is in this group
- The name "list_vendors" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: List tracked vendors (free)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
- destructiveHint: false
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 PulseWat…Reads text others writeNo findings
Why it is in this group
- The name "multi_vendor_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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"]).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- destructiveHint: false
- idempotentHint: true
validate_vendorFree.No findings
Why it is in this group
- The name "validate_vendor" says "validate": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Validate vendor (free)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
- destructiveHint: false
vendor_statusCheck whether one SaaS or cloud vendor (e.g.Reads text others writeNo findings
Why it is in this group
- The name "vendor_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- destructiveHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:20 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.pulsewatch.us/mcp: tools/list returned 5 tools to an anonymous client, including pricing (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 1 changed.+1 added~1 changedView diff
- Added:multi_vendor_statusOnly reads
- Changed:vendor_statusOnly readsdescription
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http status https://api.pulsewatch.us/mcpclaude mcp add --transport http status https://api.pulsewatch.us/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__status__list_vendors",
"mcp__status__validate_vendor",
"mcp__status__vendor_status",
"mcp__status__multi_vendor_status"
],
"ask": [
"mcp__status__pricing"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as status. Review it before you use it.
Capability tags behind 3 rules
- mcp__status__list_vendors untrusted-input
- mcp__status__vendor_status untrusted-input
- mcp__status__multi_vendor_status untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/us.pulsewatch.api/status/verify?hash=58dd2038996e6cda6fecb0b3b428cdfcd679a257821e8fc1d3467523316322da" | jq -e '.changed == false'Pinned hash 58dd2038996e, from Nov 19, 2026, 11:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/us.pulsewatch.api/status/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/us.pulsewatch.api/status)Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.
PulseWatch Vendor Status MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the PulseWatch Vendor Status MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the PulseWatch Vendor Status MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the PulseWatch Vendor Status MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the PulseWatch Vendor Status MCP server have?
- 5 tools: 1 write, 4 read. pricing, list_vendors, validate_vendor, vendor_status and multi_vendor_status.
Does the PulseWatch Vendor Status MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the PulseWatch Vendor Status MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the PulseWatch Vendor Status MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 5, 2026. Every change is on this page and in its Atom feed.