mcp-server@0.3.34
VERIFIED· not startedPublisher claims: "Official sync. labs MCP server: lipsync and dub videos, make photos talk and manage assets from 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
MCP_STATUS_TOKENOPENAI_APPS_CHALLENGE_TOKENSYNC_API_KEYSYNC_OAUTH_AUTHORIZATION_URLConfiguration, not credentials: DO_NOT_TRACK, GIT_SHA, K_REVISION, MCP_ISSUER_URL, MCP_MAX_IN_FLIGHT_REQUESTS, MCP_MAX_SESSIONS, MCP_RUNTIME_TELEMETRY_INTERVAL_MS, MCP_SESSION_IDLE_TTL_MS, MCP_SESSION_SWEEP_INTERVAL_MS, MCP_SHUTDOWN_GRACE_MS, MCP_UPLOAD_CONCURRENCY, MCP_UPLOAD_MAX_BYTES, MCP_UPLOAD_MAX_QUEUED, MCP_UPLOAD_RETRY_AFTER_MS, MCP_UPLOAD_TIMEOUT_MS, PORTER_TAG, SYNC_APP_UPLOAD_ORIGINS, SYNC_APP_UPLOAD_STORAGE_ORIGIN, SYNC_BASE_URL, SYNC_CHATGPT_APP_CONNECT_DOMAINS, SYNC_CHATGPT_APP_DIR, SYNC_CHATGPT_APP_DOMAIN, SYNC_CHATGPT_APP_PREVIOUS_DIRS, SYNC_CHATGPT_APP_RELEASES, SYNC_CHATGPT_APP_RESOURCE_DOMAINS, SYNC_MCP_REFERRAL, SYNC_MCP_REGISTRATION_URL, SYNC_MCP_SPEND_CONFIRMATION, SYNC_MCP_TELEMETRY, SYNC_MCP_TOOLSETS, SYNC_MCP_UPDATE_CHECK- Where it talks to
- sync.so (its own)Also oaiusercontent.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 oaiusercontent.com as well as its own vendor. The guard injects MCP_STATUS_TOKEN, OPENAI_APPS_CHALLENGE_TOKEN, SYNC_API_KEY, SYNC_OAUTH_AUTHORIZATION_URL only into requests to sync.so (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.
What changed since 0.3.22
vet-skills diff mcp-server 0.3.22 0.3.34This version reaches for something 0.3.22 did not: 1 new credential variable (MCP_STATUS_TOKEN). Compared from the two recorded runs, not from source.
- New credential variables
- MCP_STATUS_TOKEN
0.3.22 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
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 85/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 · 1 s · 2 scenarios · 0 deviationsStatic findings
res.status(400).json({ error: 'Initialize an MCP session before sending requests' });Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.// raw client_secret. Proxy token/revoke requests with the incoming secret andFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."build": "tsc -b tsconfig.build.json && chmod +x dist/cli.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.res.status(400).json({ error: 'Complete MCP initialization before sending requests' });Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.const UPDATE_COMMAND = 'npx -y @sync.so/mcp-server@latest';Fix: Pin versions and sources; vendor anything fetched at install time.* Local (stdio) installs go stale silently: npx keeps running whatever it cached. AtFix: Pin versions and sources; vendor anything fetched at install time.* Local (stdio) installs go stale silently: npx keeps running whatever it cached. AtFix: Pin versions and sources; vendor anything fetched at install time.commands: ["npx -y skills add synchronicity-labs/skills -g -s '*'"],Fix: Pin versions and sources; vendor anything fetched at install time.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 @sync.so/mcp-server@0.3.34 as of 8 h ago. This is the package itself, not its dependencies.