# BrunoSan Intelligence Concierge (remote · brunosan.de)

Discovery MCP for 11 intelligence domains plus LENS with live tools, routing and endpoints.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `brunosan.de`: 72/100 (this document), [markdown](https://verifymcp.io/servers/de-brunosan-intelligence/brunosan.md), [page](https://verifymcp.io/servers/de-brunosan-intelligence/brunosan)

## Channel facts

- Endpoint: `https://brunosan.de/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.13`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-27.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 894 tokens (~74/item across 12 items; 9 tools + 3 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the BrunoSan Intelligence Concierge MCP server?

BrunoSan Intelligence Concierge is a hosted endpoint at https://brunosan.de/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.

### Claude

```bash
claude mcp add --transport http de-brunosan-intelligence 'https://brunosan.de/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "de-brunosan-intelligence": {
      "url": "https://brunosan.de/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "de-brunosan-intelligence": {
      "type": "http",
      "url": "https://brunosan.de/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.de-brunosan-intelligence]
url = "https://brunosan.de/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "de-brunosan-intelligence": {
      "type": "remote",
      "url": "https://brunosan.de/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add de-brunosan-intelligence --url 'https://brunosan.de/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  de-brunosan-intelligence:
    url: "https://brunosan.de/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "de-brunosan-intelligence": {
      "Transport": "http",
      "Url": "https://brunosan.de/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add de-brunosan-intelligence -t streamable-http -u 'https://brunosan.de/mcp'
```

### Other

```json
{
  "mcpServers": {
    "de-brunosan-intelligence": {
      "type": "http",
      "url": "https://brunosan.de/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-27 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 71, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-22 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-14 (score 66)

First indexed and scored.

## MCP tools (9)

### `discover_brunosan` (~79 tokens)

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.

### `list_intelligence_domains` (~74 tokens)

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 parameters:

- `include_live_tool_counts` (boolean): If true, probe each canonical vertical MCP and include current tool counts.

### `inspect_domain` (~98 tokens)

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 parameters:

- `domain` (string, required): Canonical domain id or name, e.g. cyber, arxiv, AI News, regulatory, lens.
- `include_tools` (boolean): Include the live tools/list inventory and input schemas from the vertical MCP.

### `search_capabilities` (~98 tokens)

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 parameters:

- `limit` (integer)
- `query` (string, required): Natural-language goal or capability, e.g. 'critical CVEs', 'citation network', 'EU AI Act sanctions'.

### `inspect_tool` (~81 tokens)

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 parameters:

- `domain` (string): Optional BrunoSan domain id/name to restrict the lookup.
- `tool_name` (string, required): Exact or partial MCP tool name to inspect.

### `plan_intelligence_route` (~102 tokens)

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 parameters:

- `goal` (string, required): Research or monitoring goal that may require one or several BrunoSan verticals.
- `max_domains` (integer)

### `get_connection_info` (~38 tokens)

Return canonical connection details without guessing client-specific config.

Input parameters:

- `domain` (string, required): BrunoSan domain id/name whose canonical MCP connection should be returned.

### `get_intelligence_status` (~77 tokens)

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 parameters:

- `refresh` (boolean): Request a fresh tools/list probe. Normal calls use the short-lived cache to protect vertical MCPs.

### `get_access_options` (~46 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/de-brunosan-intelligence/brunosan#diagnostics

## Score history

- 2026-09-27: 72
- 2026-09-26: 71
- 2026-09-25: 71
- 2026-09-24: 70
- 2026-09-23: 70
- 2026-09-22: 70
- 2026-09-21: 69
- 2026-09-20: 69
- 2026-09-19: 68
- 2026-09-18: 68
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 66
- 2026-09-14: 66

## Common questions

### What is the BrunoSan Intelligence Concierge MCP server?

BrunoSan Intelligence Concierge is an MCP server listed in the public MCP registry as de.brunosan/intelligence. Discovery MCP for 11 intelligence domains plus LENS with live tools, routing and endpoints. This page covers its hosted endpoint (https://brunosan.de/mcp).

### Is the BrunoSan Intelligence Concierge MCP server safe to use?

BrunoSan Intelligence Concierge scores 72 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 BrunoSan Intelligence Concierge MCP server expose?

BrunoSan Intelligence Concierge exposes 9 tools: discover_brunosan, list_intelligence_domains, inspect_domain, search_capabilities, inspect_tool, and 4 more. Their descriptions and schemas cost roughly 693 tokens of context every time the server is loaded.

### Does the BrunoSan Intelligence Concierge MCP server require authentication?

No. We connected to BrunoSan Intelligence Concierge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the BrunoSan Intelligence Concierge MCP server still maintained?

BrunoSan Intelligence Concierge is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://brunosan.de/mcp
- Changelog RSS feed: https://verifymcp.io/servers/de-brunosan-intelligence/brunosan.xml
- Changelog JSON feed: https://verifymcp.io/servers/de-brunosan-intelligence/brunosan.json
- HTML version of this page: https://verifymcp.io/servers/de-brunosan-intelligence/brunosan