io.github.Solteris-Dev/pir-mcp
NPM · PIR-MCP · SCANNED SEP 25
Motion sensor for AI agents: tells when a screen region changes or goes still. Scores, never pixels.
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
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 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1092 tokens (~109/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
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; "pir_remove_region" implies "remove" 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 10 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.Solteris-Dev/pir-mcp server?
io.github.Solteris-Dev/pir-mcp runs locally as an npm package, launched with npx -y pir-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · pir-mcp
claude mcp add solteris-dev-pir-mcp -- npx -y pir-mcp
{
"mcpServers": {
"solteris-dev-pir-mcp": {
"command": "npx",
"args": [
"-y",
"pir-mcp"
]
}
}
} {
"servers": {
"solteris-dev-pir-mcp": {
"command": "npx",
"args": [
"-y",
"pir-mcp"
]
}
}
} codex mcp add solteris-dev-pir-mcp -- npx -y pir-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"solteris-dev-pir-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"pir-mcp"
],
"enabled": true
}
}
} openclaw mcp add solteris-dev-pir-mcp --command npx --arg -y --arg pir-mcp
mcp_servers:
solteris-dev-pir-mcp:
command: "npx"
args: ["-y", "pir-mcp"] {
"McpServers": {
"solteris-dev-pir-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"pir-mcp"
]
}
}
} assistant mcp add solteris-dev-pir-mcp -t stdio -c npx -a -y pir-mcp
{
"mcpServers": {
"solteris-dev-pir-mcp": {
"command": "npx",
"args": [
"-y",
"pir-mcp"
]
}
}
} 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.
- 25 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
- 24 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 16 Sept 26 68
First indexed and scored.
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 25 Sept 2026 · Analysed npm/pir-mcp@0.1.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 →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| 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 →
pir_define_region ~140
Name a rectangle of the screen to watch. Coordinates are in the global layout the capture tool uses (on a multi-monitor wlroots layout an output left of the primary has negative x). Masks are rects inside the region, in region-local pixels, that are ignored: put a clock or spinner there. Redefining a name replaces it and forgets its last sample.
| Name | Type | Req | Description |
|---|---|---|---|
| h | integer | yes | height, pixels |
| masks | array | – | – |
| name | string | yes | – |
| w | integer | yes | width, pixels |
| x | integer | yes | left edge, pixels |
| y | integer | yes | top edge, pixels |
No output schema declared.
No examples provided.
pir_define_window ~104
Watch a window rather than a fixed rectangle: geometry is looked up from the window id before every capture, so the region follows the window when it moves. A resize counts as maximal change. Masks are window-local. The id is whatever your window-geometry command understands (a Hyprland address like 0x5f3a..., an X11 window id).
| Name | Type | Req | Description |
|---|---|---|---|
| masks | array | – | – |
| name | string | yes | – |
| window | string | yes | – |
No output schema declared.
No examples provided.
pir_list_regions ~20
The regions currently defined, with their geometry and masks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pir_pick_mask ~60
Ask the person to draw a rectangle inside an existing region that should be ignored (a clock, a spinner, a caret). Forgets the region's last sample, since masked grids are not comparable to unmasked ones.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
pir_pick_region ~101
Ask the person at the screen to draw the rectangle to watch (a selector such as slurp appears; Escape cancels). Prefer this over pir_define_region whenever a human is present: they choose what is sensed, and you get the geometry back. Blocks until they finish or the selector times out.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| purpose | string | – | one line on why you want to watch it; returned unchanged so it lands in the transcript |
No output schema declared.
No examples provided.
pir_pick_window ~84
Ask the person at the screen to click the window to watch (visible windows are offered as boxes; Escape cancels). The region then follows that window. Prefer this over pir_define_window when a human is present.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| purpose | string | – | one line on why you want to watch it; returned unchanged so it lands in the transcript |
No output schema declared.
No examples provided.
pir_remove_region ~20
Forget a region.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
pir_sample ~74
Capture the region once and score it against the previous sample of the same region (null on the first call). Cheap and non-blocking: use it to check the capture command works, to take a baseline before doing something, or to ask 'did anything happen there since I last looked?'.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
pir_wait_for_change ~235
Block until the region looks different from how it looked when this call started, or until timeout_ms. Returns changed=true with the score, or changed=false with the largest score seen. Use it as a doorbell: 'wake me when the build output moves', 'when the dialog closes', 'when the game loads'.
| Name | Type | Req | Description |
|---|---|---|---|
| interval_ms | integer | – | sampling period (default 500) |
| metric | string | – | what the threshold applies to. rmse (default): the whole region moved. peak: any single cell moved, for a small thing that should tick inside a larger region (a clock in a bar). |
| name | string | yes | – |
| threshold | number | – | score that counts as a change, 0..1 (default 0.05). With metric=rmse a caret or cursor edge scores about 0.02 and a dialog opening 0.1+. With metric=peak a digit flipping in one cell scores about 0.0… |
| timeout_ms | integer | – | give up after this long (default 55000, max 540000) |
No output schema declared.
No examples provided.
pir_wait_for_stillness ~254
Block until consecutive samples have stayed below threshold for still_for_ms, or until timeout_ms. A short window means 'the page/animation has settled, safe to act'. A long window on something that should keep changing (a clock, a progress bar, a status bar) means it is frozen: still=true is then the alarm.
| Name | Type | Req | Description |
|---|---|---|---|
| interval_ms | integer | – | sampling period (default 500) |
| metric | string | – | what the threshold applies to. rmse (default): the whole region moved. peak: any single cell moved, for a small thing that should tick inside a larger region (a clock in a bar). |
| name | string | yes | – |
| still_for_ms | integer | yes | how long nothing may change |
| threshold | number | – | score that counts as a change, 0..1 (default 0.05). With metric=rmse a caret or cursor edge scores about 0.02 and a dialog opening 0.1+. With metric=peak a digit flipping in one cell scores about 0.0… |
| timeout_ms | integer | – | give up after this long (default 55000, max 540000) |
No output schema declared.
No examples provided.
What is the io.github.Solteris-Dev/pir-mcp server?
io.github.Solteris-Dev/pir-mcp is listed in the public MCP registry as io.github.Solteris-Dev/pir-mcp. Motion sensor for AI agents: tells when a screen region changes or goes still. Scores, never pixels. This page covers its npm package (pir-mcp).
Is the io.github.Solteris-Dev/pir-mcp server safe to use?
io.github.Solteris-Dev/pir-mcp scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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.Solteris-Dev/pir-mcp server expose?
io.github.Solteris-Dev/pir-mcp exposes 10 tools: pir_define_region, pir_define_window, pir_pick_window, pir_pick_region, pir_pick_mask, and 5 more. Their descriptions and schemas cost roughly 1,092 tokens of context every time the server is loaded.
Is the io.github.Solteris-Dev/pir-mcp server still maintained?
io.github.Solteris-Dev/pir-mcp is still listed as active in the MCP registry. We last reached this channel on 25 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.Solteris-Dev/pir-mcp server under?
io.github.Solteris-Dev/pir-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.