spectr-mcp@0.2.0
VERIFIED· not startedPublisher claims: "Spectr MCP server — turn a screen recording into a production-ready spec.md, from inside Claude Code / Cursor / any MCP client." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
ANTHROPIC_API_KEYRESEND_API_KEYWORKER_WEBHOOK_SECRETConfiguration, not credentials: COMPRESS_THRESHOLD_MB, DEDUP_THRESHOLD, FFMPEG_TIMEOUT_SECONDS, FRAME_BATCH_SIZE, MAX_FRAMES, MAX_PROJECT_LOG_LINES, MAX_TOTAL_RETRIES, MIN_SCENE_FRAMES, OUTPUT_MODE, RESEND_FROM, SCENE_THRESHOLD, SCREEN_SPLIT_MAX, SCREEN_SPLIT_MIN, SCREEN_SPLIT_TIMEOUT, SCREEN_SPLIT_WORKERS, SPEC_ANALYSIS_WORKERS, SPEC_LANE_WORKERS, SPEC_SECTION_TIMEOUT, SPECTR_CLI_LOG_LEVEL, SPECTR_MCP_HTTP, SPECTR_MCP_LOG_LEVEL, STITCH_MODEL, SUPABASE_SERVICE_KEY, SUPABASE_URL, VISION_MODEL- Where it talks to
- spectr.to (its own)Also apple.com, resend.com — not the publisher's domain; check what for before connecting.
- 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, and read the third-party hosts first. The code names apple.com, resend.com as well as its own vendor. The guard injects ANTHROPIC_API_KEY, RESEND_API_KEY, WORKER_WEBHOOK_SECRET only into requests to spectr.to (and its subdomains) and refuses the rest.
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-18 and scored it 80/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 deviationsStatic findings
cp .env.example .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."required_substrings": ("Expo SDK 54", "Expo Go", "Animated", "FlatList", "npx expo install", "iPhone 15"),Fix: Pin versions and sources; vendor anything fetched at install time.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.<spectr:file name=".env.example">Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Install Expo-native packages only with `npx expo install` and use onlyFix: Pin versions and sources; vendor anything fetched at install time.- install Expo-native packages only with `npx expo install` and only at Expo-compatible versions for the installed SDKFix: Pin versions and sources; vendor anything fetched at install time.assert "npx expo install" in claude_code_prompt["required_substrings"]Fix: Pin versions and sources; vendor anything fetched at install time.print("✗ SUPABASE_URL not set. Check your .env file.")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.extra = {"../evil.sh": "rm -rf /", ".env.example": "KEY=val"}Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.result = subprocess.run(cmd_scene, capture_output=True, text=True, timeout=FFMPEG_TIMEOUT_SECONDS)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.assert "npx expo install" in PROMPT_3_SYSTEMFix: Pin versions and sources; vendor anything fetched at install time.assert "npx expo install" in PROMPT_3_USERFix: Pin versions and sources; vendor anything fetched at install time.result = subprocess.run(cmd, capture_output=True, text=True, timeout=FFMPEG_TIMEOUT_SECONDS)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.assert "npx expo install" in SPEC_SECTION_SYSTEMFix: Pin versions and sources; vendor anything fetched at install time.extra = {"../evil.sh": "rm -rf /", ".env.example": "KEY=val"}Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Install Expo-native packages only with `npx expo install` and use onlyFix: Pin versions and sources; vendor anything fetched at install time.assert ".env.example" in filesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.assert "SUPABASE_URL=" in files[".env.example"]Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.load_dotenv(Path(__file__).parent.parent / ".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- A single sentence saying Expo-native packages must be installed only with `npx expo install` and only at Expo-compatible versions for SDK 54Fix: Pin versions and sources; vendor anything fetched at install time.result = subprocess.run(cmd_fps, capture_output=True, text=True, timeout=FFMPEG_TIMEOUT_SECONDS)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
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 spectr-mcp@0.2.0 as of 36 min ago. This is the package itself, not its dependencies.