BrunoSan Intelligence Concierge
Discovery MCP for 11 intelligence domains plus LENS with live tools, routing and endpoints.
Should I use this
Quality & Safety
Findings (1)
- LOWin get_connection_info
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"intelligence": {
"url": "https://brunosan.de/mcp"
}
}
}Remote endpoints
https://brunosan.de/mcpstreamable-httpWhat it can do
Tool inventory
Tools (9)
βͺdiscover_brunosan
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.
Input Schema
{
"type": "object",
"properties": {},
"title": "discover_brunosanArguments"
}π‘list_intelligence_domains(include_live_tool_counts)
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.
Input Schema
{
"type": "object",
"properties": {
"include_live_tool_counts": {
"default": false,
"description": "If true, probe each canonical vertical MCP and include current tool counts.",
"title": "Include Live Tool Counts",
"type": "boolean"
}
},
"title": "list_intelligence_domainsArguments"
}π’inspect_domain(domain, include_tools)
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.
Input Schema
{
"type": "object",
"properties": {
"domain": {
"description": "Canonical domain id or name, e.g. cyber, arxiv, AI News, regulatory, lens.",
"title": "Domain",
"type": "string"
},
"include_tools": {
"default": true,
"description": "Include the live tools/list inventory and input schemas from the vertical MCP.",
"title": "Include Tools",
"type": "boolean"
}
},
"required": [
"domain"
],
"title": "inspect_domainArguments"
}π’search_capabilities(query, limit)
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.
Input Schema
{
"type": "object",
"properties": {
"query": {
"description": "Natural-language goal or capability, e.g. 'critical CVEs', 'citation network', 'EU AI Act sanctions'.",
"minLength": 2,
"title": "Query",
"type": "string"
},
"limit": {
"default": 8,
"maximum": 12,
"minimum": 1,
"title": "Limit",
"type": "integer"
}
},
"required": [
"query"
],
"title": "search_capabilitiesArguments"
}π’inspect_tool(tool_name, domain)
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.
Input Schema
{
"type": "object",
"properties": {
"tool_name": {
"description": "Exact or partial MCP tool name to inspect.",
"minLength": 1,
"title": "Tool Name",
"type": "string"
},
"domain": {
"default": "",
"description": "Optional BrunoSan domain id/name to restrict the lookup.",
"title": "Domain",
"type": "string"
}
},
"required": [
"tool_name"
],
"title": "inspect_toolArguments"
}βͺplan_intelligence_route(goal, max_domains)
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.
Input Schema
{
"type": "object",
"properties": {
"goal": {
"description": "Research or monitoring goal that may require one or several BrunoSan verticals.",
"minLength": 3,
"title": "Goal",
"type": "string"
},
"max_domains": {
"default": 3,
"maximum": 5,
"minimum": 1,
"title": "Max Domains",
"type": "integer"
}
},
"required": [
"goal"
],
"title": "plan_intelligence_routeArguments"
}π’get_connection_info(domain)
Return canonical connection details without guessing client-specific config.
Input Schema
{
"type": "object",
"properties": {
"domain": {
"description": "BrunoSan domain id/name whose canonical MCP connection should be returned.",
"title": "Domain",
"type": "string"
}
},
"required": [
"domain"
],
"title": "get_connection_infoArguments"
}π’get_intelligence_status(refresh)
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.
Input Schema
{
"type": "object",
"properties": {
"refresh": {
"default": false,
"description": "Request a fresh tools/list probe. Normal calls use the short-lived cache to protect vertical MCPs.",
"title": "Refresh",
"type": "boolean"
}
},
"title": "get_intelligence_statusArguments"
}π’get_access_options
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.
Input Schema
{
"type": "object",
"properties": {},
"title": "get_access_optionsArguments"
}Community
Evidence