4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Hanko (Passkey Auth) MCP Server

Bring Authentication
to CrewAI

Learn how to connect Hanko (Passkey Auth) to CrewAI and start using 15 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Admin Create UserAdmin Get UserAdmin List User CredentialsAdmin List UsersFlow ExecutePasskey Delete CredentialPasskey List CredentialsPasskey Login FinalizePasskey Login InitPasskey Registration FinalizePasskey Registration InitPasskey Transaction FinalizePasskey Transaction InitPublic Get JwksPublic Validate Session

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Hanko (Passkey Auth)

What is the Hanko (Passkey Auth) MCP Server?

Connect your Hanko instance to any AI agent to streamline passkey-based authentication and user management. This server provides a comprehensive interface for WebAuthn flows and administrative user operations.

What you can do

  • Passkey Lifecycle — Initialize and finalize WebAuthn registration and login flows for secure, passwordless access.
  • Credential Management — List and delete registered WebAuthn credentials for specific users.
  • User Administration — Create, retrieve, and list users and their associated credentials via admin tools.
  • Transaction Security — Initialize and finalize passkey-signed transactions for sensitive operations like payments.
  • Session Validation — Publicly validate sessions and retrieve JWKS for token verification.

How it works

  1. Subscribe to this server
  2. Enter your Hanko Tenant ID and API Key
  3. Start managing identity flows from your MCP-compatible client

Who is this for?

  • Developers — quickly test and debug WebAuthn registration and login flows without manual API calls.
  • Security Engineers — audit user credentials and manage identity access policies through a conversational interface.
  • Product Teams — simulate and verify user onboarding and transaction signing workflows.

Built-in capabilities (15)

admin_create_user

Create a new user via Admin API

admin_get_user

Get a user by ID via Admin API

admin_list_user_credentials

List WebAuthn credentials for a user via Admin API

admin_list_users

List users via Admin API

flow_execute

Execute a Hanko Flow action

passkey_delete_credential

Delete a WebAuthn credential

passkey_list_credentials

List WebAuthn credentials for a user

passkey_login_finalize

Finalize a passkey login

passkey_login_init

Returns publicKey options for navigator.credentials.get(). Initialize a passkey login

passkey_registration_finalize

Finalize a passkey registration

passkey_registration_init

Returns publicKey options for navigator.credentials.create(). Initialize a passkey registration

passkey_transaction_finalize

Finalize a passkey transaction

passkey_transaction_init

g., payment confirmation) for an existing user. Initialize a passkey transaction

public_get_jwks

Get JSON Web Key Set (JWKS)

public_validate_session

Validate a Hanko session token

Why CrewAI?

When paired with CrewAI, Hanko (Passkey Auth) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Hanko (Passkey Auth) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Hanko (Passkey Auth) in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Hanko (Passkey Auth) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Hanko (Passkey Auth) to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Hanko (Passkey Auth) in CrewAI

The Hanko (Passkey Auth) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 15 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Hanko (Passkey Auth)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Hanko (Passkey Auth) for CrewAI

Every tool call from CrewAI to the Hanko (Passkey Auth) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How do I start a new passkey registration for a user?

Use the passkey_registration_init tool with the user's ID and username. This will return the necessary WebAuthn options to be used on the client side.

02

Can I view all WebAuthn credentials associated with a specific user?

Yes, you can use the passkey_list_credentials tool (or admin_list_user_credentials for admin access) to retrieve a list of all registered passkeys for any user ID.

03

Is it possible to create a user directly through the AI agent?

Absolutely. Use the admin_create_user tool to provision a new user in your Hanko project by providing a unique user ID.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →