BriefBash MCP server
com.briefbash/mcpbriefbash.comstreamable-httpv1.0.1Scanned
AI-citation (GEO) teardowns of any website: score, blockers, attack points.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 BriefBash MCP server can do
The BriefBash MCP server is published by briefbash.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: submit_analysis), but cannot delete data. 1 tool only reads.
1 tool can send data out of your system (submit_analysis).
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 21, 2026, version 1.0.1.
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.
2 tools
Changes things 1Claude Code: ask
submit_analysisSubmit a website URL to BriefBash for an AI-citation (GEO) teardown: how visible the site is to ChatGPT/Perplexity/AI Overviews, what blocks citations (llms.txt, bot access, schema…Can send data outNo findings
Why it is in this group
- The name "submit_analysis" says "submit": a word for a change.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Submit a website URL to BriefBash for an AI-citation (GEO) teardown: how visible the site is to ChatGPT/Perplexity/AI Overviews, what blocks citations (llms.txt, bot access, schema), and the attack points a competitor is winning with. Returns a brief_id — poll get_brief until status is done (typically 1-3 minutes). The first brief per email is free.
Annotations the server declares
- readOnlyHint: false
Only reads 1Show 1 read-only tool
get_briefFetch the summary of a BriefBash teardown by brief_id.No findings
Why it is in this group
- The name "get_brief" says "get": a word for reading.
Description, as the server wrote it Fetch the summary of a BriefBash teardown by brief_id. While status is "processing", wait check_back_seconds and call again. When done, returns the AI-citation score, potential score, blockers and top attack points. Full interactive teardown is at brief_url.
Annotations the server declares
- readOnlyHint: true
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 untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- 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.
Looked at Nov 21, 2026, 19:21 UTC, unchanged since Nov 7, 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
- 1
- 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 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://briefbash.com/mcp: tools/list returned 2 tools to an anonymous client, including submit_analysis (write)
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.
Tools2 changed.~2 changedView diff
- Changed:get_briefOnly readstitleannotations
- Changed:submit_analysisChanges thingstitleinputSchemaannotations
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http briefbash https://briefbash.com/mcpclaude mcp add --transport http briefbash https://briefbash.com/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__briefbash__get_brief"
],
"ask": [
"mcp__briefbash__submit_analysis"
],
"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 briefbash. Review it before you use it.
Capability tags behind 1 rule
- mcp__briefbash__submit_analysis outbound
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.briefbash/mcp/verify?hash=b434314907e328e686b4e8fd46f844b453ffdcbf70fefe68b3baa586d5b5e802" | jq -e '.changed == false'Pinned hash b434314907e3, from Nov 21, 2026, 19:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.briefbash/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.briefbash/mcp)Source: MCP Registry. Synced Nov 7, 2026, 14:17 UTC.
BriefBash MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BriefBash MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 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 BriefBash MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the BriefBash 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 BriefBash MCP server have?
- 2 tools: 1 write, 1 read. submit_analysis and get_brief.
Does the BriefBash MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BriefBash MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): submit_analysis.
Has the BriefBash MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 7, 2026. Every change is on this page and in its Atom feed.