A

npm:can-see

https://www.npmjs.com/package/can-see
95/100 · MCP Trust Grade · checked 3h ago · MCP 0.5.1

What it offers — 21 tools · Search

launch

Launch a CLI app in a virtual terminal. IMPORTANT: You MUST call

screenshot

Capture the terminal as a PNG image

screenshot_region

Capture a specific rectangular area of the visible terminal as a PNG image

screenshot_text_region

Find text in the viewport and capture the surrounding area as a PNG. Searches visible viewport only (single-line match, returns first match top-to-bot

capture_baseline

Snapshot current terminal state for later diff comparison (screenshot also auto-captures a baseline)

diff_screenshot

Compare current terminal state against the baseline, return PNG with changed cells highlighted in red

get_cell_info

Query character, colors, and text attributes at a specific cell or range of cells

read_scrollback

Read text that has scrolled above the visible terminal viewport

start_recording

Begin capturing terminal frames for an animated GIF (frames captured on output, not fixed interval)

stop_recording

Stop recording and return the captured frames as an animated GIF. If the GIF exceeds the inline size limit (~4MB), frames are automatically trimmed. I

read_text

Read the terminal buffer as plain text (for programmatic assertions instead of visual screenshots)

wait_for_text

Wait until specific text appears in the terminal buffer (replaces sleep-and-screenshot polling)

wait_for_idle

Wait until terminal output has been stable for a given duration. Use idleMs (default) for apps that stop producing output, or stableMs for apps with c

wait_for_color

Wait until a specific color appears at a position (or anywhere in the viewport)

wait_for_exit

Wait until the process exits and return its exit code and signal

send_keys

Send keystrokes to the app (e.g.,

send_text

Type a string of text into the app

get_process_status

Get the current process status — use to distinguish

+3 more tools

Spec / packaging20%100
Security (OWASP MCP)30%90
Maintenance / popularity20%100
Tool hygiene15%95
Transparency / provenance15%90

Findings

INFO Static analysis of npm package can-see@0.5.1 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:can-see on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:can-see grade A
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade A · wmcp.sh
[![MCP Trust Grade A](https://wmcp.sh/mcp/grade/npm%3Acan-see/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Acan-see)
<a href="https://wmcp.sh/mcp/grade/npm%3Acan-see"><img src="https://wmcp.sh/mcp/grade/npm%3Acan-see/badge.svg" alt="MCP Trust Grade A · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.