You’ll set up monitoring
later. You won’t.

Set up uptime monitoring for this project with Exit1.

1. Check whether the Exit1 tools (get_account, list_checks, create_check) are
   available to you. If they are, go to step 2.

   If they are not and I have no Exit1 account, create one for me. Ask for
   my email (never invent one), then POST
     {"email": "<my email>", "agent_name": "<your name>"}
   to https://app.exit1.dev/oauth/agent-signup. Use the access_token it
   returns as a Bearer token on the api_base it returns (POST requests need
   an Idempotency-Key header) and carry on with the REST endpoints. If you
   have exit1-mcp's create_account tool, use that instead. Docs:
   https://docs.exit1.dev/integrations/agent-signup

   If I already have an account (the signup returns 409 account_exists), do
   NOT try to connect from inside this session, and do not improvise with the
   raw API. Most AI tools load MCP servers only at startup and cannot open a
   browser sign-in mid-conversation, so a server added now stays unusable
   until I restart. Instead:
     - In Claude Code: run
         claude mcp add --transport http exit1 https://app.exit1.dev/mcp/v1
       then tell me to quit, run `claude mcp login exit1` in my terminal (my
       browser opens to sign in or sign up), and resume you with
       `claude --continue`. If my version has no `mcp login`, I
       authenticate via /mcp after restarting instead.
     - In other tools: tell me to add the HTTP MCP server
       https://app.exit1.dev/mcp/v1 the way my tool does it, restart it, and
       paste this prompt again.
   While you wait, do step 3 now and show me the checks you intend to create,
   so my first message after reconnecting can be "go".

2. Call get_account to see my plan limits, and list_checks to see what's
   already monitored (over REST: GET /account and GET /checks).

3. Work out what's worth monitoring by reading this project. Don't ask me for
   URLs you can find yourself. Depending on the stack, look at deploy and
   infra config, environment files and examples, the README, DNS or domain
   config, container healthchecks, CI/CD workflows, and route or endpoint
   definitions. You're looking for:
     - the production site or app, and staging if there is one
     - health/status endpoints (these are the most valuable; assert on the
       response body, not just a 200, since a 200 with a dead database is
       still a 200)
     - public APIs and webhook receivers other systems depend on
     - scheduled jobs and workers (monitor these as heartbeats)
     - the apex domain, for SSL and registration expiry
   If this project has no deployed URL you can find, ask me for it.

4. Ask me two things in one go: which email address should receive alerts,
   and whether to add a Slack/Discord webhook. Then show me the checks you
   intend to create as one short list and create them when I confirm.

5. Send a test alert to every channel you set up and tell me to check it
   arrived. Don't leave a channel configured but untested. On an account you
   just created, alerts wait until I claim it: tell me to open the claim
   email from Exit1, then send the test alerts.

Be fast and autonomous. Never put API keys, tokens or passwords into a check.
Prefer a few meaningful checks over many shallow ones.