← Index

Blink Camera

io.github.AbhijatSaxena/blink-camera-mcpv0.1.1Other

Control an Amazon Blink camera and its pan/tilt mount: aim it, read its position, grab a frame.

The current version, v0.1.1, was published to the official MCP registry on 2026-09-26. It is distributed as blink-camera-mcp on PyPI, filed under Other by this index, and declares 6 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Blink Camera in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-26).

Contracts can change after screening, with no version bump. The gate pins Blink Camera’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
BLINK_USERNAME
required

Blink account email address.

BLINK_PASSWORD
requiredsecret

Blink account password.

BLINK_2FA_FILE
secret

Path to a file holding the 2FA code, when the account has verification enabled. The code is read from the file, never from the command line.

BLINK_CAMERA_NAME

Which camera to drive, when the account has more than one.

BLINK_STATE_FILE

Where to cache the login token. Defaults to ~/.blink-mcp/state.json.

BLINK_FFMPEG

Path to the ffmpeg binary, if it is not on PATH.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Other