three_failures

MCP server · GitHub · ★ 9 · graded 2026-10-19Source linked

A runnable Docker Compose lab demonstrating the three structural failures of observe-and-detect agent governance. No API keys, no cloud accounts, 60 seconds to run.

No outside reports on file

three_failures is distributed via GitHub (Behavry-ai/three_failures); review its source code, dependencies, and requested permissions before use.

Based on public adoption and transparency signals as of Oct 19, 2026. Our opinion, not a code audit or security guarantee.

Was this verdict for Three Failures helpful?

What it can access

  • Local filesNo local folder access notedLOW
  • Command executionNo shell command runner notedLOW
  • Network reachLocal or standard API callsLOW
  • CredentialsNo API token requiredLOW
  • Package sourceGitHub (Behavry-ai/three_failures)PUBLIC

Inferred from this listing’s public package details and description. Check the project’s source before installing.

Install

No npm or PyPI package is listed. Install from source: github.com/Behavry-ai/three_failures ↗

All setup options ↓

About Three Failures

Three Failures is an MCP server focused on Developer tools and Files & documents: A runnable Docker Compose lab demonstrating the three structural failures of observe-and-detect agent governance. No API keys, no cloud accounts, 60 seconds to run.

It is hosted on GitHub at Behavry-ai/three_failures (9 GitHub stars). Based on its public metadata, it operates with standard local or API scope without broad shell execution flags noted.

Setup

These use the package this listing points to. Check the project’s own instructions before running anything.

No npm or PyPI package is listed for this MCP server. Source code and setup steps: github.com/Behavry-ai/three_failures.

Why this grade

DD — High risk signals

Signal-based grade (1/7 points): public source code. This reflects adoption and transparency, not a code review.

Popularity and upkeep

14/100
GitHub stars
9
Listing last refreshed
2026-10-29

These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.

Security reports

No reports found for this package in our research (last checked 2026-10-30).

Check a specific version →

Risks to watch for

  • Dependency & version pinning: Distributed via GitHub (Behavry-ai/three_failures). Pin an exact release version or commit SHA rather than floating tags so upstream updates are reviewed first.

How to lower the risk

Least-privilege permissions

  • Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
  • Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.

Network isolation

  • Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
  • If your IT team can, limit which websites and services it is allowed to contact.

Monitoring

  • Check its activity history or logs weekly at first, and look at what it changed or sent.
  • Turn on alerts for new logins or unusual usage on any account it connects to.

Red flags to watch for

  • It asks for more access than its job requires, or prompts you to paste passwords.
  • It suddenly updates with new owners, or starts contacting unfamiliar websites.

Questions

How do I install Three Failures?

Three Failures does not publish a standalone npm or PyPI package. Clone or follow the setup instructions in its source repository at github.com/Behavry-ai/three_failures.

Are there security reports about Three Failures?

No reports found for this package in our research (last checked 2026-10-30). Three Failures currently holds Grade D (High risk signals) based on public adoption and transparency signals. Review the permissions and source repository before granting access to local files, shell commands, or API keys.

Is Three Failures actively maintained?

Three Failures has 9 GitHub stars. Our directory data was last refreshed on 2026-10-29. Check recent commit activity, release tags, and open issues at github.com/Behavry-ai/three_failures before pinning it in production.

What are alternatives to Three Failures?

You can compare Three Failures side by side with other Docker MCP servers in the Related tools section on this page, or use the Compare tool on AgentArmorHQ.

README badge and team notes

Maintain or use Three Failures? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.

AgentArmorHQ Risk Grade D for Three Failures

GitHub README Markdown:

markdown
[![AgentArmorHQ Risk Grade for Three Failures](https://agentarmorhq.com/api/badge/behavry-ai-three-failures)](https://agentarmorhq.com/skills/behavry-ai-three-failures)

HTML embed:

html
<a href="https://agentarmorhq.com/skills/behavry-ai-three-failures"><img src="https://agentarmorhq.com/api/badge/behavry-ai-three-failures" alt="AgentArmorHQ Risk Grade for Three Failures" height="20" /></a>

Terminal check:

terminal
curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "behavry-ai-three-failures"

Share with your security lead

Need sign-off to use three_failures? Copy this note for Slack, a ticket or a pull request.

### AgentArmorHQ Security Review Memo: three_failures
- **Listing URL:** https://agentarmorhq.com/skills/behavry-ai-three-failures
- **Type:** App connector
- **Risk Grade:** Grade D (High risk signals)
- **Outside Security Advisories on File:** 0
- **Public Adoption:** 9 GitHub stars

#### Permission & Blast-Radius Signals
- **Local files:** No local folder access noted
- **Command execution:** No shell command runner noted
- **Network reach:** Local or standard API calls
- **Credentials:** No API token required
- **Package source:** GitHub (Behavry-ai/three_failures)

#### Recommended Hardened Setup
- **Source Repo:** https://github.com/Behavry-ai/three_failures
- **Controls:** Pin an exact version in `.mcp.json`, scope access to a single workspace folder, and use a least-privilege read-only token where supported.

_Based on public adoption and transparency signals as of Oct 19, 2026. Our opinion, not a code audit or security guarantee._

Key facts

Type
App connector
Publisher
Behavry-ai
Source code
github.com/Behavry-ai/three_failures
Est. context load
~550 tokens / turn (~3 tool schemas, 0.27% of 200k context)
Popularity
9 GitHub stars
Last updated
2026-10-29
Last graded
2026-10-19

Community

Discussions for Three Failures

Ask questions or share configuration tips. Governed by our Community Rules & Terms.

No posts match this filter yet.

Be the first to ask a question or share a working tip.

Was this listing for Three Failures helpful?

Check before you install, in Claude

Your assistant answers Block, Review or No known issues for any package before it installs it.

Get this check inside Claude