Skip to content

TofuBofu AI Visibility MCP server

com.tofubofu/ai-visibilitytofubofu.comstreamable-httpv1.0.0Scanned

Free AI visibility scan for any B2B company: see how often AI engines recommend it, plus the fixes.

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the TofuBofu AI Visibility MCP server can do

The TofuBofu AI Visibility MCP server is published by tofubofu.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: research_company and scan_ai_visibility), but cannot delete data. 1 tool only reads.

2 tools bring in text other people can write (research_company and scan_ai_visibility).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • research_companyStep one of a scan: read the company's website and return the scan form's steps, pre-filled with what we read.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Step one of a scan: read the company's website and return the scan form's steps, pre-filled with what we read. Call this first, walk the user through `steps` in order, show them the answers and the queries, and get a yes before calling scan_ai_visibility. Every value is a guess from the website (or, for a signed-in workspace's returning brand, what the brand already holds) for the user to confirm or correct. Returns brand_name, steps (each with title and fields: param, question, help, kind, options, value, suggestions), scan (engines, queries_per_engine, queries_total) and how_to_ask.

    Annotations the server declares

    • title: Read a company's website for the scan
    • readOnlyHint: true
    • openWorldHint: true
  • scan_ai_visibilityStart an AI-visibility scan of a company's website.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Start an AI-visibility scan of a company's website. It asks ChatGPT, Claude, Perplexity, Gemini, Google AI Mode real buying queries and records which companies they name. A free scan asks 5 queries on each engine, 25 in all. A call carrying a TofuBofu API key (Authorization: Bearer tb_live_...) re-scans that workspace's existing brand for the website, on its plan and quota. Before calling: call research_company, walk the user through its steps, show them the pre-filled answers and the queries (for a returning brand, the ones its last scan asked, which this scan asks again), and get a yes. Ask where they sell if you do not know it: geo_scope changes every query. Omit a field you do not know rather than inventing a value. The scan runs in the background (a few minutes); call get_visibility_report with the returned report_id. Returns report_id, report_url, assumed (answers not supplied) and query_warnings (buyer_questions that read as a topic, each with its reason; every one is still asked as sent). status "not_started" with report_id null means no scan ran: the email already has an account, or this website's free scan already ran this month. A sign-in link went to that inbox; show the note and stop.

    Annotations the server declares

    • title: Run AI visibility scan
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • 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 Tofu Index (named in the consideration set) and the Bofu Index (picked head to head), each with its fraction, the Tofu Index per engine, share of voice, sentiment, the top competitors winning the answers, any gap between the competitors the user named and the ones AI names, and top_fixes, the open items at the top of the brand's Fixes list (the same list the app's Fixes page shows; empty when there is none), 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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:48 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://tofubofu.com/mcp: tools/list returned 3 tools to an anonymous client, including research_company (write), scan_ai_visibility (write)

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 1 to 2

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 2 changed.+1 added~2 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 2.View diff
    • Tools that change things, listed without credentials: 1 to 2

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/mcp
claude mcp add --transport http ai-visibility https://tofubofu.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ai-visibility__get_visibility_report"
    ],
    "ask": [
      "mcp__ai-visibility__research_company",
      "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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ai-visibility. Review it before you use it.

Capability tags behind 2 rules
  • mcp__ai-visibility__research_company untrusted-input
  • mcp__ai-visibility__scan_ai_visibility untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.tofubofu/ai-visibility/verify?hash=b7204e7a1156e347498126170181ecbe10e550d2071b83d39462045bef91a5ca" | jq -e '.changed == false'

Pinned hash b7204e7a1156, from Nov 14, 2026, 15:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.tofubofu/ai-visibility/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.tofubofu/ai-visibility
[![Anlyon Radar](https://radar.anlyon.com/badge/com.tofubofu/ai-visibility.svg)](https://radar.anlyon.com/servers/com.tofubofu/ai-visibility)

Source: MCP Registry. Synced Oct 21, 2026, 18:07 UTC.

TofuBofu AI Visibility MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the TofuBofu AI Visibility MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the TofuBofu AI Visibility MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the TofuBofu AI Visibility MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the TofuBofu AI Visibility MCP server have?

3 tools: 2 write, 1 read. research_company, scan_ai_visibility and get_visibility_report.

Does the TofuBofu AI Visibility MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the TofuBofu AI Visibility MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the TofuBofu AI Visibility MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 1, 2026. Every change is on this page and in its Atom feed.