behave
MCPB · BEHAVE_0.1.6_LINUX_AMD64.MCPB · 4 COMPONENTS
Record how any CLI behaves and check that a rewrite behaves the same (golden tests).
Last scanned (19 hours ago)
Scores higher than 77% of MCPB servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 592 tokens (~118/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "behave_exec" implies "exec" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +2
- Stability: unverified → 0.10 ▲ functional
- 14 Oct 26 38
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Analysed mcpb/https://github.com/emirmrkaljevic/behave/releases/download/v0.1.6/behave_0.1.6_linux_amd64.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
behave_add_case ~78
Add one case to a spec and record the original command's behavior for it.
| Name | Type | Req | Description |
|---|---|---|---|
| args | null|array | yes | arguments |
| dir | string | yes | spec directory |
| files | object | – | input files, name to content |
| name | string | – | short description of the case |
| stdin | string | – | standard input |
| Name | Type | Req | Description |
|---|---|---|---|
| args | null|array | yes | – |
| exit | integer | yes | – |
| file | string | yes | – |
| flaky | boolean | – | – |
| name | string | yes | – |
| stderr | string | – | – |
| stdout | string | – | – |
No examples provided.
behave_diff ~123
Replay a spec against an implementation (the recorded command if impl is empty) and report which cases and flags behave differently.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | yes | spec directory |
| ignore_exit | boolean | – | do not compare exit codes |
| ignore_stderr | boolean | – | do not compare stderr |
| impl | string | – | implementation to test; empty replays the recorded command |
| max_failures | integer | – | failing cases to include in detail (default 10) |
| skip_tags | null|array | – | skip cases with these tags, e.g. meta |
| Name | Type | Req | Description |
|---|---|---|---|
| by_field | object | yes | – |
| errors | integer | yes | – |
| fail | integer | yes | – |
| failures | null|array | yes | – |
| pass | integer | yes | – |
| skip | integer | yes | – |
| summary | string | yes | – |
No examples provided.
behave_exec ~102
Run a command once in an isolated temp directory and return its exit code, stdout and stderr. Nothing is saved. Use it to explore a tool.
| Name | Type | Req | Description |
|---|---|---|---|
| args | null|array | – | arguments |
| command | string | yes | program name or path |
| files | object | – | files to create in the work dir, name to content |
| stdin | string | – | standard input |
| timeout_ms | integer | – | timeout in milliseconds (default 5000) |
| Name | Type | Req | Description |
|---|---|---|---|
| elapsed_ms | integer | yes | – |
| exit | integer | yes | – |
| stderr | string | yes | – |
| stdout | string | yes | – |
| timed_out | boolean | – | – |
No examples provided.
behave_list_cases ~54
List the cases in a spec with their arguments and recorded exit codes.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | yes | spec directory |
| tag | string | – | only cases with this tag, e.g. flag:--sort or manual |
| Name | Type | Req | Description |
|---|---|---|---|
| cases | null|array | yes | – |
| command | string | yes | – |
| total | integer | yes | – |
No examples provided.
behave_probe ~170
Read a command's --help/man page, generate test cases (flags, flag pairs, edge-case stdin, files, error paths) and record the command's behavior into a new spec directory.
| Name | Type | Req | Description |
|---|---|---|---|
| args | null|array | – | positional argument samples, e.g. jq filters |
| command | string | yes | program to probe |
| dir | string | yes | spec directory to create |
| inputs | string | – | stdin samples: text, json, both or auto (default) |
| max | integer | – | maximum number of cases (default 500) |
| sample_files | string | – | create a small sample directory tree in each work dir: auto (default; on when help mentions the current directory or recursion), on, off |
| skip_flags | null|array | – | flags never to use |
| Name | Type | Req | Description |
|---|---|---|---|
| cases | integer | yes | – |
| dir | string | yes | – |
| flags | null|array | yes | – |
| flaky | integer | yes | – |
| timed_out | integer | yes | – |
No examples provided.
How do I install the behave MCP server?
behave ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 221ed952e2a474ed6c4113fcd95fe8d2eb197e2c05e3aa40df9e0e15d92131a6; the commands to do that are on this page. If it does not match, do not open it.
mcpb · behave_0.1.6_linux_amd64.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
221ed952e2a474ed6c4113fcd95fe8d2eb197e2c05e3aa40df9e0e15d92131a6
macOS / Linux
echo "221ed952e2a474ed6c4113fcd95fe8d2eb197e2c05e3aa40df9e0e15d92131a6 behave_0.1.6_linux_amd64.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\behave_0.1.6_linux_amd64.mcpb).Hash -eq "221ed952e2a474ed6c4113fcd95fe8d2eb197e2c05e3aa40df9e0e15d92131a6"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the behave MCP server?
behave is an MCP server listed in the public MCP registry as io.github.emirmrkaljevic/behave. Record how any CLI behaves and check that a rewrite behaves the same (golden tests). This page covers its MCPB bundle (https://github.com/emirmrkaljevic/behave/releases/download/v0.1.6/behave_0.1.6_linux_amd64.mcpb).
Is the behave MCP server safe to use?
behave scores 42 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the behave MCP server expose?
behave exposes 5 tools: behave_add_case, behave_diff, behave_exec, behave_list_cases, behave_probe. Their descriptions and schemas cost roughly 527 tokens of context every time the server is loaded.
What licence is the behave MCP server under?
behave declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.