// MCP SERVER RECORD

Mcp Shellkeeper

Unverified
NPMmcp-shellkeeper
DRisk gradehigh blast radius
Catalogue entry updated 10 days ago
Auth postureNot probedno remote endpoint probed yet
Tools72 Execute · 2 Write · 3 Read
Worst categoryExecutegrade tracks the peak, not the average
Capability mix
Execute 2Write 2Read 3
What it can reach
Ingests untrusted inputTouches secretsReaches networkRuns codeTouches filesChanges permissionsSends external commsPersistsDeletes dataMoves money
Tools 7
terminal_executeExecuteCriticalterminal_new_sessionExecuteCriticalterminal_close_sessionWriteMediumterminal_upload_fileWriteHighterminal_download_fileReadMedium
View all 7 tools
terminal_get_bufferReadLowterminal_list_sessionsReadLow
Change history
No changes recorded since first scan. Watched servers surface a diff within the hour.
Recommended policy
terminal_executerequire approval
terminal_close_sessionrate limit
Read-only toolsallow
Full policy breakdown with enforcement rules →
// RUNNING THIS SERVER
DIRECT INSTALL npx -y mcp-shellkeeper

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.