Skip to content
Aevrin MCP · works in Claude Code, Codex and Cursor

Install one MCP.
Get six tools for your AI agent.

Add Aevrin MCP to your agent once, then just ask. It checks an MCP server before your agent trusts it, inspects a skill before you install it, shows what your agent can reach, finds and fixes problems in your code, reviews pull requests, and writes tests that really run.

Free plan, no card. Every product is included.

The Aevrin dashboard

Your AI agent writes code and plugs in new tools.

Each of those needs a safety check.

Aevrin MCP

One install. Six safety checks.

  • MCP Scanner
  • Skill Inspector
  • Agent Posture
  • Code Security
  • AI Code Reviewer
  • Test Generation

Add Aevrin MCP to your agent once. Get all six checks.

Aevrin MCP is a plug for Claude Code, Codex, Cursor or any app that speaks MCP. Run these two commands, start a new session, and ask your agent for a check in plain words.

  • Uses the key your CLI already has
  • Searching is free
aevrin login
claude mcp add-json --scope user aevrin '{
  "type": "http",
  "url": "https://api.mcp.aevrin.net/mcp",
  "headersHelper": "aevrin mcp-header"
}'
Read the setup guide
01 · MCP Scanner

Know what an MCP server does before your agent trusts it.

An MCP server is a plug that gives an AI agent new tools. Aevrin runs the server in a safe sandbox, reads every tool it offers, and grades it from A to F.

  • A clear decision

    A and B mean allow. C and D mean ask a person first. F means block. Your agent can follow that rule directly.

  • Honest about what it missed

    If a server hides its tools, the scan says it could not check them. An unfinished scan is marked incomplete and gets no grade. It is never called clean.

  • Uses a shared checklist

    Each problem is matched to the OWASP MCP Top 10, a public list of the biggest MCP risks. It reads the same in the dashboard, the terminal and CI.

Part of Aevrin MCPSee how MCP Scanner works
02 · Skill Inspector

Check an AI skill before you install it.

A skill is a set of instructions and code your agent will follow. Point Aevrin at one and it reads both. Then it tells you: Safe, Caution or Do not install.

  • Reads the words too

    A trick can hide in plain sentences, not just in code. Aevrin reads what the skill tells your agent to do, next to what its scripts really do.

  • Checks in layers

    Code checks, security rules and a lookup of known library bugs run first. An optional AI pass then reads for intent that rules cannot see.

  • Reports where you work

    SARIF for code scanning, JSON for scripts, Markdown for a pull request, and a short summary in your terminal.

03 · Agent Posture

See everything your AI agent can reach.

Aevrin reads how an AI coding agent is set up: its MCP servers, skills, plugins and hooks, and the files, keys, commands and network it can reach. Then it gives the setup a score out of 100.

  • A score you can explain

    Every agent starts at 100. Each point it loses has a name, such as a key the shell can read, so you know which setting cost it.

  • Paths, not just settings

    Aevrin joins what an agent can run with what it can read. You see the route from the agent to a secret, not a flat list of permissions.

  • Grades from real scans

    An MCP server your agent can call keeps the grade from its own scan. A server nobody has scanned is shown as ungraded, never as safe.

Part of Aevrin MCPSee how Agent Posture works
04 · Code Security

Find and fix security problems without leaving your agent.

Connect Claude Code, Codex, Cursor or another MCP app to Aevrin MCP. Your agent can then scan code, explain a problem, fix it and scan again, all in the same chat.

  • Many kinds of checks

    Aevrin MCP carries checks for web apps, APIs, logins, injection, cloud, containers, AI agents, smart contracts and more. Your agent finds the right one by asking.

  • Your code stays with you

    These checks run on your machine with your own permissions. Aevrin gives your agent the method. Your code is not uploaded.

  • Problems that hold up

    Each problem says where it is, what sets it off and what it lets someone do. It is checked against the code before you see it.

Part of Aevrin MCPSee how Code Security works
05 · AI Code Reviewer

Review code AI wrote before it ships.

Aevrin reviews pull requests, code changes and whole repositories for problems an attacker could use. It shows how the attack would work and suggests a safe fix you can apply and scan again.

  • Beyond simple patterns

    Some problems depend on what the code means, not how it looks, like a missing check on who owns a record. The reviewer reasons about that.

  • Proof, not guesses

    Each problem names the file and line, the input that reaches it, and what an attacker gets. A person can confirm it in minutes.

  • Fix, then check again

    The fix is applied as a change and the code is scanned again. The pull request closes with the problem gone, not just commented on.

06 · Test Generation

Get tests that really run.

Aevrin finds the code a change left untested and writes tests in your project's own style. It runs them, fixes the ones that fail, and gives back only tests that pass and add coverage.

  • Run, not just written

    Every test runs before you get it. A failing test is fixed or dropped. It is never handed back as if it worked.

  • Your style

    Tests use the framework, layout and style your project already has, so they read like your team wrote them.

  • Coverage you can see

    You see which lines the new tests reach and how much coverage went up, so you can tell useful tests from filler.

What a scan gives you

Everything you need to trust a server, or refuse it.

Every scan grades a server from A to F, matches its problems to the OWASP MCP Top 10, and says which step stopped if it could not finish.

A grade you can act on

Each server gets a letter from A to F and a risk score out of 100. Higher is worse.

Unfinished is never clean

A scan has five steps. If one cannot finish, the report names it and gives no grade.

Matched to the OWASP MCP Top 10

Problems map to 7 of the 10 groups. MCP08 is not tested, and every report says so.

Exit codes your CI can use

--fail-on picks the level that fails a build. Exit 3 means incomplete, so a half-done scan cannot pass quietly.

A report you can share

Pro can export a printable report. What was not checked stays in it, so a saved copy cannot make a partial scan look clean.

Explained in plain words

An AI explanation says what a problem means. It never changes a grade.

Try it on a server you already use.

The free plan has every Aevrin product and 1,500 credits a month. No card, and nothing renews on its own.

Works with the tools you already use.

Aevrin reads, scans or plugs into each of these. You keep working where you work today.

  • Claude CodeAgent posture and Aevrin MCP
  • CodexAgent posture and Aevrin MCP
  • CursorAevrin MCP
  • GitHubRepositories to scan
  • MCP serversBy web address or start command
  • Your CIExit codes for every build
  • Any MCP app

    If an app can use MCP servers, it can use Aevrin MCP.

  • One key

    Your agent uses the same Aevrin key as the CLI. There is no second account.

  • Nothing to browse

    Your agent asks for what it needs. Aevrin answers with checks an Aevrin admin has reviewed.

Where it runs

The same checks, wherever you work.

Ask your agent, type a command, add a step to CI, or open the dashboard. A problem reads the same in every place.

In your agent

Aevrin MCP gives Claude Code, Codex or Cursor three tools: find a check, get it, run it.

In your terminal

The aevrin command scans a server, a folder or your agent setup.

In CI

One step in your pipeline. It fails the build at the level you choose.

On the dashboard

Every scan, problem and agent in one place. Your account is yours alone.

Pricing

Start free. Pay when you scan more.

Two plans: Free and Pro, both spending one monthly pool of credits. Pro has a far bigger pool and adds AI code review and report export. It buys one month or one year, and nothing renews on its own.

  • Free

    No card

    $0a month

    No card needed. Nothing to cancel.

    For trying Aevrin on the servers and code you use.

    Start free

    Includes

    • Agent Posture, MCP Scanner, Skill Inspector and Code Security
    • 1,500 credits a month, spent however you like
    • An MCP scan costs 50 credits
    • A capability run costs 10, a read 1. Searching is free.
    • Agent posture on 1 monitored device
    • Aevrin MCP checks for web, API, cloud, AI agents, supply chain and more
  • Pro

    $17a month

    $199 paid once for 12 months. You save $29 a year.

    For daily use, in your terminal and in CI.

    Choose Pro, annual billing

    Includes

    • Everything in Free, with a far bigger pool
    • 50,000 credits a month at the same per-action prices
    • AI code review, 50 credits a review
    • Agent posture on up to 10 devices
    • Every Aevrin MCP check, for daily use in the terminal and CI
    • 2 capability runs at a time
    • A printable report you can export
    • Top up 5,000 credits any time; they never expire
No card for Free. Pro does not renew on its own.Buy Pro from your dashboard

Questions and answers

Something not answered here? Write to support.

Scanning

Aevrin starts the server in a throwaway container, says hello to it the way an MCP app does, and checks every tool it offers. It looks for hidden instructions, tools that ask for too much, secrets passed in as inputs, known bad packages, scripts that run on install, and more. It reads what each tool says it does, not what it does while running, so a grade describes one version at one moment.

One of the five steps could not finish. Most often the server would not start without a login of its own. The report names the step and the reason, and gives no grade. Incomplete is never treated as clean, and the CLI exits with code 3.

Seven: MCP01, MCP02, MCP03, MCP04, MCP05, MCP07 and MCP09. MCP08, hidden instructions in a live tool's answers, needs testing against a running server, so it is not tested, and every report says so. MCP06 and MCP10 have no rule.

No. An explanation describes what the scan found. It never finds anything itself, so a problem or a grade never changes because of what a model said. Explanations run on your own Groq, OpenAI, Anthropic or Google Gemini key. They see only a short, approved summary of the scan, never your code or your settings.

Agent posture

Not unless you ask. aevrin agent scan reads your Claude Code and Codex settings on your machine and runs nothing. The report stays on your machine unless you add --upload. An upload carries facts about your keys, never the keys themselves.

Aevrin MCP

An MCP server Aevrin hosts for you. Your agent connects to it with the same Aevrin key the CLI uses. Your agent says what it is trying to do, and Aevrin answers with checks an Aevrin admin has reviewed and published, each under the name that admin chose. There is nothing to browse and nothing to install: your agent asks, and Aevrin answers.

One of two answers, and the result says which. Either Aevrin runs the check on its own servers, in a closed-off sandbox that can only reach the web addresses its reviewed list allows, and hands back the output. Or Aevrin sends the steps an admin wrote, with inputs, outputs and examples, and your agent follows them itself. Neither is a lesser answer. The difference is where the work happens: steps your agent follows on your machine run with your own permissions, not inside Aevrin's sandbox.

Not yet. Searching, getting a check and getting its steps work now. Running on Aevrin's servers is built but switched off until the machine for it is ready. Until then a run returns an error, and nothing is counted against your plan.

Everything spends from your monthly credit pool (1,500 on Free, 50,000 on Pro). Searching is free and never counted. Getting one check costs 1 credit. Running one costs 10 credits on top of that read. When a check allows a recent result to be reused, that answer still costs the same 10 credits but uses none of your monthly compute time, so getting and running a check costs the same either way.

Only the input your agent gives it. A check never receives your API key, your sign-in session, your cookies or your scan history.

Plans and billing

Two: Free and Pro. Free gives you 1,500 credits a month, one watched device, and no report export; Pro gives you 50,000 credits a month, AI code review, up to 10 watched devices, and report export. Everything spends from the one pool: an MCP scan costs 50 credits, an AI code review 50 (Pro only), a capability run 10, a posture upload 5, a capability read 1. Searching is free and never counted, and a one-time top-up adds 5,000 credits that never expire. Every account is personal: only you can see your scans, problems and agents.

No. Free needs only an account. No billing details at all.

No. Each checkout buys one month or one year. Your account goes back to Free after that date unless you buy again.

Anything that costs credits pauses until the pool refills on your monthly cycle, or you upgrade, or you buy a one-time top-up of 5,000 credits that never expire. The refusal names the action, what it costs and when the pool refills, in the CLI and the dashboard. Searching stays free.