// MCP SERVER RECORD

Otoinstall

Unverified
NPMotoinstall-mcp-server
DRisk gradehigh blast radius
Catalogue entry updated 7 days ago
Auth postureNot probedno remote endpoint probed yet
Tools92 Execute · 1 Write · 6 Read
Worst categoryExecutegrade tracks the peak, not the average
Capability mix
Execute 2Write 1Read 6
What it can reach
Ingests untrusted inputTouches secretsReaches networkRuns codeTouches filesChanges permissionsSends external commsPersistsDeletes dataMoves money
Tools 9
deploy_projectExecuteHighdeploy_zipExecuteHighadd_serverWriteHighanalyze_projectReadLowcheck_deploy_statusReadLow
View all 9 tools
get_deploy_logsReadLowlist_projectsReadLowlist_serversReadLowwhoamiReadLow
Change history
No changes recorded since first scan. Watched servers surface a diff within the hour.
Recommended policy
deploy_projectrequire approval
add_serverrate limit
Read-only toolsallow
Full policy breakdown with enforcement rules →
// RUNNING THIS SERVER
DIRECT INSTALL npx -y otoinstall-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.