An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Bcrypt Hash Engine to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Store passwords safely and verify logins instantly.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 2 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-02

2 capabilities in this set.

Part of 2 available through bcryptjs.

  1. 01

    Bcrypt hash

    This capability hashes a password using bcrypt. It handles the salt and lets you configure the computational cost (salt rounds) to meet specific security requirements.

  2. 02

    Bcrypt verify

    Use this capability to check if a provided password matches a stored hash. It returns a simple boolean result, which is the only reliable way to verify bcrypt credentials.

Real work

What teams actually run

01

User Registration

When a new user signs up, the agent calls this MCP to hash the password using the appropriate salt rounds before creating the user record.

02

Login Attempt

The agent takes the provided password and the stored hash, then calls the verification capability to return a simple true/false match result.

03

Compliance Audit

If a compliance officer mandates a higher security level, the agent can re-hash the password using a higher salt round count.

04

Data Migration

When moving old user data, the agent can process and re-hash passwords to ensure they meet current security standards.

Automate a task

Put bcryptjs to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

bcryptjs works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put bcryptjs to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

946ms average. Fast in production.

bcryptjs is checked daily against the live service.

Daily averagePeak 1220ms
Oct 3Today
Fastest day
728ms
Slowest day
1220ms
14-day trend
Slowing+22%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 2 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of bcryptjs, so you can see the experience inside your AI.

It does not authenticate your account with bcryptjs. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

bcryptjs Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_VgRCSgyjUOAZXasfzN85yyaKf89xFObklBU0TrT8/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — bcryptjs capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "bcrypt-hash-engine-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_VgRCSgyjUOAZXasfzN85yyaKf89xFObklBU0TrT8/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up bcryptjs in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work bcryptjs owners hand off.

This MCP is essential for developers, security engineers, and backend architects. If your application handles user accounts, you need this capability to ensure credentials are never stored in plaintext. It lets your AI client perform cryptographic operations that are reliable and compliant.

  • 01

    Backend Developer

    Needs to securely hash and verify passwords during user registration and login flows.

  • 02

    Security Engineer

    Uses this MCP to enforce industry best practices for password storage and compliance.

  • 03

    DevOps Architect

    Integrates secure, pure JavaScript components into complex, multi-runtime authentication systems.

FAQ

Questions bcryptjs owners ask.

  • 01

    Why is bcrypt better than just hashing the password in my code?

    Bcrypt is the industry standard because it includes a built-in salt and is intentionally slow. This design makes it much harder for attackers to brute-force passwords, which simple hashing functions don't account for.

  • 02

    Does this MCP require any complex setup or compilation?

    No. It uses pure JavaScript, which means you don't have to deal with native compilation headaches or complex runtime dependencies.

  • 03

    How do I change the security level?

    You can configure the salt rounds when hashing. The default is 10, but you can increase it to 12 or higher for systems that require greater security, like financial applications.

  • 04

    Can I verify a password against a hash?

    Yes. The bcrypt_verify capability handles this. You pass the password and the stored hash, and it returns a simple boolean indicating if the match is valid.

  • 05

    Why bcrypt instead of SHA-256 or MD5 for passwords?

    SHA-256 and MD5 are fast. that's the problem. An attacker can try billions of hashes per second. Bcrypt is intentionally slow (configurable via salt rounds), making brute-force attacks economically infeasible.

  • 06

    What salt rounds should I use for a financial application?

    12 minimum. Each additional round doubles the computation time. 10 = ~100ms, 12 = ~400ms, 14 = ~1.6s. Balance security vs. login latency for your use case.

  • 07

    Can I verify a password without knowing the salt?

    Yes. that's the beauty of bcrypt. The salt is embedded in the hash string itself ($2a$10$...). Just pass the password and the stored hash to bcrypt_verify.

Explore

More in Security

Suggestions

Connect bcryptjs to Claude, Cursor, ChatGPT & more