Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.ExpertVagabond/volcengine

NPM · VOLCENGINE-MCP

ByteDance Volcano Engine (Doubao) MCP server

Available components

0 this week 69 Trust /100

Last scanned (16 hours ago)

Scores higher than 39% of npm servers

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.5.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 7 of 14 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency18
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 260 tokens (~65/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 82% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1
    • Stability: 0.97 → pass security
  • 19 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 13 Nov 26 +1
    • Stability: 0.97 → pass security
  • 11 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 3 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 24 Oct 26 0
    • CVE-2023-54404 affects this package: high ▼ security
  • 22 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/volcengine-mcp@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 3 findings
ID CVE Severity Vector Fix available
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-w48q-cv73-mx4w CVE-2025-66414 high yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 14 packages
Packages resolved 14
Stale 7
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~260 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
doubao_chat ~70

Have a multi-turn conversation with Doubao models. Supports conversation history.

NameTypeReqDescription
max_tokensnumber––
messagesarrayyesArray of chat messages with role (system/user/assistant) and content
modelstring–Model ID to use
temperaturenumber––

No output schema declared.

No examples provided.

doubao_embeddings ~49

Generate text embeddings using Doubao embedding models. Useful for semantic search and RAG.

NameTypeReqDescription
modelstring–Embedding model ID
textsarrayyesArray of texts to embed

No output schema declared.

No examples provided.

doubao_generate ~122

Generate text using ByteDance Doubao models. Use for text completion, content generation, and single-turn tasks.

NameTypeReqDescription
max_tokensnumber–Maximum tokens to generate
modelstring–Model ID (e.g., doubao-pro-32k, doubao-lite-4k, doubao-seed-1-6-250615)
promptstringyesThe prompt to send to the model
system_promptstring–Optional system prompt to set context
temperaturenumber–Sampling temperature (0-1)

No output schema declared.

No examples provided.

doubao_list_models ~19

List available Doubao models from Volcano Engine

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.ExpertVagabond/volcengine MCP server?

io.github.ExpertVagabond/volcengine runs locally as an npm package, launched with npx -y volcengine-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · volcengine-mcp

# add to Claude Code
claude mcp add expertvagabond-volcengine -- npx -y volcengine-mcp
Common questions

What is the io.github.ExpertVagabond/volcengine MCP server?

io.github.ExpertVagabond/volcengine is an MCP server listed in the public MCP registry as io.github.ExpertVagabond/volcengine. ByteDance Volcano Engine (Doubao) MCP server. This page covers its npm package (volcengine-mcp).

Is the io.github.ExpertVagabond/volcengine MCP server safe to use?

io.github.ExpertVagabond/volcengine scores 69 out of 100 on VerifyMCP. We recorded 3 known advisories against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.ExpertVagabond/volcengine MCP server expose?

io.github.ExpertVagabond/volcengine exposes 4 tools: doubao_generate, doubao_chat, doubao_embeddings, doubao_list_models. Their descriptions and schemas cost roughly 260 tokens of context every time the server is loaded.

Is the io.github.ExpertVagabond/volcengine MCP server still maintained?

io.github.ExpertVagabond/volcengine is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.ExpertVagabond/volcengine MCP server under?

io.github.ExpertVagabond/volcengine declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.ExpertVagabond/volcengine MCP server?

VerifyMCP ran 16 checks on io.github.ExpertVagabond/volcengine, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.