mcp-server@0.38.0
VERIFIED· startup onlyPublisher claims: "MCP server connecting AI agents to Scavio: web search, page extraction, and structured e-commerce, social, travel, jobs, real-estate, app-store, ad-library and company-filing data. 504 tools across 74 platforms plus Extract, Company Enrich, site map, craw" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
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_AUTH_SECRETSCAVIO_API_KEYConfiguration, not credentials: DASHBOARD_URL, ISSUER_URL, PLATFORM_KEYS, SCAVIO_API_BASE_URL, SCAVIO_PLATFORMS, TRANSPORT- Where it talks to
- scavio.dev (its own)Also glama.ai, cvs.com, menards.com, sephora.com, specsonline.com, ulta.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
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names glama.ai, cvs.com, menards.com, sephora.com, specsonline.com, ulta.com as well as its own vendor. The guard injects MCP_AUTH_SECRET, SCAVIO_API_KEY only into requests to scavio.dev (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; startup only; authenticated tool behavior not tested) on 2026-11-09 and scored it 88/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 · 27 s · 2 scenarios · 0 deviationsStatic findings
* Local npx installs run over stdio; the hosted server (mcp.scavio.dev) runsFix: Pin versions and sources; vendor anything fetched at install time.* Local npx installs run over stdio; the hosted server (mcp.scavio.dev) runsFix: Pin versions and sources; vendor anything fetched at install time.body = env?.details ? { ...env.details, message: env.message } : json;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. 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 @scavio/mcp-server@0.38.0 as of 5d ago. This is the package itself, not its dependencies.