BrunoSan Intelligence Concierge
REMOTE · BRUNOSAN.DE · SCANNED SEP 27
Discovery MCP for 11 intelligence domains plus LENS with live tools, routing and endpoints.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 894 tokens (~74/item across 12 items; 9 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · brunosan.de
claude mcp add --transport http de-brunosan-intelligence 'https://brunosan.de/mcp'
{
"mcpServers": {
"de-brunosan-intelligence": {
"url": "https://brunosan.de/mcp"
}
}
} {
"servers": {
"de-brunosan-intelligence": {
"type": "http",
"url": "https://brunosan.de/mcp"
}
}
} [mcp_servers.de-brunosan-intelligence] url = "https://brunosan.de/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"de-brunosan-intelligence": {
"type": "remote",
"url": "https://brunosan.de/mcp",
"enabled": true
}
}
} openclaw mcp add de-brunosan-intelligence --url 'https://brunosan.de/mcp' --transport streamable-http
mcp_servers:
de-brunosan-intelligence:
url: "https://brunosan.de/mcp" {
"McpServers": {
"de-brunosan-intelligence": {
"Transport": "http",
"Url": "https://brunosan.de/mcp"
}
}
} assistant mcp add de-brunosan-intelligence -t streamable-http -u 'https://brunosan.de/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 +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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 15 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Sept 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://brunosan.de/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=brunosan.de | CN=YR2,O=Let's Encrypt,C=US | 22 Aug 2026 | 20 Nov 2026 | RSA 4096 | SHA256-RSA | 572db0943e726c2bb5e9b0187fe0cff8439 |
| SANs: brunosan.de, www.brunosan.de | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of brunosan.de. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| de. | present | 26755 | 8 | Verified |
| brunosan.de. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://brunosan.de/mcp | Verified | 200 | |
| http (plaintext) | http://brunosan.de/mcp | HTTPS enforced | 301 | https://brunosan.de/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
discover_brunosan ~79
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
get_access_options ~46
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 present but exposes no named parameters.
No output schema declared.
No examples provided.
get_connection_info ~38
Return canonical connection details without guessing client-specific config.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | BrunoSan domain id/name whose canonical MCP connection should be returned. |
No output schema declared.
No examples provided.
get_intelligence_status ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| refresh | boolean | – | Request a fresh tools/list probe. Normal calls use the short-lived cache to protect vertical MCPs. |
No output schema declared.
No examples provided.
inspect_domain ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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. |
No output schema declared.
No examples provided.
inspect_tool ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Optional BrunoSan domain id/name to restrict the lookup. |
| tool_name | string | yes | Exact or partial MCP tool name to inspect. |
No output schema declared.
No examples provided.
list_intelligence_domains ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_live_tool_counts | boolean | – | If true, probe each canonical vertical MCP and include current tool counts. |
No output schema declared.
No examples provided.
plan_intelligence_route ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | yes | Research or monitoring goal that may require one or several BrunoSan verticals. |
| max_domains | integer | – | – |
No output schema declared.
No examples provided.
search_capabilities ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Natural-language goal or capability, e.g. 'critical CVEs', 'citation network', 'EU AI Act sanctions'. |
No output schema declared.
No examples provided.
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.