Bawbel Scanner
PYPI · BAWBEL-MCP
Scan MCP servers and skill files for AVE vulnerabilities. Conformance scoring and threat intel.
Available components
Last scanned (21 hours ago)
Scores higher than 76% of PyPI servers
Category Security
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 17 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to bawbel/bawbel-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 164 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1248 tokens (~113/item across 11 items; 10 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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.
- 4 Nov 26 −19
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.67 functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Security disclosure: fail → pass ▲ functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.80 functional
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 4 Nov 2026 · Analysed pypi/bawbel-mcp@1.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | bawbel/bawbel-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/bawbel/bawbel-mcp/.github/workflows/publish.yml@refs/tags/v1.1.0 |
| Rekor log index | 1615491456 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:886bec169bb32d79d6e09cdbe2714fb864adb8d00ea6e6ffb599a14de95f0786 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 17 packages
| Packages resolved | 17 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
accept_finding Accept Finding ~219
Insert a justified suppression comment into a skill file. Marks a finding as a false positive or accepted risk with a documented reason, reviewer, and optional expiry date. The suppression is written directly into the file as a structured comment that lives in version control and shows up in PR reviews. Accepted risks with an expiry date automatically resurface as active findings on the next scan after the expiry date passes.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptance_type | string | – | "false-positive" (permanent) or "accepted-risk" (with expiry) |
| ave_id | string | yes | AVE ID to suppress (e.g. AVE-2026-00001) |
| expires_days | – | – | Days until the accepted risk expires (required for accepted-risk) |
| file_path | string | yes | Absolute or relative path to the skill file |
| line | integer | yes | Line number of the finding to suppress |
| reason | string | yes | Why this finding is a false positive or accepted risk |
| reviewer | string | yes | Your GitHub handle or name |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check_conformance Check Conformance ~83
Score an MCP server manifest against the MCP specification. Runs 18 checks across 3 tiers (REQUIRED, RECOMMENDED, BEST PRACTICE) and returns a grade from A+ to F. A server is conformant when all REQUIRED checks pass.
| Name | Type | Req | Description |
|---|---|---|---|
| url_or_path | string | yes | Local path to server.json OR base URL of MCP server |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check_pins Check Pins ~86
Check a directory for skill file rug pull drift. Compares current SHA-256 hashes of skill files against the pins stored in .bawbel-pins.json. Reports any files that changed after the last audit. Run bawbel pin <path> from the CLI to create the initial pin file.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Directory to check (default: current directory) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_ave List Ave ~98
List AVE records with optional filters. Use this to browse the full AVE database or filter by severity, component type, or OWASP MCP category.
| Name | Type | Req | Description |
|---|---|---|---|
| component_type | – | – | Filter by skill, mcp, prompt, or plugin |
| owasp_mcp | – | – | Filter by OWASP MCP category (e.g. MCP03, MCP05) |
| severity | – | – | Filter by CRITICAL, HIGH, MEDIUM, or LOW |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
lookup_ave Lookup Ave ~86
Get the full AVE record for a specific vulnerability ID. Returns the complete record including title, description, AIVSS score, behavioral fingerprint, indicators of compromise, OWASP MCP mapping, and remediation steps.
| Name | Type | Req | Description |
|---|---|---|---|
| ave_id | string | yes | AVE ID in the format AVE-2026-NNNNN (e.g. AVE-2026-00001) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scan_chain Scan Chain ~99
Delegation chain scan of skill file content. Filters to AVE-2026-00048 (unsafe agent delegation) and related rules. Detects sub-agent spawning with inherited permissions and missing trust boundaries. Use this when evaluating a skill that spawns sub-agents or delegates tasks to other agents.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text content to scan |
| no_ignore | boolean | – | If True, bypass all suppressions |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scan_content Scan Content ~141
Scan raw text content for AVE security vulnerabilities. Use this to check skill file content, system prompts, MCP tool descriptions, or any agentic AI component before using it. Returns findings with AVE IDs, AIVSS severity scores, OWASP MCP categories, and links to full remediation guidance. Also detects toxic flows where two findings combine into a complete attack chain.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text content to scan (skill file, system prompt, etc.) |
| label | string | – | Optional label for the content in the output |
| no_ignore | boolean | – | If True, bypass all suppressions and show every finding |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scan_creds Scan Creds ~108
Credential-focused scan of skill file content. Filters to AVE-2026-00047 (hardcoded credentials) and related rules only. Detects API keys, tokens, passwords, private keys, and URL-embedded credentials. Use this when you specifically want to check whether a skill file contains hardcoded secrets before adding it to your agent config.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text content to scan |
| no_ignore | boolean | – | If True, bypass all suppressions |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scan_server_card Scan Server Card ~135
Fetch and scan an MCP server-card for security vulnerabilities. Fetches .well-known/mcp.json from the given server URL and scans all tool descriptions, parameter descriptions, and config schemas for AVE vulnerabilities before your agent connects. This is the primary tool to run before adding any MCP server to your configuration. A poisoned server-card injects behavioral instructions at the discovery layer, before any tool call is made.
| Name | Type | Req | Description |
|---|---|---|---|
| no_ignore | boolean | – | If True, bypass all suppressions and show every finding |
| url | string | yes | Base URL of the MCP server (e.g. https://api.example.com) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_ave Search Ave ~98
Search AVE records by keyword. Searches across AVE ID, title, attack class, description, and behavioral fingerprint. Returns matching records with severity, AIVSS score, and a link to the full record.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results (default 10, max 20) |
| query | string | yes | Search term (e.g. "tool poisoning", "credential", "MCP01") |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Bawbel Scanner MCP server?
Bawbel Scanner runs locally as a PyPI package, launched with uvx bawbel-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · bawbel-mcp
claude mcp add bawbel-bawbel-mcp -- uvx bawbel-mcp
What is the Bawbel Scanner MCP server?
Bawbel Scanner is an MCP server listed in the public MCP registry as io.github.bawbel/bawbel-mcp. Scan MCP servers and skill files for AVE vulnerabilities. Conformance scoring and threat intel. This page covers its PyPI package (bawbel-mcp).
Is the Bawbel Scanner MCP server safe to use?
Bawbel Scanner scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 Bawbel Scanner MCP server expose?
Bawbel Scanner exposes 10 tools: scan_content, scan_server_card, scan_creds, scan_chain, accept_finding, and 5 more. Their descriptions and schemas cost roughly 1,153 tokens of context every time the server is loaded.
Is the Bawbel Scanner MCP server still maintained?
Bawbel Scanner is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Bawbel Scanner MCP server under?
Bawbel Scanner declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.