app.llmauditPublished by llmaudit.appOfficial publisherv1.1.0Updated Nov 2, 2026
Measure whether AI assistants actually recommend a brand, from measured answers.
Measures whether AI assistants actually recommend a brand when buyers ask for recommendations, reporting the measured answers rather than model self-reports.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/app.llmaudit%2Fllmaudit/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"llm-audit": {
"type": "http",
"url": "https://mcp.llmaudit.app/mcp"
}
}
}MCP server for askedthrice.com. Lets anyone's assistant measure whether a brand shows up when buyers ask an AI for a recommendation.
Closed since 2026-10-29. Asked Thrice no longer runs free measurements; the product is a paid scan that needs an account.
start_visibility_checkreturnsstatus: "closed"with the link to askedthrice.com and does not call the API.get_visibility_checkstill reads measurements started before that date. The sections below describe how it worked while it was open.
Hosted at https://mcp.askedthrice.com/mcp (streamable HTTP). Listed in the official MCP registry as com.askedthrice/askedthrice. The stdio bridge for clients that only launch local commands is the npm package askedthrice-mcp, in npm/.
Full spec: specs/features/geo-13-mcp-server.md in the private llm-rank-tracker repo.
or, for command-only clients:
start_visibility_check starts the measurement and returns a runId.get_visibility_check collects it. Returns running until the providers answer.askedthrice://methodology explains how it is measured.Two tools rather than one because a measurement takes up to two minutes: the audit is 15 to 60 s and the measured map another 15 to 60 s.
It returns the measured map: the buyer questions that were asked live and who won each answer. Never the providers' self-report, which is what each model believes about the brand. The two numbers drift apart a lot in practice, and the self-report is always the optimistic one; that is why the tool contract does not expose it in any field.
It never returns a 0 to 100 score: a verdict in three bands and counts.
Every free measurement spends askedthrice's API keys, on the order of USD 0.05 to 0.15. Three guards, all covered by tests:
MCP_MONTHLY_RUN_LIMIT (default 200) as the channel ceiling, separate from the web funnel budget.npm run stats reads mcp_runs and reports how much of the monthly ceiling is left, who called, which domains were measured and which one currently holds the 30-day quota.
Needs SUPABASE_URL (or NEXT_PUBLIC_SUPABASE_URL) and SUPABASE_SERVICE_ROLE_KEY. --days is the daily detail, --history how far back it looks; the current month is always included in full, because that number has to match the guard's.
The first thing it prints, when there are any, is the orphaned runs: reserved rows that never got their audit_id. They return "Unknown runId" to the client forever while holding their domain's free quota and counting against the monthly ceiling. Delete them by run_id.
Vercel Web Analytics cannot measure this: it works by injecting a script into HTML, and here there is no HTML and no browser to run it, every request is a JSON-RPC call from an MCP client. It would read zero forever.
Dockerfile builds the HTTP server and serves it on 0.0.0.0:3001, which is what Glama and similar directories run to verify the server starts and answers introspection. Port and host are read by xmcp.config.ts at build time, so they go as ENV before npm run build, not at docker run. Without SUPABASE_* the run store is in memory: fine for a check, not for serving traffic.
Tests run against real fixtures in fixtures/ (already-paid runs from prospecting). None of them touch the network or call a provider.
server.json is published with mcp-publisher using DNS auth on askedthrice.com. The key lives outside the repo as a PEM; the CLI wants the raw ed25519 seed in hex:
Bump version in server.json on every publish; the registry rejects a repeat. When the npm package changes version, update packages[0].version too.
Source: README.md at commit 0c5e67c
Get visibility check
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.
runIdrequiredStart visibility check
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.
brandrequiredwebsiterequiredcategoryrequiredlanguagelocationcompetitors100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
{"mcpServers":{"askedthrice":{"url":"https://mcp.askedthrice.com/mcp"}}}{"mcpServers":{"askedthrice":{"command":"npx","args":["-y","askedthrice-mcp"]}}}node --env-file <file.env> scripts/stats.mjsnode --env-file <file.env> scripts/stats.mjs --days 30 --history 180npm run dev # xmcp devnpm test # vitest, no networknpm run build # xmcp buildHEX=$(openssl pkey -in <key.pem> -noout -text | sed -n '/^priv:/,/^pub:/p' | grep -v '^priv:\|^pub:' | tr -d ' :\n')mcp-publisher login dns --domain askedthrice.com --private-key "$HEX"mcp-publisher publish server.json