Skip to content
MCP server

MCP Behave

Runtime security auditor that traces what an MCP server actually does, for vetting

Runs locally
Install
Pricing
Open source
Platforms
CLI, Linux, macOS
Runs
Locally
Version
0.3.5
Listing updated
today

Similar MCP servers

About MCP Behave

MCP Behave is an open-source MCP server for security. It runs locally on your machine and is started by your AI client.

The README says mcp-behave runs an MCP server under a system call tracer (a macOS dylib, a Linux LD_PRELOAD library, or strace), then calls every tool, resource and prompt the server advertises. It records network connections, sensitive file reads and subprocess launches, and checks tool metadata and outputs for hidden Unicode, ANSI escapes, prompt-injection phrasing and Markdown image exfiltration.

The project positions itself against static scanners that only read tool descriptions. Its pitch is that observed runtime behaviour is what matters, so a server that describes itself as local but opens sockets gets flagged. Findings are reported as observations, and a scorecard, SARIF and JSON output make it usable in CI pipelines.

Beyond live audits, it offers an offline linter for manifest files, a manifest-hash rug-pull check, a fuzzing mode for tool arguments, and a scan of local AI client configurations for plaintext secrets and over-broad mounts. It is aimed at developers and security reviewers who install MCP servers and want to check them before use.

Install

Run in a terminal

claude mcp add mcp-behave -- npx -y mcp-behave

Add to claude_desktop_config.json

{
  "mcpServers": {
    "mcp-behave": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-behave"
      ]
    }
  }
}
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp-behave": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-behave"
      ]
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "mcp-behave": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-behave"
      ]
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "mcp-behave": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-behave"
      ]
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "mcp-behave": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-behave"
      ]
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Tools this server provides (3)

Taken from the project documentation; the running server may differ.

audit_server
Probes and dynamically audits another MCP server's behavioral footprint.
inspect_manifest
Safely fetches and inspects advertised tools, resources, and prompts, and checks for rug-pulls.
scan_client_configs
Scans local AI client configurations to discover installed MCP servers and audit their security posture.

What it does

Syscall-level runtime tracing
Wraps the server process with a platform tracer to record network, file and subprocess activity during tool calls.
Metadata injection checks
Scans tool names, descriptions and prompts for zero-width characters, BiDi overrides, ANSI escapes and injection phrasing.
Output exfiltration detection
Flags external Markdown or HTML image links in tool responses that could leak data when rendered.
Rug-pull detection
Stores manifest hashes between runs and alerts when advertised tools or descriptions change silently.
Offline manifest linter
Checks static tool definitions against a rule catalog without starting the server.
CI-ready output
Provides JSON and SARIF output, a 0-100 scorecard and exit codes keyed to a severity threshold.

Good for

  • Vetting a third-party MCP server before connecting it to an AI client
  • Checking whether a server makes network calls it does not declare
  • Linting tool schemas in a CI pipeline before release
  • Auditing MCP servers already configured in Claude Desktop or Cursor

Pricing

Open source

MIT licensed; free to use and self-host.

MCP Behave FAQ

How is it installed?

The README lists pip and npm installs, plus zero-install runs via npx or uvx.

Does it work on Windows?

The README describes native tracers for macOS and Linux, and Docker for macOS and Windows hosts; it does not describe a native Windows tracer.

Does it run remote servers?

Remote SSE and streamable-HTTP servers get manifest analysis only, because client-side process tracing is not possible there.

Is MCP Behave free?

Yes. MCP Behave is open source, so you can use and self-host it for free.

How do I add MCP Behave to Claude Code?

Run this command in your terminal: claude mcp add mcp-behave -- npx -y mcp-behave

What are the best alternatives to MCP Behave?

The closest alternatives to MCP Behave are mcp-audit, MCPSense, mcp-audit, MCP Tool Poisoning Scanner and mcpsteward.

Where this comes from

  • Description: written from the project's README and its MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers