Preventionlabs

au.com.preventionlabsPublished by preventionlabs.com.auOfficial publisherv1.2.6Updated Nov 3, 2026

See what's wrong with a live website from the outside, with proof: uptime, DNS, HTTPS, leaked files.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Preventionlabs checks a user's live website from the outside — uptime, DNS, HTTPS, redirects, leaked files and email deliverability — and returns…

What you can do
  • List the account's websites and see which are verified
  • Run a new external check of a verified site and get issues, warnings and evidence
  • Read the most recent report, how long ago it ran, and remaining free reports and balance
  • Grouped findings cover uptime, DNS and email records, HTTPS and certificates, redirects, JavaScript errors, leaked files and, with Cloudflare connected, server errors and blocked traffic
When to use it
Useful when a user asks what is wrong with their own site, whether it is down, slow or broken, why email lands in spam, or whether a deploy, DNS, hosting or email change broke something — and for re-checking after a fix.
Requirements
A Preventionlabs account with at least one verified website. Authentication is OAuth, or a Preventionlabs API key supplied as the PREVENTIONLABS_API_KEY environment variable for the local npm package. Available as a remote endpoint or a local stdio process; network access is needed.
Before you install
Reports cost money: the first 2 per verified site are free, then A$2 each from the account balance, so repeated runs spend funds. The API key is a secret and should be kept out of shared config. Reports only cover sites the account has proven it owns, and only what is visible from outside — not the server, code or logged-in pages.

Installation

In SourceWeft

  1. Open Preventionlabs in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/au.com.preventionlabs%2Fpreventionlabs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "preventionlabs": {
      "type": "http",
      "url": "https://app.preventionlabs.com.au/mcp"
    }
  }
}

Tools

3

list_sites

List Preventionlabs sites

Lists the user's websites in their Preventionlabs account, and whether each is verified. Call it first when the user asks about 'my website' or 'my site' without naming it, or to see which sites can be checked. Only verified sites can be checked. Costs no run.

Takes no parameters.

run_report

Check a live website

Checks the user's live website now. Use it when they ask what's wrong with their website, whether it's down, slow or broken, what security problems show from the outside, why their emails go to spam, or whether a change broke something. Runs a new Preventionlabs report on one of the account's verified websites and returns it as Markdown: what's broken on the live site and where (pages, browser errors, uptime, DNS, HTTPS, redirects, leaked files, email setup, and Cloudflare errors, deploys and recent changes when Cloudflare is connected), with evidence and what to do. Read-only. Takes 15 seconds to about a minute. Use it after a deploy or a DNS, hosting or email change, when the site seems down or broken, and again after a fix to prove it worked. Each run uses one of the site's 2 free reports, or A$2 from the account's balance; to reread the last result, use latest_report instead.

Parameterssite

latest_report

Read the latest report

Returns the most recent Preventionlabs report for a verified website, how long ago it ran, and how many free reports and how much balance are left. Costs no run. Use it to reread a result, or to check what's left before deciding whether to run a new report. It shows the site as it was then, not now.

Parameterssite

Version history

6
  1. v1.2.6LatestOct 31, 2026
  2. v1.2.4Oct 29, 2026
  3. v1.2.2Oct 26, 2026
  4. v1.2.0Oct 17, 2026
  5. v1.1.0Oct 17, 2026
  6. v1.0.1Oct 14, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.