mcpbeat

Audit MCP Server

ai.webmatik/audit
answering

Audit is answering right now. Last checked 12 min ago. It exposes 2 tools.

AI website growth audits: SEO, performance, AI readiness (GEO), conversion, a11y, security.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
535 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add audit --transport http https://webmatik.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "audit": {
      "url": "https://webmatik.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.audit]
url = "https://webmatik.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "audit": {
      "url": "https://webmatik.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "audit": {
      "url": "https://webmatik.ai/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

audit
get_audit
Fetch a Webmatik audit by id. While background analysis (AI vision, AI search visibility) is still running the response says so — poll every ~15s until status is "completed". Returns scores per category, failed checks, and the prioritized recommendations.
run_audit
Start a full Webmatik growth audit of a website: SEO, performance (Core Web Vitals), AI readiness (GEO), conversion, retention, UI/UX, accessibility, and security — 70+ checks with a 0–100 Growth Score and a prioritized action plan. The audit takes 60–180 seconds; this returns an auditId immediately — poll get_audit for the result. Requires a Webmatik API key (get one at https://webmatik.ai/account, Starter/Growth plans).

Endpoints

URLTransportStateLatencyChecked
https://webmatik.ai/mcp streamable-http answering 524 ms 12 min ago

Audit — questions

Answers built from our own checks of this server.

What can Audit do?
It exposes 2 tools, read directly from the server on our last check. Among them: get_audit, run_audit. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Audit working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 535 ms. The bar chart above shows every period we have measured.
How do I connect Audit?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Audit need an API key?
No. Audit completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Audit?
It answers our handshake in 535 ms on average, which is faster than 20% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.