mcp server
TofuBofu AI Visibility
Free AI visibility scan for any B2B company: see how often AI engines recommend it, plus the fixes.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-07-16.
What this server can do
2 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_visibility_report(report_id)- 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. Required: report_id.
scan_ai_visibility(email, domain, capacity, sells_to, geo_scope, locations, competitors, buyer_questions)- 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. Args: domain: The company's website or domain, e.g. "acme.com". email: The user's work email. Required, we send the finished report here and it identifies the account. One free scan per email per month. geo_scope: How the company sells. One of "global" (software and products, buyers anywhere), "national" (services across one whole country), "national_local" (national with a strong local angle, e.g. cybersecurity, accounting, consulting), "local" (bound to its own cities, e.g. a regional MSP). Omit if the user does not know. locations: The country for "national", or the cities for "local", e.g. ["Canada"] or ["Vancouver, BC", "Seattle, WA"]. competitors: Companies the user says they compete with. buyer_questions: Questions the user's buyers actually ask AI. These are asked verbatim and tracked scan over scan. sells_to: Who they sell to, in the user's own words, e.g. ["SMB", "healthcare", "IT directors"]. Apollo and ZoomInfo sell the same category to different halves of the market, so this changes the altitude of every buying question. capacity: Who will do the fixes. One of "solo", "one_marketer", "small_team", "full_team". Sizes the action plan. 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. Required: domain, email.
Last successful function declaration observed on . Source: https://tofubofu.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://tofubofu.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-16 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-16 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 2 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | tofubofu.com | |
| mcp endpoint status | ok | The server listed 2 functions when asked. | as of probe | tofubofu.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json