Skills/PyPI/optical-context-mcp

optical-context-mcp@0.1.5

VERIFIED· not started

Publisher claims: "MCP server that compresses OCR-heavy PDFs into dense packed images for AI agent workflows." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher chrboebel · publishing for 252 daysInstalls 173Last detonated 15 h ago
$claude mcp add optical-context-mcp -- uvx optical-context-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
MISTRAL_API_KEYConfiguration, not credentials: OPTICAL_CONTEXT_ADAPTIVE_MODEL_PATH, OPTICAL_CONTEXT_DISABLE_ADAPTIVE_SIZING, OPTICAL_CONTEXT_MCP_JOBS_DIR
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for MISTRAL_API_KEY and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --net declared -- uvx optical-context-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-13 and scored it 89/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsoptical_mcp/service.py:27 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesload_dotenv(PROJECT_ROOT / ".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

No other findings across 2,284 lines in 24 files.

Cost to the agent

Instructions loaded
≈62 tok
1 file · 24 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for optical-context-mcp@0.1.5 as of 14 h ago. This is the package itself, not its dependencies.

optical-context-mcp@0.1.5 safety verdict: Verified (not started) — KillerSkills