Security check for AI agents and MCP servers

Is your AI agent open to strangers?

One unprotected endpoint or leaked key can let anyone use your agent, or run up your AI bill. Find out in about a minute, for free.

  • No sign-up
  • Never runs your agent's tools
  • Fix prompts for Claude Code, Cursor and Lovable

What we check

The four ways AI agents most often leak access or money.

Open MCP servers

Can anyone connect to your MCP server and list its tools? We ask it the same way any MCP client would, and rank what it exposes by risk. We never run a tool.

Open agent endpoints

Will your chat or agent route answer a stranger with no login? If it does, anyone can run up your AI bill. We send one tiny message to find out.

Leaked AI keys

We look through your site's code and your public repo for Anthropic, OpenAI, Gemini, Stripe and other keys that strangers could copy.

Risky agent settings

We read your agent config files for tokens written in plain text, blanket shell access, and settings that skip every permission check.

Antivirus won't catch these. It looks for viruses on your computer, but these are settings on your agent's servers.

How it works

  1. Scan for free

    Paste your MCP server or agent URL, your public GitHub repo, or both. You get a grade and a count of problems.

  2. Prove it's yours

    Add a short token to your site or repo. This unlocks the deeper checks and keeps your results private to you.

  3. Fix it

    The full report shows where each problem is and gives you a prompt to paste into your AI coding tool to fix it.

Pricing

Start free. Pay only if there's something to fix.

Free scan

Free
  • Grade out of 100
  • Number of problems in each check
  • One scan per target per day
Scan now

Full report

A$199 one time
  • Where every problem is
  • How serious each one is
  • A fix prompt for each problem
  • Kept for 30 days
See a sample
Best value

Daily monitoring

A$79 / month

or A$790/year, 2 months free

  • Everything in the full report
  • We re-scan every day
  • An email when a new problem appears
  • Free GitHub badge showing your latest grade
  • Cancel anytime
Scan first
Example badge: agent safety check, grade A, with the date it was last checked

Show people your agent is checked

Daily monitoring includes a badge for your GitHub page. It shows your latest grade and the date we last checked, and updates after every daily scan, so visitors can see you take security seriously.

We only scan what you own

Every scan asks you to confirm you own the target or have the owner's permission. Checks that talk to an agent only run after you prove ownership, and the full report only shows details for targets you've proved are yours. Found keys are masked before they're saved. Our scanner refuses to reach private networks or cloud metadata addresses.

Questions

What is Agent Safety Check?

A security scanner for AI agents. It checks whether your MCP server or agent endpoint answers strangers with no login, whether AI or payment keys are visible in your site's code or public GitHub repo, and whether your agent config files have risky settings.

Why does it matter if my MCP server is open?

An MCP server gives an AI agent tools, such as reading files, sending email or querying a database. If it answers anyone who knows its address, strangers can list and use those tools too. Many servers are left open because the quick-start examples don't add a login.

I already pay for antivirus. Doesn't that cover this?

No, they do different jobs. Antivirus checks the files on your computer for known viruses. These problems aren't viruses. They're settings on servers you run on the internet, such as an MCP server with no login, a chat page anyone can use, or an AI key sitting in public code. Nothing on your computer looks wrong, so antivirus has nothing to catch. Keep your antivirus, and check your agent's setup too.

Why not just ask ChatGPT?

You can ask any AI for advice, and it's often useful. But a chatbot reads your site the way a person reads a web page. We test it. Our scanner connects to your agent the way other software would, and checks whether your MCP server (the connection that lets your AI use tools) lets anyone in without a password. It also searches your site's code and your GitHub repo for leaked keys. We run the same checks the same way every time, so results don't depend on how you word the question. With daily monitoring, we compare each day's results with the day before and only email you when something new goes wrong. And we never ask for your keys, so there's nothing sensitive to paste anywhere.

Is it safe to scan my agent?

Yes. The free scan only reads what any browser or GitHub visitor can already see. The two checks that talk to your agent send at most a handful of tiny requests, never call a tool, and only run after you prove you own it.

Why do I have to prove I own it?

So nobody can use us to find holes in someone else's agent. You add a short token to your site or repo, which takes about a minute. We show the details of a problem only to the proven owner.

What do I get in the full report?

Every problem we found, exactly where it is (the URL, or the file and line), how serious it is, and a ready-to-paste prompt that fixes it in Claude Code, Cursor or Lovable.

Do you store my keys or code?

No. Any key we find is masked before it's saved, so we only keep the first and last few characters. Scan results are deleted after 30 days.

Does a good grade mean my code is safe?

No. A grade tells you how your agent did on our four checks on the day we ran them. We don't scan for viruses or every kind of bug, so no scanner, including ours, can promise code is completely safe. Daily monitoring re-runs the checks every day so you hear about new problems quickly.

What if the scan finds nothing?

Then you don't need to pay for anything. The free scan tells you how many problems there are before you decide.

Check your agent before someone else does

Run a free scan