Adding a site

Adding a site is the whole of setup. There is no configuration to work through first.

1. Sign in and open your dashboard.
2. Enter your domain.

Both standards are checked immediately rather than at the next scheduled run, so adding a site produces an answer within a minute instead of an empty row until tomorrow.

What happens from then on

Every site is rechecked daily at 06:00. Each run is compared against what we already knew:

• A check that starts failing opens an issue
• A check that stops failing closes it
• A run that merely confirms yesterday does nothing at all

You are emailed only when that list of open issues changes. A site failing the same check every morning for a fortnight sends one message, not fourteen.

That is the whole setup

There is nothing else to install. Checks run against your site from outside, so nothing goes on your servers and nothing changes in your code.

If your site offers WebMCP tools, there is one optional script that reports which of them agents actually call. Skip it otherwise — it would have nothing to report.

How many sites you can add

Depends on your plan, and the cap is hard — see plans and limits. The free tier covers one site, which is deliberately enough to monitor a real site properly rather than to evaluate us on a toy.

Staging and production count separately. Monitoring staging is genuinely useful, since it catches a regression before it ships, but it is a second site.

Removing one

Removing a site stops the checks and hides it from your dashboard. Its recorded events are removed on the next nightly prune. Nothing is billed after removal.