syia-mcp-vendor-2025-x7k9@0.1.14
VERIFIED· install onlyPublisher claims: "MCP Vendor Module" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 8 of 12 bundled scripts run with no arguments (the rest were not run: per-bundle cap), with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
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
COHERE_API_KEYLLAMA_API_KEYOPENAI_API_KEYPERPLEXITY_API_KEYTYPESENSE_API_KEYor--llama-api-key/--typesense-api-key/--cohere-api-key/--openai-api-key/--perplexity-api-keyConfiguration, not credentials: MONGODB_DB_NAME, MONGODB_URI, TYPESENSE_HOST, TYPESENSE_PORT, TYPESENSE_PROTOCOL, VENDOR_MODEL- Where it talks to
- no vendor host named in the codeAlso llamaindex.ai, siya.com, perplexity.ai — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names llamaindex.ai, siya.com, perplexity.ai as well as its own vendor. The guard injects COHERE_API_KEY, LLAMA_API_KEY, OPENAI_API_KEY, PERPLEXITY_API_KEY, TYPESENSE_API_KEY only into requests to the host you bind (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; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-19 and scored it 90/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
print("Set it in your environment, in a .env file, or provide it with --llama-api-key.")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.print("Set it in your environment, in a .env file, or provide it with --llama-api-key.")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for syia-mcp-vendor-2025-x7k9@0.1.14 as of 18 h ago. This is the package itself, not its dependencies.