pulsemcp verified Safe content atomic mcp-remote

Tafa (File System)

This MCP server provides fast and efficient file system operations for Claude Desktop integration, built by the Tafa MCP Team using Node.js with comprehensive security features including path validation, permission checks, and automatic backup creation. The implementation offers complete file management capabilities including read/write operations, directory management, advanced search with pattern matching and content search, batch operations like compression and extraction, duplicate detection, and file organization tools. Built with sandboxed execution, configurable allowed directories, and Docker support, it serves developers needing secure file system automation through AI assistants, teams requiring programmatic file management with safety controls, and users wanting to leverage Claude's capabilities for organizing, searching, and manipulating files across their desktop environment with enterprise-grade security controls.

Cognium trust score

79%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.

Scan details: Circle-IR · 2026-09-28 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: cloud-infra
Source: PulseMCP
Repository: github.com/n3urax/tafa-mcp
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve Tafa (File System) from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"