videovector-mcp-server@7.0.1
VERIFIED· not startedPublisher claims: "Model Context Protocol server for the VectorMethods VideoVector media intelligence API" 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_OAUTH_ISSUERMCP_OAUTH_JWKS_URLMCP_OAUTH_RESOURCEVIDEOVECTOR_API_KEYConfiguration, not credentials: MCP_HTTP_HOST, MCP_TRANSPORT_MODE, MCP_UPLOAD_API_BASE_URL, VIDEOVECTOR_BASE_URL- Where it talks to
- vectormethods.com (its own)Also files.example — 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 files.example as well as its own vendor. The guard injects MCP_OAUTH_ISSUER, MCP_OAUTH_JWKS_URL, MCP_OAUTH_RESOURCE, VIDEOVECTOR_API_KEY only into requests to vectormethods.com (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-10 and scored it 92/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 · 10 s · 2 scenarios · 0 deviationsStatic findings
verify your email if requested, and return to the client. No API key or localFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct."npm_install_command": "npx -y @vectormethods/videovector-mcp-server"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 @vectormethods/videovector-mcp-server@7.0.1 as of 5d ago. This is the package itself, not its dependencies.