Blink Camera
PYPI · BLINK-CAMERA-MCP · SCANNED SEP 28
Control an Amazon Blink camera and its pan/tilt mount: aim it, read its position, grab a frame.
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
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 4 of 48 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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 548 tokens (~68/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (88% of tools); any adoption earns full credit.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; "pan_tilt_home" 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 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Blink Camera MCP server?
Blink Camera runs locally as a PyPI package, launched with uvx blink-camera-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · blink-camera-mcp
claude mcp add abhijatsaxena-blink-camera-mcp -- uvx blink-camera-mcp
{
"mcpServers": {
"abhijatsaxena-blink-camera-mcp": {
"command": "uvx",
"args": [
"blink-camera-mcp"
]
}
}
} {
"servers": {
"abhijatsaxena-blink-camera-mcp": {
"command": "uvx",
"args": [
"blink-camera-mcp"
]
}
}
} codex mcp add abhijatsaxena-blink-camera-mcp -- uvx blink-camera-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"abhijatsaxena-blink-camera-mcp": {
"type": "local",
"command": [
"uvx",
"blink-camera-mcp"
],
"enabled": true
}
}
} openclaw mcp add abhijatsaxena-blink-camera-mcp --command uvx --arg blink-camera-mcp
mcp_servers:
abhijatsaxena-blink-camera-mcp:
command: "uvx"
args: ["blink-camera-mcp"] {
"McpServers": {
"abhijatsaxena-blink-camera-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"blink-camera-mcp"
]
}
}
} assistant mcp add abhijatsaxena-blink-camera-mcp -t stdio -c uvx -a blink-camera-mcp
{
"mcpServers": {
"abhijatsaxena-blink-camera-mcp": {
"command": "uvx",
"args": [
"blink-camera-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.
- 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
- 26 Sept 26 67
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 28 Sept 2026 · Analysed pypi/blink-camera-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 48 packages
| Packages resolved | 48 |
|---|---|
| Stale | 3 |
| No linked repository | 1 |
| 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 →
camera_status ~89
Report the camera's orientation, travel limits and session state. Call this first: `position` is null until the camera has a live session, which tells you the other tools will fail. When the session could not be started at all, `startup_error` says why. It also reports `stream_url`, where the live video can be read (e.g. by OBS or ffmpeg).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
pan_tilt ~124
Aim the camera at an absolute angle and wait until it gets there. `pan` and `tilt` are whole degrees (signed, roughly -128..127). The returned position is one the hardware reported; if the mount never confirms arrival this fails instead of pretending success. A camera already at the requested angle is left alone and reported as settled with `moved: false` -- that is a success. Set `force` to re-send.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | – |
| pan | integer | yes | – |
| tilt | integer | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
pan_tilt_home ~25
Send the camera to its saved home position and report where it ends up.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
pan_tilt_nudge ~78
Turn the camera relative to where it points now, in degrees. Prefer this when you have not read the current angle: it reads the mount's own report first and keeps the move small. Deltas are clamped to the mount's angle range.
| Name | Type | Req | Description |
|---|---|---|---|
| pan_delta | integer | – | – |
| tilt_delta | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pan_tilt_overview ~29
Start a full 360 degree pan overview. Returns immediately; the sweep takes a while.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
pan_tilt_set_home ~22
Save the camera's current angle as its home position.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
pan_tilt_stop ~25
Stop the mount's motors immediately. Harmless when it is already idle.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
snapshot ~61
Capture one still frame of whatever the camera is pointed at. This looks into the room, so call it only when the user asks to see the camera. The frame comes from the stream the camera is already sending, so it does not start a second session.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Blink Camera MCP server?
Blink Camera is an MCP server listed in the public MCP registry as io.github.AbhijatSaxena/blink-camera-mcp. Control an Amazon Blink camera and its pan/tilt mount: aim it, read its position, grab a frame. This page covers its PyPI package (blink-camera-mcp).
Is the Blink Camera MCP server safe to use?
Blink Camera scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 28 September 2026. 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 Blink Camera MCP server expose?
Blink Camera exposes 8 tools: camera_status, pan_tilt, pan_tilt_nudge, pan_tilt_stop, pan_tilt_home, and 3 more. Their descriptions and schemas cost roughly 453 tokens of context every time the server is loaded.
Is the Blink Camera MCP server still maintained?
Blink Camera is still listed as active in the MCP registry. We last reached this channel on 28 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 Blink Camera MCP server under?
Blink Camera declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.