io.github.asume21/webear
NPM · WEBEAR · SCANNED SEP 20
Give your AI coding assistant ears — capture, analyze, and describe live audio.
Available components
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 Security53
- Malware check failed: a supply-chain vendor flagged a high-severity malware risk. See how to fix → Fail
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
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 80 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 247 tokens (~61/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.asume21/webear MCP server?
io.github.asume21/webear runs locally as an npm package, launched with npx -y webear. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · webear
claude mcp add asume21-webear -- npx -y webear
{
"mcpServers": {
"asume21-webear": {
"command": "npx",
"args": [
"-y",
"webear"
]
}
}
} {
"servers": {
"asume21-webear": {
"command": "npx",
"args": [
"-y",
"webear"
]
}
}
} codex mcp add asume21-webear -- npx -y webear
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"asume21-webear": {
"type": "local",
"command": [
"npx",
"-y",
"webear"
],
"enabled": true
}
}
} openclaw mcp add asume21-webear --command npx --arg -y --arg webear
mcp_servers:
asume21-webear:
command: "npx"
args: ["-y", "webear"] {
"McpServers": {
"asume21-webear": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"webear"
]
}
}
} assistant mcp add asume21-webear -t stdio -c npx -a -y webear
{
"mcpServers": {
"asume21-webear": {
"command": "npx",
"args": [
"-y",
"webear"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.83 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 0
- Security disclosure: fail → unverified ▼ 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 20 Sept 2026 · Analysed npm/webear@1.2.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
analyze_audio ~55
Run signal analysis on a captured audio clip. Returns RMS, peak dB, clipping, spectral centroid, frequency band energy, estimated BPM, and timing jitter.
| Name | Type | Req | Description |
|---|---|---|---|
| capture_id | string | yes | The capture ID returned by capture_audio |
No output schema declared.
No examples provided.
capture_audio ~60
Record a short clip of what the running web app is currently outputting. Returns a capture ID you can pass to analyze_audio or describe_audio.
| Name | Type | Req | Description |
|---|---|---|---|
| duration_ms | number | – | How many milliseconds to record (default 3000, max 30000) |
No output schema declared.
No examples provided.
describe_audio ~60
Send a captured audio clip to Gemini or GPT-4o to get a plain-English description of what it sounds like — useful when something sounds wrong but you cannot describe it.
| Name | Type | Req | Description |
|---|---|---|---|
| capture_id | string | yes | The capture ID returned by capture_audio to describe |
No output schema declared.
No examples provided.
diff_audio ~72
Compare two audio captures and flag what changed — loudness, tone, timing, clipping. Use this before and after a code change to verify the audio impact.
| Name | Type | Req | Description |
|---|---|---|---|
| capture_id_a | string | yes | First capture ID (the "before") |
| capture_id_b | string | yes | Second capture ID (the "after") |
No output schema declared.
No examples provided.
What is the io.github.asume21/webear MCP server?
io.github.asume21/webear is an MCP server listed in the public MCP registry as io.github.asume21/webear. Give your AI coding assistant ears, capture, analyze, and describe live audio. This page covers its npm package (webear).
Is the io.github.asume21/webear MCP server safe to use?
io.github.asume21/webear scores 71 out of 100 on VerifyMCP. A supply-chain scanner flagged a possible malware risk on one channel of this server. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.asume21/webear MCP server expose?
io.github.asume21/webear exposes 4 tools: capture_audio, analyze_audio, describe_audio, diff_audio. Their descriptions and schemas cost roughly 247 tokens of context every time the server is loaded.
Is the io.github.asume21/webear MCP server still maintained?
io.github.asume21/webear is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.asume21/webear MCP server under?
io.github.asume21/webear declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.