LLM Audit
REMOTE · MCP.LLMAUDIT.APP · 2 COMPONENTS · SCANNED SEP 20
Measure whether AI assistants actually recommend a brand, from measured answers.
Available components
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Renamed to com.askedthrice/askedthrice. Same server, same maintainer; the endpoint is now https://mcp.askedthrice.com/mcp and the npm package is askedthrice-mcp.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 292 tokens (~97/item across 3 items; 2 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the LLM Audit MCP server?
LLM Audit is a hosted endpoint at https://mcp.llmaudit.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.llmaudit.app
claude mcp add --transport http app-llmaudit-llmaudit 'https://mcp.llmaudit.app/mcp'
{
"mcpServers": {
"app-llmaudit-llmaudit": {
"url": "https://mcp.llmaudit.app/mcp"
}
}
} {
"servers": {
"app-llmaudit-llmaudit": {
"type": "http",
"url": "https://mcp.llmaudit.app/mcp"
}
}
} [mcp_servers.app-llmaudit-llmaudit] url = "https://mcp.llmaudit.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-llmaudit-llmaudit": {
"type": "remote",
"url": "https://mcp.llmaudit.app/mcp",
"enabled": true
}
}
} openclaw mcp add app-llmaudit-llmaudit --url 'https://mcp.llmaudit.app/mcp' --transport streamable-http
mcp_servers:
app-llmaudit-llmaudit:
url: "https://mcp.llmaudit.app/mcp" {
"McpServers": {
"app-llmaudit-llmaudit": {
"Transport": "http",
"Url": "https://mcp.llmaudit.app/mcp"
}
}
} assistant mcp add app-llmaudit-llmaudit -t streamable-http -u 'https://mcp.llmaudit.app/mcp'
{
"mcpServers": {
"app-llmaudit-llmaudit": {
"type": "http",
"url": "https://mcp.llmaudit.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.llmaudit.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.llmaudit.app | CN=YR2,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | RSA 2048 | SHA256-RSA | 5a8a571aa7c6f6611fcbc802caa9de66b5a |
| SANs: *.llmaudit.app, llmaudit.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.llmaudit.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| llmaudit.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.llmaudit.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.llmaudit.app/mcp | HTTPS enforced | 308 | https://mcp.llmaudit.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_visibility_check Get visibility check ~82
Collect the result of a measurement started with start_visibility_check. Returns status running while the providers are still answering, so poll every 20 to 30 seconds. When ready it reports a verdict, how many of the buyer questions the brand won, which competitors were named instead, and which providers actually answered.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | From start_visibility_check |
No output schema declared.
No examples provided.
start_visibility_check Start visibility check ~191
Measure whether a brand shows up when buyers ask AI assistants for a recommendation. Asks real buyer questions to OpenAI, Anthropic and Gemini and reports what they answered, not what they claim they would answer. Free, no signup, one measurement per domain every 30 days. Returns a runId: call get_visibility_check with it after about a minute. If the domain was already measured this month the response says quota_reached and includes when it ran.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand name as customers write it |
| category | string | yes | What the business sells, in plain words |
| competitors | string | – | Up to 5 real competitors, comma separated |
| language | string | – | Language the buyer questions are asked in |
| location | string | – | Where the business competes, like 'Cordoba, Argentina' |
| website | string | yes | Domain, like yourbrand.com |
No output schema declared.
No examples provided.
What is the LLM Audit MCP server?
LLM Audit is an MCP server listed in the public MCP registry as app.llmaudit/llmaudit. Measure whether AI assistants actually recommend a brand, from measured answers. This page covers its hosted endpoint (https://mcp.llmaudit.app/mcp).
Is the LLM Audit MCP server safe to use?
LLM Audit scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the LLM Audit MCP server expose?
LLM Audit exposes 2 tools: get_visibility_check, start_visibility_check. Their descriptions and schemas cost roughly 273 tokens of context every time the server is loaded.
Does the LLM Audit MCP server require authentication?
No. We connected to LLM Audit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LLM Audit MCP server still maintained?
LLM Audit is marked deprecated in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.