// MCP SERVER RECORD

Filesystem

Verified
REPOmodelcontextprotocol/server-filesystemNPM@modelcontextprotocol/server-filesystem
DRisk gradehigh blast radius
Last checked 15 days ago·Live handshake·Watched hourly for changes
Auth postureNot probedno remote endpoint probed yet
Tools144 Write · 10 Read
Worst categoryWritegrade tracks the peak, not the average
Capability mix
Write 4Read 10
What it can reach
Ingests untrusted inputTouches secretsReaches networkRuns codeTouches filesChanges permissionsSends external commsPersistsDeletes dataMoves money
Tools 14
create_directoryWriteLowedit_fileWriteHighmove_fileWriteMediumwrite_fileWriteHighdirectory_treeReadLow
View all 14 tools
get_file_infoReadLowlist_allowed_directoriesReadLowlist_directoryReadLowlist_directory_with_sizesReadLowread_fileReadLowread_media_fileReadLowread_multiple_filesReadLowread_text_fileReadLowsearch_filesReadLow
These definitions cost 1,666 tokens of context →
Change history
No change history on record for this server. Watched servers surface a diff within the hour.
Recommended policy
write_filerequire approval
edit_filerequire approval
create_directoryrequire approval
move_filerequire approval
Read-only toolsallow
Full policy breakdown with enforcement rules →

This record as markdown: /tools/filesystem.md — append .md to any tool or server page.

// RUNNING THIS SERVER
DIRECT INSTALL npx -y @modelcontextprotocol/server-filesystem

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.