PulseWatch
Actively maintained
≈ 118visits/mo
Use not read yet · estimate, read Oct 15, 2026
- For
- Teams and solo users who need to watch third-party services for outages and service health
- Activity
- Actively maintainedrelease 2 weeks ago · site updated 5 days ago
- Runs as
- API
- App Store
- 00 ratingsiPhone & iPad · updated Oct 3, 2026
- Used for
- Track outages across third-party services the business depends on
- Monitor SaaS dependencies and get alerted when they fail
- Compare current service incidents against past incident history
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantspulsewatch.us ↗
Price not read
These are PulseWatch's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
- MCP serverus.pulsewatch.api/statusverified in the MCP registry
- Stateanswers, 4 toolschecked 2026-10-18
- Address to connectapi.pulsewatch.us/mcp
- API docspulsewatch.us/api-docsthe vendor's page ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use PulseWatch for?
Sign in to leave a noteWhat is PulseWatch?
Tracks third-party service status and outages in real time, sending alerts when vendors you depend on go down.
Who is PulseWatch for?
Teams and solo users who need to watch third-party services for outages and service health
Is PulseWatch still maintained?
Actively maintained: release 2 weeks ago · site updated 5 days ago.
Does PulseWatch have an iPhone app?
Yes: “PulseWatch - Web Monitor” on the App Store, rated 0 from 0 ratings; current version released 2026-10-03.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk