Skip to content

BRAINIAC Customer Support Intelligence MCP server

software.brainiac/customer-supportbrainiac.softwarestreamable-httpv1.0.1Scanned

Paid Customer Support Intelligence API via x402. Unpaid tool calls return 402.

8 tools: 6 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 6 write, 2 read.
  • Reads private data · 3
  • Reads text others write · 8
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the BRAINIAC Customer Support Intelligence MCP server can do

The BRAINIAC Customer Support Intelligence MCP server is published by brainiac.software, a domain the MCP Registry verified. It has 8 tools. It can create or change data (6 tools: customer-support_ticket-classify, customer-support_ticket-prioritize, customer-support_sentiment-analyze, customer-support_resolution-suggest and 2 more), but cannot delete data. 2 tools only read.

3 tools read private data (customer-support_ticket-deduplicate, customer-support_conversation-summarize and customer-support_sentiment-analyze); 8 tools bring in text other people can write (customer-support_ticket-classify, customer-support_ticket-prioritize, customer-support_ticket-deduplicate and 5 more).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 6Claude Code: ask
  • customer-support_escalation-detectFlag a ticket when the text contains a documented escalation phrase, the priority rules mark it critical, or the same email appears on three tickets in the request.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Flag a ticket when the text contains a documented escalation phrase, the priority rules mark it critical, or the same email appears on three tickets in the request. No escalation is performed. Price $0.04 USDC. POST /api/v1/customer-support/escalation-detect. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Detect escalation signals
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • customer-support_quality-auditCheck supplied replies for a resolution claim, a missing reply, or an email, amount, order, or policy that was not in the ticket.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check supplied replies for a resolution claim, a missing reply, or an email, amount, order, or policy that was not in the ticket. The audit does not confirm that any action happened. Price $0.12 USDC. POST /api/v1/customer-support/quality-audit. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Audit support reply quality
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • customer-support_resolution-suggestDraft a reply that quotes the customer and a supplied policy only when that policy shares a word with the ticket.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Draft a reply that quotes the customer and a supplied policy only when that policy shares a word with the ticket. The draft does not resolve the ticket or state an unsupplied policy. Price $0.05 USDC. POST /api/v1/customer-support/resolution-suggest. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Draft a support reply
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • customer-support_sentiment-analyzeLabel customer wording with a documented positive and negative word list.Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "customer-support_sentiment-analyze" says "analyze": a word for reading.
    • The description's first verb is "label": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • private-dataThe input names a file (input.file), and the tool reads: it reads files.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "customer-support_sentiment-analyze" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "customer-support_sentiment-analyze" says "analyze": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Label customer wording with a documented positive and negative word list. Text with no listed words stays unspecified. Price $0.03 USDC. POST /api/v1/customer-support/sentiment-analyze. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Analyze ticket sentiment
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • customer-support_ticket-classifyClassify supplied tickets into billing, access, outage, defect, delivery, or account when one documented keyword list has the most matches.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Classify supplied tickets into billing, access, outage, defect, delivery, or account when one documented keyword list has the most matches. A caller-supplied category list replaces that set. A tie stays unclassified. Price $0.03 USDC. POST /api/v1/customer-support/ticket-classify. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Classify support tickets
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • customer-support_ticket-prioritizeSet priority from a supplied severity and from documented urgency and business-impact phrases.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "set": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "customer-support_ticket-prioritize" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "set": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Set priority from a supplied severity and from documented urgency and business-impact phrases. A ticket with none of those signals stays unspecified. Price $0.04 USDC. POST /api/v1/customer-support/ticket-prioritize. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Prioritize support tickets
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • customer-support_conversation-summarizeRestate up to three customer sentences and quote supplied agent replies.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "customer-support_conversation-summarize" says "summarize": a word for reading.

    What it can reach

    • private-dataThe name "customer-support_conversation-summarize" says "summarize" and "conversation": it reads messages.
    • private-dataThe input names a file (input.file), and the tool reads: it reads files.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "customer-support_conversation-summarize" says "summarize" and "conversation": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "reply": it reads comments, which other people can write.
    Description, as the server wrote it
    Restate up to three customer sentences and quote supplied agent replies. The summary does not decide that a ticket was resolved. Price $0.04 USDC. POST /api/v1/customer-support/conversation-summarize. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Summarize a support conversation
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • customer-support_ticket-deduplicateFind duplicate tickets for the same email address and repeated wording across customers.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "find" and "email": it reads mail.
    • private-dataThe input names a file (input.file), and the tool reads: it reads files.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "customer-support_ticket-deduplicate" says "ticket": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "find" and "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    Find duplicate tickets for the same email address and repeated wording across customers. Each pair names the rule and a confidence level. Tickets are not merged. Price $0.05 USDC. POST /api/v1/customer-support/ticket-deduplicate. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Detect duplicate tickets
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:31 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.brainiac.software/mcp/customer-support: tools/list returned 8 tools to an anonymous client, including customer-support_ticket-classify (write), customer-support_ticket-prioritize (write), customer-support_sentiment-analyze (write), customer-support_resolution-suggest (write), customer-support_escalation-detect (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "customer-support_ticket-prioritize" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "set": a word for a change.

    What this check looks for
  • The server marks "customer-support_sentiment-analyze" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "customer-support_sentiment-analyze" says "analyze": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools8 changed.~8 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http customer-support https://www.brainiac.software/mcp/customer-support
claude mcp add --transport http customer-support https://www.brainiac.software/mcp/customer-support

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__customer-support__customer-support_ticket-deduplicate",
      "mcp__customer-support__customer-support_conversation-summarize"
    ],
    "ask": [
      "mcp__customer-support__customer-support_ticket-classify",
      "mcp__customer-support__customer-support_ticket-prioritize",
      "mcp__customer-support__customer-support_sentiment-analyze",
      "mcp__customer-support__customer-support_resolution-suggest",
      "mcp__customer-support__customer-support_escalation-detect",
      "mcp__customer-support__customer-support_quality-audit"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as customer-support. Review it before you use it.

Capability tags behind 8 rules
  • mcp__customer-support__customer-support_ticket-classify untrusted-input
  • mcp__customer-support__customer-support_ticket-prioritize untrusted-input
  • mcp__customer-support__customer-support_ticket-deduplicate private-data, untrusted-input
  • mcp__customer-support__customer-support_conversation-summarize private-data, untrusted-input
  • mcp__customer-support__customer-support_sentiment-analyze private-data, untrusted-input
  • mcp__customer-support__customer-support_resolution-suggest untrusted-input
  • mcp__customer-support__customer-support_escalation-detect untrusted-input
  • mcp__customer-support__customer-support_quality-audit untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/software.brainiac/customer-support/verify?hash=111a68e510d00fd30eca033c59dc661c13a2cdff80aef0084874560366cfd726" | jq -e '.changed == false'

Pinned hash 111a68e510d0, from Nov 20, 2026, 01:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/software.brainiac/customer-support/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for software.brainiac/customer-support
[![Anlyon Radar](https://radar.anlyon.com/badge/software.brainiac/customer-support.svg)](https://radar.anlyon.com/servers/software.brainiac/customer-support)

Source: MCP Registry. Synced Nov 20, 2026, 01:18 UTC.

BRAINIAC Customer Support Intelligence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BRAINIAC Customer Support Intelligence MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the BRAINIAC Customer Support Intelligence MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the BRAINIAC Customer Support Intelligence MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the BRAINIAC Customer Support Intelligence MCP server have?

8 tools: 6 write, 2 read. customer-support_ticket-classify, customer-support_ticket-prioritize, customer-support_sentiment-analyze, customer-support_resolution-suggest, customer-support_escalation-detect, customer-support_quality-audit, customer-support_ticket-deduplicate and customer-support_conversation-summarize.

Does the BRAINIAC Customer Support Intelligence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the BRAINIAC Customer Support Intelligence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the BRAINIAC Customer Support Intelligence MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.