io.github.Jonahbkerr/yocoolab
NPM · @YOCOOLAB/MCP-SERVER
Pin visual feedback on any live web page and send it to Claude Code, Cursor or your AI agent.
Available components
Last scanned (2 hours ago)
Scores higher than 65% of npm servers
Category Developer Tools
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 9.0.1, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency48
- 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 (Apache-2.0).Pass
- Actively maintained (last published 32 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 432 tokens (~72/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 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; "reply_to_companion" implies "send" 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 supported MCP spec version (2025-11-25); the latest is 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.
- 3 Nov 26 +6
- Stability: fail → pass ▲ security
- 17 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 43 to 60.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43.
- 15 Oct 26 −3
No change was recorded against any check on this day. Stability & Change Management went from 60 to 40.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57.
- 4 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Oct 26 −20
- Malware scan: pass → unverified ▼ security
- Stability: 0.83 → fail ▼ security
- Schema quality: 59 → 72 ▼ functional
- Package version: 2.4.3 → 3.0.0 functional
- Package version: 2.4.3 → 2.5.0 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 5 Nov 2026 · Analysed npm/@yocoolab/mcp-server@3.0.0
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Deprecated | 1 |
| Stale | 30 |
| 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 →
find_source_for_selection ~103
Searches the workspace for source files that likely define or render the selected UI element. Returns ranked candidates with file paths, line ranges, confidence scores, and match reasons. Can work with live Chrome selections or stored thread element_context.
| Name | Type | Req | Description |
|---|---|---|---|
| correlationId | string | – | The correlationId of a specific selection. If omitted, uses the latest selection. |
| thread_id | string | – | A Yocoolab thread ID to use stored element_context instead of a live selection. |
No output schema declared.
No examples provided.
get_companion_messages ~49
Check for new messages from the AI Companion panel in the Chrome extension. Returns pending messages and clears the queue. Each message includes the user text, page context, and optional screenshot/element attachments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_element_context ~130
Returns a comprehensive summary of a UI element, including its DOM context, computed styles, and ranked source code candidates. Works with live Chrome selections or stored thread element_context. This is the primary tool to use when the user wants to modify a UI element.
| Name | Type | Req | Description |
|---|---|---|---|
| correlationId | string | – | The correlationId of a specific selection. If omitted, uses the latest selection. |
| includePrompt | boolean | – | Whether to include a pre-built edit prompt with constraints (default: true). |
| thread_id | string | – | A Yocoolab thread ID to use stored element_context instead of a live selection. |
No output schema declared.
No examples provided.
get_latest_selection ~40
Returns the most recent element selection from the Chrome extension. Includes element selector, tag, text content, classes, attributes, computed styles, and page context.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_selection_history ~49
Returns the last N element selections from the Chrome extension, newest first. Useful for comparing multiple elements or reviewing recent selections.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of selections to return (max 50) |
No output schema declared.
No examples provided.
reply_to_companion ~61
Send a reply back to the AI Companion panel in the Chrome extension. The reply will appear as an assistant message in the companion chat UI. Supports Markdown formatting.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The reply message to display in the companion panel (supports Markdown) |
No output schema declared.
No examples provided.
How do I install the io.github.Jonahbkerr/yocoolab MCP server?
io.github.Jonahbkerr/yocoolab runs locally as an npm package, launched with npx -y @yocoolab/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @yocoolab/mcp-server
claude mcp add jonahbkerr-yocoolab -- npx -y @yocoolab/mcp-server
What is the io.github.Jonahbkerr/yocoolab MCP server?
io.github.Jonahbkerr/yocoolab is an MCP server listed in the public MCP registry as io.github.Jonahbkerr/yocoolab. Pin visual feedback on any live web page and send it to Claude Code, Cursor or your AI agent. This page covers its npm package (@yocoolab/mcp-server).
Is the io.github.Jonahbkerr/yocoolab MCP server safe to use?
io.github.Jonahbkerr/yocoolab scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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.Jonahbkerr/yocoolab MCP server expose?
io.github.Jonahbkerr/yocoolab exposes 6 tools: get_companion_messages, reply_to_companion, get_latest_selection, get_selection_history, find_source_for_selection, get_element_context. Their descriptions and schemas cost roughly 432 tokens of context every time the server is loaded.
Is the io.github.Jonahbkerr/yocoolab MCP server still maintained?
io.github.Jonahbkerr/yocoolab is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.Jonahbkerr/yocoolab MCP server under?
io.github.Jonahbkerr/yocoolab 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.