BRAINIAC Threat Intelligence & Public Signals MCP server
software.brainiac/threat-intelligencebrainiac.softwarestreamable-httpv1.0.1Scanned
Paid Threat Intelligence & Public Signals API via x402. Unpaid tool calls return 402.
8 tools: 6 change things and 2 only read.
- Reads private data · 2
- Reads text others write · 8
- Can send data out · 0
- No 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.
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 Threat Intelligence & Public Signals MCP server can do
The BRAINIAC Threat Intelligence & Public Signals 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: threat-intelligence_public-threat-feed-aggregate, threat-intelligence_ioc-context-enrich, threat-intelligence_certificate-threat-cluster, threat-intelligence_typosquatting-domain-detect and 2 more), but cannot delete data. 2 tools only read.
2 tools read private data (threat-intelligence_domain-threat-history and threat-intelligence_exposed-service-risk-analyze); 8 tools bring in text other people can write (threat-intelligence_public-threat-feed-aggregate, threat-intelligence_ioc-context-enrich, threat-intelligence_domain-threat-history and 5 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
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
threat-intelligence_certificate-threat-clusterIdentify relationships between domains using caller-supplied certificates and optional public crt.sh data.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 Identify relationships between domains using caller-supplied certificates and optional public crt.sh data. Shared certificate attributes are linkage evidence, not confirmed abuse. Price $0.04 USDC. POST /api/v1/threat-intelligence/certificate-threat-cluster. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Cluster certificate relationships
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
threat-intelligence_ioc-context-enrichEnrich supplied IPs, domains, URLs, and hashes using caller context plus optional public DNS/feeds.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 Enrich supplied IPs, domains, URLs, and hashes using caller context plus optional public DNS/feeds. A single weak feed hit is never classified as malicious. Price $0.04 USDC. POST /api/v1/threat-intelligence/ioc-context-enrich. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Enrich IoC context
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
threat-intelligence_phishing-infrastructure-clusterGroup related phishing domains and infrastructure using caller evidence and optional public phishing feeds.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 Group related phishing domains and infrastructure using caller evidence and optional public phishing feeds. Clusters are relationship hypotheses, not confirmed campaigns. Price $0.04 USDC. POST /api/v1/threat-intelligence/phishing-infrastructure-cluster. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Cluster phishing infrastructure
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
threat-intelligence_public-threat-feed-aggregateAggregate caller-supplied and verified key-free public threat feeds (CISA KEV, OpenPhish, capped PhishTank).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 Aggregate caller-supplied and verified key-free public threat feeds (CISA KEV, OpenPhish, capped PhishTank). URLhaus/ThreatFox require auth and are not queried. Feed hits are not confirmed malice. Price $0.05 USDC. POST /api/v1/threat-intelligence/public-threat-feed-aggregate. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Aggregate public threat feeds
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
threat-intelligence_threat-indicator-confidence-scoreCalculate explainable confidence scores for supplied threat indicators using multi-source corroboration.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 Calculate explainable confidence scores for supplied threat indicators using multi-source corroboration. Single weak signals are capped and never claimed as confirmed malice. Price $0.03 USDC. POST /api/v1/threat-intelligence/threat-indicator-confidence-score. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Score threat-indicator confidence
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
threat-intelligence_typosquatting-domain-detectIdentify domains resembling supplied brand or company domains using local string/keyboard heuristics.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 Identify domains resembling supplied brand or company domains using local string/keyboard heuristics. Resemblance alone is not confirmed phishing. Price $0.03 USDC. POST /api/v1/threat-intelligence/typosquatting-domain-detect. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Detect typosquat domains
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 2Show 2 read-only tools
threat-intelligence_domain-threat-historyAnalyze publicly accessible domain history and DNS/RDAP context from caller fields and optional key-free public lookups.Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "analyze": a word for reading.
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.
Description, as the server wrote it Analyze publicly accessible domain history and DNS/RDAP context from caller fields and optional key-free public lookups. History attributes alone are not malice. Price $0.04 USDC. POST /api/v1/threat-intelligence/domain-threat-history. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Analyze domain threat history
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
threat-intelligence_exposed-service-risk-analyzeAnalyze caller-supplied external service inventory and scan results for exposure risk.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "threat-intelligence_exposed-service-risk-analyze" says "analyze": a word for reading.
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.
Description, as the server wrote it Analyze caller-supplied external service inventory and scan results for exposure risk. Never initiates intrusive network scanning. Price $0.04 USDC. POST /api/v1/threat-intelligence/exposed-service-risk-analyze. An unpaid call returns the x402 payment terms and does not run.
Annotations the server declares
- title: Analyze exposed service risk
- 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 data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write8
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- threat-intelligence_certificate-threat-cluster
- threat-intelligence_domain-threat-history
- threat-intelligence_exposed-service-risk-analyze
- threat-intelligence_ioc-context-enrich
- threat-intelligence_phishing-infrastructure-cluster
- threat-intelligence_public-threat-feed-aggregate
- threat-intelligence_threat-indicator-confidence-score
- threat-intelligence_typosquatting-domain-detect
- 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.
Looked at Nov 20, 2026, 19:35 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.
What this check looks forMatched text
https://www.brainiac.software/mcp/threat-intelligence: tools/list returned 8 tools to an anonymous client, including threat-intelligence_public-threat-feed-aggregate (write), threat-intelligence_ioc-context-enrich (write), threat-intelligence_certificate-threat-cluster (write), threat-intelligence_typosquatting-domain-detect (write), threat-intelligence_phishing-infrastructure-cluster (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools8 changed.~8 changedView diff
- Changed:threat-intelligence_certificate-threat-clusterChanges thingsinputSchemaannotations
- Changed:threat-intelligence_domain-threat-historyOnly readsinputSchemaannotations
- Changed:threat-intelligence_exposed-service-risk-analyzeOnly readsinputSchemaannotations
- Changed:threat-intelligence_ioc-context-enrichChanges thingsinputSchemaannotations
- Changed:threat-intelligence_phishing-infrastructure-clusterChanges thingsinputSchemaannotations
- Changed:threat-intelligence_public-threat-feed-aggregateChanges thingsinputSchemaannotations
- Changed:threat-intelligence_threat-indicator-confidence-scoreChanges thingsinputSchemaannotations
- Changed:threat-intelligence_typosquatting-domain-detectChanges thingsinputSchemaannotations
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http threat-intelligence https://www.brainiac.software/mcp/threat-intelligenceclaude mcp add --transport http threat-intelligence https://www.brainiac.software/mcp/threat-intelligenceRun 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.
{
"permissions": {
"allow": [
"mcp__threat-intelligence__threat-intelligence_domain-threat-history",
"mcp__threat-intelligence__threat-intelligence_exposed-service-risk-analyze"
],
"ask": [
"mcp__threat-intelligence__threat-intelligence_public-threat-feed-aggregate",
"mcp__threat-intelligence__threat-intelligence_ioc-context-enrich",
"mcp__threat-intelligence__threat-intelligence_certificate-threat-cluster",
"mcp__threat-intelligence__threat-intelligence_typosquatting-domain-detect",
"mcp__threat-intelligence__threat-intelligence_phishing-infrastructure-cluster",
"mcp__threat-intelligence__threat-intelligence_threat-indicator-confidence-score"
],
"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 threat-intelligence. Review it before you use it.
Capability tags behind 8 rules
- mcp__threat-intelligence__threat-intelligence_public-threat-feed-aggregate untrusted-input
- mcp__threat-intelligence__threat-intelligence_ioc-context-enrich untrusted-input
- mcp__threat-intelligence__threat-intelligence_domain-threat-history private-data, untrusted-input
- mcp__threat-intelligence__threat-intelligence_certificate-threat-cluster untrusted-input
- mcp__threat-intelligence__threat-intelligence_typosquatting-domain-detect untrusted-input
- mcp__threat-intelligence__threat-intelligence_phishing-infrastructure-cluster untrusted-input
- mcp__threat-intelligence__threat-intelligence_exposed-service-risk-analyze private-data, untrusted-input
- mcp__threat-intelligence__threat-intelligence_threat-indicator-confidence-score 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/threat-intelligence/verify?hash=57142b3ca0edd5add46f43f604946d58c717197e9eaef78a70525e5fcef80873" | jq -e '.changed == false'Pinned hash 57142b3ca0ed, from Nov 20, 2026, 01:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/software.brainiac/threat-intelligence/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/software.brainiac/threat-intelligence)Source: MCP Registry. Synced Nov 20, 2026, 01:18 UTC.
BRAINIAC Threat Intelligence & Public Signals MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BRAINIAC Threat Intelligence & Public Signals MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 0 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 Threat Intelligence & Public Signals 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 Threat Intelligence & Public Signals 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 Threat Intelligence & Public Signals MCP server have?
- 8 tools: 6 write, 2 read. threat-intelligence_public-threat-feed-aggregate, threat-intelligence_ioc-context-enrich, threat-intelligence_certificate-threat-cluster, threat-intelligence_typosquatting-domain-detect, threat-intelligence_phishing-infrastructure-cluster, threat-intelligence_threat-indicator-confidence-score, threat-intelligence_domain-threat-history and threat-intelligence_exposed-service-risk-analyze.
Does the BRAINIAC Threat Intelligence & Public Signals MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BRAINIAC Threat Intelligence & Public Signals 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 Threat Intelligence & Public Signals 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.