HN Showcase
Back to browse
MCP-enabled file storage for AI agents, auth via Ethereum wallet

MCP-enabled file storage for AI agents, auth via Ethereum wallet

by womd·Feb 25, 2026·2 points·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidWizardryNiche Gem

Clever FTP-as-backbone for MCP storage, but wallet auth is niche friction for most teams.

Strengths
  • •Dual-interface design: AI agents use MCP protocol while humans use standard FTP over TLS concurrently
  • •Ethereum signature auth eliminates password/email overhead, novel credentialing for infra access
  • •Live, deployed service ready to test—not vaporware; demo cost explicitly low to reduce friction
Weaknesses
  • •Wallet authentication is a barrier for non-crypto teams; adds UX complexity vs API keys
  • •MCP is early/emerging standard; unclear if this solves a real persistent storage gap vs simpler alternatives (S3, B2, SFTP)
Target Audience

AI agent developers, enterprises managing file workflows with wallet-native auth

Similar To

Hugging Face Spaces storage · Modal file system API · LangChain agent tools

Post Description

I built a live demo of an MCP (Model Context Protocol) server backed by FTP storage. It lets AI agents manage files — read, write, search, edit, upload — through a structured tool interface, while the same files stay accessible via standard FTP over TLS.

Authentication is wallet-based (Ethereum signatures — no passwords, no email).

Try it: https://service.c33b.org Provision: https://signin.c33b.org

Stack: ProFTPD + custom MCP layer, runs on Linux. Compatible with Claude, Codex, n8n, and any MCP client.

Looking for honest feedback: - Is the concept useful to you, or is this solving a problem that doesn't exist? - What would you want from agent-accessible persistent storage? - Anything that would stop you from trying it?

thx 4 feedback

Similar Projects