BlobsVault Reviews and Details

Questions & Answers

1. Why should a person choose BlobsVault over its competitors?

   No other 2FA manager offers an MCP server, per-agent scoped keys, or a REST API designed for programmatic access. Google Authenticator, Authy, and 2FAS are all built for humans — none of them can be connected to an AI agent, CI/CD pipeline, or automation script without dangerous workarounds.

   BlobsVault is also architecturally zero-knowledge. Unlike most competitors, we cannot decrypt your vault even if we wanted to — the master password never leaves your device.

   For teams, per-member encryption means no central point of compromise. For developers, the open-source MCP server and SDKs mean you can audit the implementation before connecting your agents.

2. How would you describe the primary audience of BlobsVault?

   BlobsVault serves three main audiences:

   1. AI builders — developers building agents with Claude, Cursor, or any MCP-compatible tool that need 2FA access without manual intervention or hardcoded secrets.

   2. DevOps and platform engineers — teams running CI/CD pipelines, automation scripts, and infrastructure tools that need programmatic TOTP generation via REST API or CLI.

   3. Security-conscious individuals and small teams — people who want a 2FA manager where the provider genuinely cannot read their secrets, with team sharing and audit logs.

3. Which are the primary technologies used for building BlobsVault?

   Frontend: React, Vite, Tailwind CSS Backend: Node.js, Express Database: PostgreSQL Infrastructure: Docker, Nginx, Let's Encrypt SSL, Contabo VPS Payments: Paddle Email: Zoho SMTP Authentication: Passport.js (Google and GitHub OAuth) MCP Server: open source, MCP protocol SDKs: Python, Node.js — open source on GitHub CLI: blobsvault-cli on npm Encryption: AES-256 client-side, PBKDF2 key derivation

4. Who are some of the biggest customers of BlobsVault?

   BlobsVault is an early-stage product launched in 2026. We are not disclosing specific customers at this time. Our current users include individual developers and AI builders using the MCP server and REST API to give their agents secure 2FA access.

5. What makes BlobsVault unique?

   BlobsVault is the only 2FA manager built specifically for AI agents and programmatic access.

   Every other authenticator app is designed for humans tapping phones. BlobsVault is designed for code.

   Three things make it unique: a native MCP server (Claude, Cursor, and any MCP-compatible agent generates 2FA codes natively), per-agent scoped identities (each agent gets its own bvagent* key restricted to specific accounts, tracked, and revokable independently), and zero-knowledge encryption (AES-256 client-side — the server only ever stores ciphertext). The MCP server, SDKs, and decoder are open source on GitHub.

6. What's the story behind BlobsVault?

   BlobsVault started from a problem I kept hitting while building AI agents: services protected by 2FA would stop the agent cold. Every authenticator app is designed for humans — there was nothing built for code.

   I wanted a solution where each agent gets its own identity, with scoped access, audit trails, and instant revocation. And because 2FA secrets are extremely sensitive, I also wanted zero-knowledge encryption — where the architecture makes it impossible for the provider to read your secrets, not just a promise in a privacy policy.

   I built BlobsVault solo from Madagascar. It's my first SaaS product, and the MCP + agent identity model is what I wish had existed when I started building agents.