// MCP SERVER RECORD

Vcluster Yaml

Unverified
NPMvcluster-yaml-mcp-server
BRisk grademodest
Catalogue entry updated 6 days ago
Auth postureNot probedno remote endpoint probed yet
Tools71 Write · 6 Read
Worst categoryWritegrade tracks the peak, not the average
Capability mix
Write 1Read 6
What it can reach
Ingests untrusted inputTouches secretsReaches networkRuns codeTouches filesChanges permissionsSends external commsPersistsDeletes dataMoves money
Tools 7
create-vcluster-configWriteMediumextract-validation-rulesReadLowget-changelogReadLowget-server-infoReadLowlist-versionsReadLow
View all 7 tools
smart-queryReadLowvalidate-configReadLow
Change history
No changes recorded since first scan. Watched servers surface a diff within the hour.
Recommended policy
create-vcluster-configrate limit
Read-only toolsallow
Full policy breakdown with enforcement rules →
// RUNNING THIS SERVER
DIRECT INSTALL npx -y vcluster-yaml-mcp-server

Installed this way, nothing enforces the recommended policy above — calls run exactly as the agent makes them.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.