Skip to content

BRAINIAC Physical & IoT Security MCP server

software.brainiac/physical-securitybrainiac.softwarestreamable-httpv1.0.1Scanned

Paid Physical & IoT Security API via x402. Unpaid tool calls return 402.

8 tools: 5 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 5 write, 3 read.
  • Reads private data · 3
  • Reads text others write · 8
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

5 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 Physical & IoT Security MCP server can do

The BRAINIAC Physical & IoT Security MCP server is published by brainiac.software, a domain the MCP Registry verified. It has 8 tools. It can create or change data (5 tools: physical-security_sensor-event-anomaly-detect, physical-security_door-access-pattern-detect, physical-security_access-tailgating-signal-detect, physical-security_camera-tampering-signal-detect and 1 more), but cannot delete data. 3 tools only read.

3 tools read private data (physical-security_perimeter-breach-signal-detect, physical-security_alarm-correlation-analyze and physical-security_iot-device-behavior-analyze); 8 tools bring in text other people can write (physical-security_sensor-event-anomaly-detect, physical-security_door-access-pattern-detect, physical-security_access-tailgating-signal-detect and 5 more).

The fixed checks matched 1 finding (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 5Claude Code: ask
  • physical-security_access-tailgating-signal-detectIdentify possible tailgating using caller-supplied access grants correlated with nearby motion/occupancy or unbadged second passages.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 possible tailgating using caller-supplied access grants correlated with nearby motion/occupancy or unbadged second passages. Not visually confirmed. Price $0.05 USDC. POST /api/v1/physical-security/access-tailgating-signal-detect. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Detect tailgating signals
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • physical-security_building-security-timelineGenerate a chronological security timeline from caller-supplied building events.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "generate": 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 "physical-security_building-security-timeline" 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 "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Generate a chronological security timeline from caller-supplied building events. Timeline entries are observed events, not confirmed incidents. Price $0.05 USDC. POST /api/v1/physical-security/building-security-timeline. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Build building-security timeline
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • physical-security_camera-tampering-signal-detectIdentify camera tampering indicators from caller-supplied telemetry (covered/moved/signal-loss).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 camera tampering indicators from caller-supplied telemetry (covered/moved/signal-loss). Scene content is not visually verified. Price $0.04 USDC. POST /api/v1/physical-security/camera-tampering-signal-detect. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Detect camera-tampering signals
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • physical-security_door-access-pattern-detectIdentify unusual access patterns from caller-supplied door-entry logs (denials, forced doors, held-open, after-hours).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 unusual access patterns from caller-supplied door-entry logs (denials, forced doors, held-open, after-hours). Not a confirmed intrusion. Price $0.04 USDC. POST /api/v1/physical-security/door-access-pattern-detect. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Detect unusual door-access patterns
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • physical-security_sensor-event-anomaly-detectDetect anomalies in caller-supplied sensor telemetry using thresholds, baselines, and local standard-deviation rules.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
    Detect anomalies in caller-supplied sensor telemetry using thresholds, baselines, and local standard-deviation rules. Anomalies are not confirmed physical incidents. Price $0.04 USDC. POST /api/v1/physical-security/sensor-event-anomaly-detect. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Detect sensor-event anomalies
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • physical-security_alarm-correlation-analyzeCorrelate alarms from multiple caller-supplied sensors into possible incident groups using time windows.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "physical-security_alarm-correlation-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
    Correlate alarms from multiple caller-supplied sensors into possible incident groups using time windows. Correlation is not confirmation of a physical incident. Price $0.05 USDC. POST /api/v1/physical-security/alarm-correlation-analyze. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Correlate multi-sensor alarms
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • physical-security_iot-device-behavior-analyzeIdentify unusual IoT device behaviour from caller-supplied telemetry (reporting gaps, outliers, unexpected reboot/config events).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "physical-security_iot-device-behavior-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
    Identify unusual IoT device behaviour from caller-supplied telemetry (reporting gaps, outliers, unexpected reboot/config events). Devices are never contacted or controlled. Price $0.04 USDC. POST /api/v1/physical-security/iot-device-behavior-analyze. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Analyze IoT device behaviour
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • physical-security_perimeter-breach-signal-detectAnalyze caller-supplied perimeter sensor events for possible breaches.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 caller-supplied perimeter sensor events for possible breaches. Multi-sensor alarms raise confidence; still not a confirmed physical breach. Price $0.04 USDC. POST /api/v1/physical-security/perimeter-breach-signal-detect. An unpaid call returns the x402 payment terms and does not run.

    Annotations the server declares

    • title: Detect perimeter-breach signals
    • 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:34 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
5
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 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.brainiac.software/mcp/physical-security: tools/list returned 8 tools to an anonymous client, including physical-security_sensor-event-anomaly-detect (write), physical-security_door-access-pattern-detect (write), physical-security_access-tailgating-signal-detect (write), physical-security_camera-tampering-signal-detect (write), physical-security_building-security-timeline (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "physical-security_building-security-timeline" 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 "generate": a word for a change.

    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 physical-security https://www.brainiac.software/mcp/physical-security
claude mcp add --transport http physical-security https://www.brainiac.software/mcp/physical-security

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__physical-security__physical-security_perimeter-breach-signal-detect",
      "mcp__physical-security__physical-security_alarm-correlation-analyze",
      "mcp__physical-security__physical-security_iot-device-behavior-analyze"
    ],
    "ask": [
      "mcp__physical-security__physical-security_sensor-event-anomaly-detect",
      "mcp__physical-security__physical-security_door-access-pattern-detect",
      "mcp__physical-security__physical-security_access-tailgating-signal-detect",
      "mcp__physical-security__physical-security_camera-tampering-signal-detect",
      "mcp__physical-security__physical-security_building-security-timeline"
    ],
    "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 physical-security. Review it before you use it.

Capability tags behind 8 rules
  • mcp__physical-security__physical-security_sensor-event-anomaly-detect untrusted-input
  • mcp__physical-security__physical-security_door-access-pattern-detect untrusted-input
  • mcp__physical-security__physical-security_access-tailgating-signal-detect untrusted-input
  • mcp__physical-security__physical-security_perimeter-breach-signal-detect private-data, untrusted-input
  • mcp__physical-security__physical-security_camera-tampering-signal-detect untrusted-input
  • mcp__physical-security__physical-security_alarm-correlation-analyze private-data, untrusted-input
  • mcp__physical-security__physical-security_iot-device-behavior-analyze private-data, untrusted-input
  • mcp__physical-security__physical-security_building-security-timeline 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/physical-security/verify?hash=72c20435fea1c5ad25fdd87411e267c4b674f9d0268cf0e363afaff4248ce788" | jq -e '.changed == false'

Pinned hash 72c20435fea1, 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/physical-security/changes.xml

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

Badge

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

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

BRAINIAC Physical & IoT Security MCP server: questions and answers

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

Is the BRAINIAC Physical & IoT Security MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 5 of which can change, send or delete something, and 1 finding 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 Physical & IoT Security 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 Physical & IoT Security 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 Physical & IoT Security MCP server have?

8 tools: 5 write, 3 read. physical-security_sensor-event-anomaly-detect, physical-security_door-access-pattern-detect, physical-security_access-tailgating-signal-detect, physical-security_camera-tampering-signal-detect, physical-security_building-security-timeline, physical-security_perimeter-breach-signal-detect, physical-security_alarm-correlation-analyze and physical-security_iot-device-behavior-analyze.

Does the BRAINIAC Physical & IoT Security MCP server need sign-in or OAuth?

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

Does the BRAINIAC Physical & IoT Security 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 Physical & IoT Security 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.