BrunoSan Intelligence Concierge

endpoint

https://brunosan.de/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is BrunoSan Intelligence Concierge live?

Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.

Is BrunoSan Intelligence Concierge free to use?

Yes — the hub reached it with no key and no payment.

What tools does BrunoSan Intelligence Concierge have?

9 tools: get_connection_info, inspect_domain, inspect_tool, plan_intelligence_route, discover_brunosan, search_capabilities, get_access_options, list_intelligence_domains, ….

Is BrunoSan Intelligence Concierge safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• get_access_options reads open 9h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "get_access_optionsArguments",
    "properties": {}
  }

  arguments 5 lines copy
• list_intelligence_domains reads open 9h ago

  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.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "title": "list_intelligence_domainsArguments",
    "properties": {
      "include_live_tool_counts": {
        "type": "boolean",
        "title": "Include Live Tool Counts",
        "default": false,
        "description": "If true, probe each canonical vertical MCP and include current tool counts."
      }
    }
  }

  arguments 12 lines copy
• get_intelligence_status reads open 9h ago

  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.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "title": "get_intelligence_statusArguments",
    "properties": {
      "refresh": {
        "type": "boolean",
        "title": "Refresh",
        "default": false,
        "description": "Request a fresh tools/list probe. Normal calls use the short-lived cache to protect vertical MCPs."
      }
    }
  }

  arguments 12 lines copy
• get_connection_info reads unknown 24h ago

  Return canonical connection details without guessing client-specific config.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "title": "get_connection_infoArguments",
    "required": [
      "domain"
    ],
    "properties": {
      "domain": {
        "type": "string",
        "title": "Domain",
        "description": "BrunoSan domain id/name whose canonical MCP connection should be returned."
      }
    }
  }

  arguments 14 lines copy
• inspect_domain reads unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "title": "inspect_domainArguments",
    "required": [
      "domain"
    ],
    "properties": {
      "domain": {
        "type": "string",
        "title": "Domain",
        "description": "Canonical domain id or name, e.g. cyber, arxiv, AI News, regulatory, lens."
      },
      "include_tools": {
        "type": "boolean",
        "title": "Include Tools",
        "default": true,
        "description": "Include the live tools/list inventory and input schemas from the vertical MCP."
      }
    }
  }

  arguments 20 lines copy
• inspect_tool reads unknown never probed

  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.

  mcp-tool

  123456789101112131415161718192021

  {
    "type": "object",
    "title": "inspect_toolArguments",
    "required": [
      "tool_name"
    ],
    "properties": {
      "domain": {
        "type": "string",
        "title": "Domain",
        "default": "",
        "description": "Optional BrunoSan domain id/name to restrict the lookup."
      },
      "tool_name": {
        "type": "string",
        "title": "Tool Name",
        "minLength": 1,
        "description": "Exact or partial MCP tool name to inspect."
      }
    }
  }

  arguments 21 lines copy
• plan_intelligence_route reads unknown never probed

  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.

  mcp-tool

  12345678910111213141516171819202122

  {
    "type": "object",
    "title": "plan_intelligence_routeArguments",
    "required": [
      "goal"
    ],
    "properties": {
      "goal": {
        "type": "string",
        "title": "Goal",
        "minLength": 3,
        "description": "Research or monitoring goal that may require one or several BrunoSan verticals."
      },
      "max_domains": {
        "type": "integer",
        "title": "Max Domains",
        "default": 3,
        "maximum": 5,
        "minimum": 1
      }
    }
  }

  arguments 22 lines copy
• discover_brunosan reads unknown never probed

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "title": "discover_brunosanArguments",
    "properties": {}
  }

  arguments 5 lines copy
• search_capabilities reads unknown 24h ago

  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.

  mcp-tool

  12345678910111213141516171819202122

  {
    "type": "object",
    "title": "search_capabilitiesArguments",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 8,
        "maximum": 12,
        "minimum": 1
      },
      "query": {
        "type": "string",
        "title": "Query",
        "minLength": 2,
        "description": "Natural-language goal or capability, e.g. 'critical CVEs', 'citation network', 'EU AI Act sanctions'."
      }
    }
  }

  arguments 22 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

• arxiv.mcp.brunosan.de BrunoSan ArXiv Intelligence mcp · 16 tools