BrunoSan Intelligence Concierge MCP server
de.brunosan/intelligencebrunosan.destreamable-httpv1.0.13Scanned
Discovery MCP for 11 intelligence domains plus LENS with live tools, routing and endpoints.
9 tools: 3 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 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.
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 BrunoSan Intelligence Concierge MCP server can do
The BrunoSan Intelligence Concierge MCP server is published by brunosan.de, a domain the MCP Registry verified. It has 9 tools. It can create or change data (3 tools: discover_brunosan, inspect_domain and plan_intelligence_route), but cannot delete data. 6 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
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.
Last scanned Nov 14, 2026, version 1.0.13.
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.
9 tools
Changes things 3Claude Code: ask
discover_brunosanStart here: understand the complete BrunoSan Intelligence network.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 here: understand the complete BrunoSan Intelligence network. Returns every intelligence domain, the LENS cross-domain layer, canonical MCP endpoints, human documentation, evidence doctrine, current access summary and concrete next actions. This is intentionally richer than a directory so an agent can decide whether BrunoSan can satisfy its goal.
inspect_domainOpen one BrunoSan vertical as a complete capability object.No findings
Why it is in this group
- The name "inspect_domain" says "inspect": a word for reading.
- The description's first verb is "open": a word for a change.
Description, as the server wrote it Open one BrunoSan vertical as a complete capability object. Returns purpose, canonical endpoint, human page, related routing vocabulary, disclaimer and—by default—the LIVE tools/list inventory from that vertical.
plan_intelligence_routePlan a source-authority route for a complex intelligence goal.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Plan a source-authority route for a complex intelligence goal. The plan is deterministic and names concrete live tools where possible. If several specialized domains are useful, LENS is recommended as the cross-domain entity layer. V1 plans and connects; it does not proxy protected vertical calls.
Only reads 6Show 6 read-only tools
get_access_optionsReturn current BrunoSan access and pricing from the shared pricing manifest.No findings
Why it is in this group
- The name "get_access_options" says "get": a word for reading.
Description, as the server wrote it Return current BrunoSan access and pricing from the shared pricing manifest. No price is embedded in this server. Unknown or absent manifest values stay absent rather than being estimated.
get_connection_infoReturn canonical connection details without guessing client-specific config.No findings
Why it is in this group
- The name "get_connection_info" says "get": a word for reading.
Description, as the server wrote it Return canonical connection details without guessing client-specific config.
get_intelligence_statusCheck whether each canonical BrunoSan MCP currently initializes and lists tools.No findings
Why it is in this group
- The name "get_intelligence_status" says "get": a word for reading.
Description, as the server wrote it Check whether each canonical BrunoSan MCP currently initializes and lists tools. This is a capability-plane health check only; it does not execute protected intelligence tools or make claims about underlying data freshness.
inspect_toolFind and inspect one underlying vertical MCP tool.No findings
Why it is in this group
- The name "inspect_tool" says "inspect": a word for reading.
Description, as the server wrote it Find and inspect one underlying vertical MCP tool. Returns the owning domain, exact live tool description and input schema. This does not execute the tool and never requests or forwards an API key.
list_intelligence_domainsList all BrunoSan intelligence authorities.No findings
Why it is in this group
- The name "list_intelligence_domains" says "list": a word for reading.
Description, as the server wrote it List all BrunoSan intelligence authorities. By default this is instant and SSOT-only. Set include_live_tool_counts=true when the agent needs proof that the underlying MCP servers are reachable now.
search_capabilitiesSearch the whole BrunoSan network for what an agent is trying to do.No findings
Why it is in this group
- The name "search_capabilities" says "search": a word for reading.
Description, as the server wrote it Search the whole BrunoSan network for what an agent is trying to do. Ranking is deterministic over SSOT descriptions, a documented routing vocabulary and LIVE tool names/descriptions/schemas. Returns concrete tool candidates, not merely domain names.
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 or outbound.
- 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 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.
Looked at Nov 20, 2026, 18:51 UTC, unchanged since Oct 22, 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
- 3
- 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 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://brunosan.de/mcp: tools/list returned 9 tools to an anonymous client, including discover_brunosan (write), inspect_domain (write), plan_intelligence_route (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.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.13. Values in angle brackets are yours to fill in.
claude mcp add --transport http intelligence https://brunosan.de/mcpclaude mcp add --transport http intelligence https://brunosan.de/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__intelligence__list_intelligence_domains",
"mcp__intelligence__search_capabilities",
"mcp__intelligence__inspect_tool",
"mcp__intelligence__get_connection_info",
"mcp__intelligence__get_intelligence_status",
"mcp__intelligence__get_access_options"
],
"ask": [
"mcp__intelligence__discover_brunosan",
"mcp__intelligence__inspect_domain",
"mcp__intelligence__plan_intelligence_route"
],
"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 intelligence. Review it before you use it.
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/de.brunosan/intelligence/verify?hash=8da1ee66a69ee03118a2d4d5ad2cf3f46c6448034badf9811943d26c4c47dc0b" | jq -e '.changed == false'Pinned hash 8da1ee66a69e, from Nov 14, 2026, 22:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/de.brunosan/intelligence/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/de.brunosan/intelligence)Source: MCP Registry. Synced Oct 21, 2026, 18:11 UTC.
BrunoSan Intelligence Concierge MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BrunoSan Intelligence Concierge MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 3 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 BrunoSan Intelligence Concierge MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the BrunoSan Intelligence Concierge 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 BrunoSan Intelligence Concierge MCP server have?
- 9 tools: 3 write, 6 read. discover_brunosan, inspect_domain, plan_intelligence_route, list_intelligence_domains, search_capabilities, inspect_tool, get_connection_info, get_intelligence_status and 1 more.
Does the BrunoSan Intelligence Concierge MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BrunoSan Intelligence Concierge MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the BrunoSan Intelligence Concierge MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.