mcp-behave
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
mcp-behave is a runtime behavioral auditor and security scanner for MCP servers. It verifies whether an MCP server's actual runtime behavior matches what it declares.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_serverB | Run a runtime behavioral audit on an MCP server. Exercises tools, resources, and prompts using canary inputs, captures system calls (network, files, subprocesses), and detects undeclared behaviors or manifest rug-pulls. |
| inspect_manifestB | Inspect an MCP server's declared capabilities (tools, resources, prompts) without executing tool actions or tracing syscalls. Also checks for manifest rug-pulls against prior recorded runs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct modes: inspect_manifest is static, read-only manifest inspection, while audit_server performs runtime execution and syscall tracing. Although both mention rug-pull detection, the descriptions make the static-vs-runtime boundary explicit.
Both names follow a consistent snake_case verb_noun pattern (inspect_manifest, audit_server). The verbs accurately reflect each tool's action.
Two tools is thin for the server's scope, though each covers a meaningful analysis mode (static and runtime). Additional tools for managing or comparing audit runs would make the set feel more complete.
The surface covers the core static and dynamic auditing workflows, including rug-pull detection. Minor gaps exist around retrieving, listing, or comparing prior audit results and managing baselines.