CursorIDE

Dynamic (Web3 Auth) MCP Server

Bring Web3 Authentication
to Cursor

Name: Dynamic (Web3 Auth) MCP Server
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

Learn how to connect Dynamic (Web3 Auth) to Cursor and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Check SanctionsDelete UserGet Embedded Wallet VersionsGet Event TypesGet Token BalancesGet UserGet WebhooksRevoke Session

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the Dynamic (Web3 Auth) MCP Server?

Connect your Dynamic environment to any AI agent to streamline Web3 user management and security workflows through natural conversation.

What you can do

User Management — Fetch detailed user profiles or permanently delete users from specific environments using get_user and delete_user.
Security & Compliance — Use check_sanctions to verify if specific wallet addresses are sanctioned across multiple chains (ETH, SOL, EVM, etc.).
Session Control — Instantly terminate active user sessions with revoke_session to maintain environment security.
Infrastructure Monitoring — List active embedded wallet versions and configured webhooks to audit your auth setup.
Financial Insights — Retrieve real-time token balances for users across different networks using get_token_balances.

How it works

Subscribe to this server
Enter your Dynamic API Token
Start managing your Web3 auth layer from Claude, Cursor, or any MCP-compatible client

Who is this for?

Web3 Developers — Debug user profiles and check token balances directly from your code editor.
Security & Ops Teams — Audit wallet sanctions and revoke suspicious sessions instantly without opening the dashboard.
Product Managers — Monitor webhook configurations and available event types to coordinate feature releases.

Built-in capabilities (8)

check_sanctions

Check wallet sanctions

delete_user

Delete a user from an environment

get_embedded_wallet_versions

Get active embedded wallet versions

get_event_types

Get available event types

get_token_balances

Get token balances for a user

get_user

Get a user by ID in an environment

get_webhooks

Get configured webhooks

revoke_session

Revoke an active user session

Why Cursor?

Cursor's Agent mode turns Dynamic (Web3 Auth) into an in-editor superpower. Ask Cursor to generate code using live data from Dynamic (Web3 Auth) and it fetches, processes, and writes. all in a single agentic loop. 8 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

—
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
—
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
—
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
—
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

See it in action

Dynamic (Web3 Auth) in Cursor

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

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

Teams that connect Dynamic (Web3 Auth) to Cursor 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 catalog	Find and host yourself	4,000+ managed
Infrastructure	Self-hosted	Sandboxed V8 isolates
Credential handling	Plaintext in config	Vault + runtime injection
Data loss prevention	None	Configurable DLP policies
Kill switch	None	Global instant shutdown
Financial circuit breakers	None	Per-server limits + alerts
Audit trail	None	Ed25519 signed logs
SIEM log streaming	None	Splunk, Datadog, Webhook
Honeytokens	None	Canary alerts on leak
Custom domains	Not applicable	DNS challenge verified
GDPR compliance	Manual effort	Automated purge + export

Unlock for AI Agents View step-by-step setup guide for Cursor →

Enterprise Security

Why teams choose Vinkius for Dynamic (Web3 Auth) in Cursor

The Dynamic (Web3 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 8 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Cursor 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.

Unlock for AI Agents View full Dynamic (Web3 Auth) details →

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
Dynamic (Web3 Auth) for Cursor

Every tool call from Cursor to the Dynamic (Web3 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

Can I check if a specific wallet address is sanctioned before onboarding a user?

Yes! Use the check_sanctions tool by providing the wallet address and the chain (e.g., ETH, SOL). The agent will return the sanction status for that environment.

How do I retrieve the token balances for a user across different networks?

Simply use the get_token_balances tool. You'll need to provide the environment ID, user ID, and an array of balance requests specifying the address and chain.

Is it possible to terminate a suspicious user session immediately?

Yes. Use the revoke_session tool with the specific session ID. This will instantly invalidate the session and disconnect the user.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.