Is the Brunosan Intelligence MCP server down?

mcp-registry/de.brunosan/intelligence · v1.28.1

healthy
Last checked 2026-10-25 09:42 UTC · handshake 504ms

As of 2026-10-25 09:42 UTC, the Brunosan Intelligence MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
100%
checks observed
4,747
outages (90d)
1
tools
9

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

Install Brunosan Intelligence MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http brunosan-intelligence-mcp-server https://brunosan.de/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (80/100)

B (80/100): 0 error(s), 2 warning(s) across 9 tool(s); ~1,399 tokens of tool definitions.
Scores higher than 19% of 15,682 MCP servers Glimind has audited.
Its tool list costs an agent ~1,399 tokens per session — lighter than 65% of servers.
78 → 80 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions74
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

9 of 9 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: discover_brunosan, get_access_options, get_connection_info, get_intelligence_status, inspect_domain and 4 more

2 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: plan_intelligence_route, search_capabilities

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fde.brunosan%2Fintelligence/fixes

get_access_options 1 change
{
  "name": "get_access_options",
  "description": "Return current BrunoSan access and pricing from the shared pricing manifest.\n\n    No price is embedded in this server. Unknown or absent manifest values stay\n    absent rather than being estimated.\n    ",
  "inputSchema": {
    "type": "object",
    "title": "get_access_optionsArguments",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_connection_info 1 change
{
  "name": "get_connection_info",
  "description": "Return canonical connection details without guessing client-specific config.",
  "inputSchema": {
    "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."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_intelligence_status 1 change
{
  "name": "get_intelligence_status",
  "description": "Check whether each canonical BrunoSan MCP currently initializes and lists tools.\n\n    This is a capability-plane health check only; it does not execute protected\n    intelligence tools or make claims about underlying data freshness.\n    ",
  "inputSchema": {
    "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."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/de.brunosan/intelligence"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/de.brunosan/intelligence"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fde.brunosan%2Fintelligence.svg)](https://glimind.com/server/mcp-registry%2Fde.brunosan%2Fintelligence?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fde.brunosan%2Fintelligence?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fde.brunosan%2Fintelligence.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fde.brunosan%2Fintelligence.svg
   :target: https://glimind.com/server/mcp-registry%2Fde.brunosan%2Fintelligence?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:34927ba56615a1f0…, first seen 2026-10-17, included at leaf 15175 of 65,214. Version history · verify what your client received.

Tools (9)

Compare: most reliable knowledge servers · most reliable devops servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Brunosan Intelligence MCP server down right now?

As of 2026-10-25 09:42 UTC, the Brunosan Intelligence MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

How many tools does Brunosan Intelligence MCP server provide?

Brunosan Intelligence MCP server advertises 9 tools, including discover_brunosan, get_access_options, get_connection_info, get_intelligence_status, inspect_domain.

How do I install Brunosan Intelligence MCP server?

Point your MCP client at this streamable-http endpoint: https://brunosan.de/mcp

Is the Brunosan Intelligence MCP server safe to connect to an AI agent?

Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Brunosan Intelligence MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve