TofuBofu AI Visibility
by tofubofu.com · remote · no sign-in to list tools · v1.0.0 · published by com.tofubofu
Free AI visibility scan for any B2B company: see how often AI engines recommend it, plus the fixes.
2 tools: 1 change things and 1 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things1Claude Code: ask: see these tools
- Only reads1Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http ai-visibility https://tofubofu.com/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
2 tools
Changes things 1Claude Code: ask
scan_ai_visibilityStart a free AI-visibility scan for a B2B company's website.No findings
Why it is in this group
- The description's first verb is "start": a word for a change.
Description, as the server wrote it Start a free AI-visibility scan for a B2B company's website. Checks how often AI engines (ChatGPT, Claude, Perplexity, Gemini, Google AI Mode, Microsoft Copilot) name the company when buyers ask for vendor recommendations, and finds the gaps. The scan runs in the background (roughly 1-2 minutes); call get_visibility_report with the returned report_id to read the score and findings. ASK THE USER for geo_scope and sells_to before calling, if you do not already know them. Everything past `email` is optional and the scan runs without it, but geo_scope changes EVERY question we generate: a firm that sells across one country, scored on one city's questions, looks invisible when it is not. Guessing is worse than asking, and asking costs one line of conversation. Where you do not know, omit the field rather than inventing a plausible value: an omitted field is recorded as unknown, and the report says its framing was assumed. Every parameter carries its own description, generated from the one intake contract the in-app scan form renders from, so what you are told here and what a customer is asked are the same question. Returns: report_id, a report_url to view live, whether an existing report was reused (free scan already used this month), and which intake answers were missing, so you can offer to re-run with them.
Annotations the server declares
- title: Run AI visibility scan
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 1Claude Code: allow
get_visibility_reportFetch the results of an AI-visibility scan started with scan_ai_visibility.No findings
Why it is in this group
- The name "get_visibility_report" says "get": a word for reading.
Description, as the server wrote it Fetch the results of an AI-visibility scan started with scan_ai_visibility. Args: report_id: The id returned by scan_ai_visibility. Returns: While running: {status: "running", progress}. When done: the visibility score, how often AI mentions the brand, share of voice, top competitors winning the answers, and the highest-priority fixes, plus the report_url.
Annotations the server declares
- title: Get AI visibility report
- readOnlyHint: true
- openWorldHint: false
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.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ai-visibility https://tofubofu.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ai-visibility__get_visibility_report"
],
"ask": [
"mcp__ai-visibility__scan_ai_visibility"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as ai-visibility. Review it before you use it.