// MCP SERVER RECORD

Yafldev

Unverified
NPM@yafldev/mcp
DRisk gradehigh blast radius
Catalogue entry updated 2 days ago
Auth postureNot probedno remote endpoint probed yet
Tools51 Destructive · 1 Write · 3 Read
Worst categoryDestructivegrade tracks the peak, not the average
Capability mix
Destructive 1Write 1Read 3
What it can reach
Ingests untrusted inputTouches secretsReaches networkRuns codeTouches filesChanges permissionsSends external commsPersistsDeletes dataMoves money
Exfiltration pathReads content an attacker can plant and can send data outward — a prompt-injection-to-exfiltration route.
Tools 5
delete_fileDestructiveCriticalupload_fileWriteMediumdownload_fileReadLowget_statusReadLowlist_filesReadLow These definitions cost 859 tokens of context →
Change history
No change history on record for this server.
Recommended policy
delete_filedeny
upload_filerate limit
Read-only toolsallow
Full policy breakdown with enforcement rules →
// RUNNING THIS SERVER
DIRECT INSTALL npx -y @yafldev/mcp

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.