TofuBofu AI Visibility
REMOTE · TOFUBOFU.COM · SCANNED SEP 26
Free AI visibility scan for any B2B company: see how often AI engines recommend it, plus the fixes.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1097 tokens (~548/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the TofuBofu AI Visibility MCP server?
TofuBofu AI Visibility is a hosted endpoint at https://tofubofu.com/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 · tofubofu.com
claude mcp add --transport http com-tofubofu-ai-visibility 'https://tofubofu.com/mcp'
{
"mcpServers": {
"com-tofubofu-ai-visibility": {
"url": "https://tofubofu.com/mcp"
}
}
} {
"servers": {
"com-tofubofu-ai-visibility": {
"type": "http",
"url": "https://tofubofu.com/mcp"
}
}
} [mcp_servers.com-tofubofu-ai-visibility] url = "https://tofubofu.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-tofubofu-ai-visibility": {
"type": "remote",
"url": "https://tofubofu.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-tofubofu-ai-visibility --url 'https://tofubofu.com/mcp' --transport streamable-http
mcp_servers:
com-tofubofu-ai-visibility:
url: "https://tofubofu.com/mcp" {
"McpServers": {
"com-tofubofu-ai-visibility": {
"Transport": "http",
"Url": "https://tofubofu.com/mcp"
}
}
} assistant mcp add com-tofubofu-ai-visibility -t streamable-http -u 'https://tofubofu.com/mcp'
{
"mcpServers": {
"com-tofubofu-ai-visibility": {
"type": "http",
"url": "https://tofubofu.com/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.
- 26 Sept 26 0
- “scan_ai_visibility” reworded the description of “buyer_questions” cosmetic
- “scan_ai_visibility” reworded the description of “geo_scope” cosmetic
- “scan_ai_visibility” reworded the description of “locations” cosmetic
- “scan_ai_visibility” reworded the description of “sells_to” cosmetic
4 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 21 Aug 26 0
- Tool “scan_ai_visibility” rewrote its description, which is the text the model reads security
- Schema quality: 402 → 548 ▼ functional
- Tool coverage: 0% → 89% ▲ functional
- “scan_ai_visibility” reworded the description of “buyer_questions” cosmetic
- “scan_ai_visibility” reworded the description of “capacity” cosmetic
- “scan_ai_visibility” reworded the description of “competitors” cosmetic
- “scan_ai_visibility” reworded the description of “domain” cosmetic
- “scan_ai_visibility” reworded the description of “email” cosmetic
- “scan_ai_visibility” reworded the description of “geo_scope” cosmetic
- “scan_ai_visibility” reworded the description of “locations” cosmetic
- “scan_ai_visibility” reworded the description of “sells_to” cosmetic
- 14 Aug 26 0
- Tool “scan_ai_visibility” rewrote its description, which is the text the model reads security
- Schema quality: 181 → 402 ▼ functional
- “scan_ai_visibility” added an optional parameter “buyer_questions” cosmetic
- “scan_ai_visibility” added an optional parameter “capacity” cosmetic
- “scan_ai_visibility” added an optional parameter “competitors” cosmetic
- “scan_ai_visibility” added an optional parameter “geo_scope” cosmetic
- “scan_ai_visibility” added an optional parameter “locations” cosmetic
- “scan_ai_visibility” added an optional parameter “sells_to” cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
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 26 Sept 2026 · Probed https://tofubofu.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tofubofu.com | CN=WR3,O=Google Trust Services,C=US | 17 Aug 2026 | 15 Nov 2026 | RSA 2048 | SHA256-RSA | d30c0acabb83397d107ba09c146031f4 |
| SANs: tofubofu.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tofubofu.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tofubofu.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tofubofu.com/mcp | Verified | 200 | |
| http (plaintext) | http://tofubofu.com/mcp | HTTPS enforced | 302 | https://tofubofu.com/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_report ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | – |
No output schema declared.
No examples provided.
scan_ai_visibility ~927
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.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer_questions | – | – | Queries your buyers ask. Queries this company's buyers actually ask. They are put to the engines verbatim and tracked scan over scan, which is what makes a trend line mean anything. Shapes the querie… |
| capacity | string | – | Who will do the fixes? We size and sequence the plan to match. A solo founder does not get a list built for a five-person team. One of: solo (Just me); one_marketer (One marketer); small_team (A smal… |
| competitors | – | – | Who would a buyer otherwise pick? Companies the user says a buyer would pick instead of them. We track whoever the engines name either way, so this is the user's own view rather than the whole compar… |
| domain | string | yes | The company's website or domain, e.g. "acme.com". |
| string | yes | The user's work email. Required: we send the finished report there and it identifies the account. One free scan per email per month. | |
| geo_scope | string | – | Where do you sell? Getting this wrong skews the whole report: a national firm scored on one city's queries looks invisible, and a local one scored nationally looks unwinnable. One of: global (Anywher… |
| locations | – | – | Which places? The country you sell across, or the cities you are bound to. Shapes which geography goes into a localized buying query. Omit it rather than guessing: an omitted answer is recorded as un… |
| sells_to | – | – | What size and type of customer? SMB and enterprise are different queries with different winners. Shapes the same. 'Best sales engagement platform for SMB teams' is not the same query as 'for enterpri… |
No output schema declared.
No examples provided.
What is the TofuBofu AI Visibility MCP server?
TofuBofu AI Visibility is an MCP server listed in the public MCP registry as com.tofubofu/ai-visibility. Free AI visibility scan for any B2B company: see how often AI engines recommend it, plus the fixes. This page covers its hosted endpoint (https://tofubofu.com/mcp).
Is the TofuBofu AI Visibility MCP server safe to use?
TofuBofu AI Visibility scores 75 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 TofuBofu AI Visibility MCP server expose?
TofuBofu AI Visibility exposes 2 tools: scan_ai_visibility, get_visibility_report. Their descriptions and schemas cost roughly 1,030 tokens of context every time the server is loaded.
Does the TofuBofu AI Visibility MCP server require authentication?
No. We connected to TofuBofu AI Visibility without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TofuBofu AI Visibility MCP server still maintained?
TofuBofu AI Visibility is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.