Ext Ops Panel
Open dashboard
Comparison

io.github.HurleySk/can-see vs io.github.Solteris-Dev/pir-mcp

io.github.HurleySk/can-see is an MCP server published by HurleySk. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Solteris-Dev/pir-mcp is an MCP server published by Solteris-Dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.HurleySk/can-seeio.github.Solteris-Dev/pir-mcp
Official MCP Registry Listed
Version: 0.4.0
Downloads/month (npm): 169
Downloads/week (npm): 32
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (npm): 125
Downloads/week (npm): 47
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.HurleySk/can-see vs io.github.Solteris-Dev/pir-mcp
Factio.github.HurleySk/can-seeio.github.Solteris-Dev/pir-mcp
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (can-see)On your machine (pir-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 05, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/hurleysk/can-seegithub.com/solteris-dev/pir-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.HurleySk/can-see

In its own words, on Official MCP Registry:

Let AI agents see and interact with terminal/CLI apps via PNG screenshots

io.github.Solteris-Dev/pir-mcp

In its own words, on Official MCP Registry:

Motion sensor for AI agents: tells when a screen region changes or goes still. Scores, never pixels.

How to run each

io.github.HurleySk/can-see As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio can-see -- npx -y can-see

io.github.Solteris-Dev/pir-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio pir-mcp -- npx -y pir-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.HurleySk/can-see asks for

  • DEFAULT_COLS
  • DEFAULT_ROWS
  • IDLE_TIMEOUT_MS

Only io.github.Solteris-Dev/pir-mcp asks for

  • PIR_CAPTURE_CMD
  • PIR_MAX_WAIT_MS
  • PIR_PICK_WINDOW_CMD
  • PIR_SELECT_CMD
  • PIR_WINDOW_GEOMETRY_CMD

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.HurleySk/can-see · What it can do: io.github.Solteris-Dev/pir-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built