Skip to content

AX Audit MCP Server

io.github.AINative-Studio/ax-auditAINative-Studiostreamable-httpv1.0.0Scanned

Scan any website for AI-agent readiness: 0-100 score, grade, and agent-simulation audit.

2 tools: 2 change things.

Tools: 0 delete, 0 irreversible, 2 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 2
  • No findings

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 2Claude Code: ask
  • run_full_auditRun the full AX Audit on a URL — the same real AR-* checks as scan_site (the exact check count grows over time, so it is intentionally not pinned here), plus an agent-simulation ta…Can send data outNo findings

    Why it is in this group

    • The name "run_full_audit" says "run": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Run the full AX Audit on a URL — the same real AR-* checks as scan_site (the exact check count grows over time, so it is intentionally not pinned here), plus an agent-simulation task (e.g. "find pricing") and an industry benchmark percentile, with the result persisted server-side. Returns a report_id that can be used to retrieve the same report later without re-scanning. No authentication required.
  • scan_siteRun an AX Audit on a URL — scores how ready a website is for AI agents across every real AR-* check this engine runs (robots.txt AI policy, llms.txt, agent.json, JSON-LD, OpenAPI, …Can send data outNo findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Run an AX Audit on a URL — scores how ready a website is for AI agents across every real AR-* check this engine runs (robots.txt AI policy, llms.txt, agent.json, JSON-LD, OpenAPI, MCP/OAuth discovery, AR-PROV provisioning, and more — the exact check count grows over time, so it is intentionally not pinned here). Returns a 0-100 score, a letter grade, and a per-check breakdown. No authentication required.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http ax-audit https://ainative.ax/mcp
claude mcp add --transport http ax-audit https://ainative.ax/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__ax-audit__scan_site",
      "mcp__ax-audit__run_full_audit"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ax-audit. Review it before you use it.

Capability tags behind 2 rules
  • mcp__ax-audit__scan_site outbound
  • mcp__ax-audit__run_full_audit outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/io.github.AINative-Studio/ax-audit/verify?hash=d86c9ed450975b10eda28691964453f810843e5bad5c407367814096e5ae25ea" | jq -e '.changed == false'

Pinned hash d86c9ed45097, from Oct 27, 2026, 08:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.github.AINative-Studio/ax-audit/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for io.github.AINative-Studio/ax-audit
[![anlyon.dev](https://anlyon.dev/badge/io.github.AINative-Studio/ax-audit.svg)](https://anlyon.dev/servers/io.github.AINative-Studio/ax-audit)

Source: MCP Registry · repository. Synced Oct 27, 2026, 08:17 UTC.