Open source · Free · Runs locally

BlissPoint AI coding-assistant scanner

The AI coding-assistant scanner is a free, open-source tool with 14 checks for the MCP servers, Agent Skills and memory files your AI coding agent loads automatically; it runs on your own machine and only reads files. Every finding is explained in plain English.

A free, open-source scanner for everything your AI coding agent loads — with every finding explained in plain English, and nothing leaving your machine.

View on GitHub →How to run itSecurity hub for small teams

The problem, in plain English

If you use Claude Code, Claude Desktop, or Cursor, your agent already trusts a growing pile of things without asking you each time: MCP servers (outside tools it can call), Agent Skills (packaged instructions it can follow), and memory files like CLAUDE.md that it reads on every session. Most teams have never seen the full list in one place — and security research keeps finding real, exploitable problems hiding in exactly these things: servers with no authentication, skills bundling malicious scripts, instruction files quietly poisoned to make an agent misbehave persistently.

The scanner inventories all of it on your own machine and tells you exactly what needs attention — in language a manager with no security background can act on, not just a security engineer.

How to run it, and what happens

  1. Get the scanner from GitHub

    You need Node.js 20 or later and git. Clone the repository and build it once; nothing is installed globally and no account is created.

    git clone https://github.com/anthonyhammock/BlissPoint-Security.git
    cd BlissPoint-Security
    npm ci
    npm run build

    The npm package is coming; until it is published, the scanner runs from source like this.

  2. Point it at your project

    From that folder, give it the path of the project you want checked: the one that holds your agent's configuration, with a .claude/ or .cursor/ directory, a CLAUDE.md, or an MCP server config.

    node dist/cli.js scan --dir ~/code/my-app

    It also lists what your agent loads from your own settings on this machine.

  3. It reads, and only reads

    The scanner opens config files and text files and looks at their contents. It never executes, imports or runs anything it finds, never changes a file, and never sends anything off your machine — there is no network call and nothing is recorded anywhere. Run it as often as you like.

  4. Read the output in your terminal

    First an inventory — how many MCP servers, skills and memory files it found — then the findings, most severe first. Each one names its rule, the file and line, what this means, and what to do, and maps to a published OWASP category. A clean run says "no known issues found by the current rules" — deliberately not "secure".

  5. Optionally, keep watching

    node dist/cli.js lock records a baseline; scan --verify then flags anything new, changed or removed since. scan --sarif results.sarif writes results for GitHub's code-scanning UI, and the ready-made GitHub Action in the repository builds the scanner from source and runs it on every push.

Terminal output of a scan: an inventory summary, then one CRITICAL finding (TXT-003) with the file and line, what it means, and what to do.
A real scan: the inventory, then one finding — rule, file and line, what it means, what to do.

What it actually checks

14 deterministic rules — no LLM involved, no network call, the same result every time on the same input. Every finding maps to the OWASP MCP Top 10 or the OWASP Agentic Skills Top 10, with a plain-English explanation and a concrete fix — never a bare "vulnerability detected". Among them:

  • Hard-coded secrets

    API keys or tokens sitting in an MCP server's config, where every agent session can read them.

  • Unpinned servers

    An MCP server launched without a pinned version — the classic "rug pull" setup where tomorrow's update isn't today's code.

  • Unauthenticated remotes

    A remote MCP server reachable with no visible authentication at all.

  • Command injection

    Shell commands assembled from untrusted input inside a server or skill.

  • Hidden Unicode

    Invisible characters in a skill or memory file — the standard way to smuggle instructions past a human reader.

  • Data exfiltration instructions

    Text telling the agent to send, upload or forward your data to an outside address.

  • Pipe-to-shell

    An instruction to download a script and run it straight away, sight unseen.

Built to be trusted

Deterministic rules, a benchmark you can run yourself, and findings you can act on in minutes.

Benchmarked, with the caveat in plain sight

Every rule is scored against a generated benchmark corpus that ships in the repository: 56 malicious and 101 clean samples, each written by a script to exercise the rules. It scores 100% precision and recall there, but the project wrote both the corpus and the rules, so that is self-graded, not independent validation. Run it yourself with npm test.

Every finding is a decision, not a guess

A finding names its rule, the file and the line, says what it means in plain English, and tells you what to do — ranked most severe first and mapped to the OWASP category it belongs to. Five minutes per finding is the design target, and most take less.

A clean run says exactly what was checked

"No known issues found by the current rules" is a precise statement: these 14 rules, this inventory, this moment. Lock a baseline and every later change to what your agent loads is flagged the instant it appears. The rule set and the tested platforms are listed in the project README.

See an AI assistant built with these safeguards: Aiva at BlissPoint Access asks before anything goes out, never sees passwords, and every action can be undone.

Who should run it, and when?

Anyone whose team uses an AI coding agent: developers, the person who looks after a small company's laptops, and managers who need to know what these tools can reach. Run it before you install a new MCP server or skill, after you copy a config from a blog post or a teammate, and on a schedule in your build pipeline so a changed file is caught the day it appears. If you hire contractors who bring their own agent setup, ask them to run it on the shared project and send you the summary.

It is one layer, not the whole job. Pair it with the basics on the Security hub: multi-factor login, same-day removal of leavers' access, and private remote access through a WireGuard VPN on your own server.

How does it compare with the scanners you already use?

What each kind of scanner looks at
CheckThis scannerTypical secrets or dependency scanner
Hard-coded API keys in MCP server configsYesOften, if the file is in the repo
Unpinned or unauthenticated MCP serversYesNo
Hidden Unicode and injected instructions in skills and memory filesYesNo
Known vulnerable packages in your appNoYes
Baseline lock to flag new or changed agent toolsYesNo

Keep your existing tools; this one covers the part of the stack they don't read.

Questions

What is an AI coding-assistant scanner?

A tool that lists everything your AI coding agent loads on its own, such as MCP servers, Agent Skills and memory files like CLAUDE.md, and flags risky settings and hidden instructions in them, with a plain-English fix for each.

Does the scanner send my code or settings anywhere?

No. It runs on your own machine, only reads files, and makes no network call. Nothing is uploaded, logged or shared.

Which AI coding tools does it support?

Claude Code, Claude Desktop and Cursor configurations, plus MCP server configs, Agent Skills folders and memory files in any project you point it at. The README lists the tested platforms.

Is it really free?

Yes. It is open source under the MIT license, with no account, no usage limit and no paid tier.

Does a clean scan mean my setup is secure?

No, and the scanner says so. A clean run means no known issues were found by its current rules. It doesn't replace reviewing what you install or a full security review.

How is this different from a secrets scanner or dependency checker?

Those look at your application code and packages. This scanner looks at what your AI agent trusts: the tools it can call, the skills it follows and the instructions it reads every session, which other scanners usually skip.

Free and open source, MIT licensed

Run it on every project, as often as you like, with nothing to sign up for. Security disclosure policy · questions to solutions@blisspointanalytics.com.

Get the source →