4,000+ servers built on vurb.ts
Vinkius
Google ADKSDK
Google ADK
Dynamic (Web3 Auth) MCP Server

Bring Web3 Authentication
to Google ADK

Learn how to connect Dynamic (Web3 Auth) to Google ADK and start using 8 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
Check SanctionsDelete UserGet Embedded Wallet VersionsGet Event TypesGet Token BalancesGet UserGet WebhooksRevoke Session

Compatible with every major AI agent and IDE

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

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

  1. Subscribe to this server
  2. Enter your Dynamic API Token
  3. 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 Google ADK?

Google ADK natively supports Dynamic (Web3 Auth) as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 8 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

  • Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution

  • Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Dynamic (Web3 Auth)

  • Production-ready features like session management, evaluation, and deployment come built-in. not bolted on

  • Seamless integration with Google Cloud services means you can combine Dynamic (Web3 Auth) tools with BigQuery, Vertex AI, and Cloud Functions

G
See it in action

Dynamic (Web3 Auth) in Google ADK

AI AgentVinkius
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 Google ADK 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 Dynamic (Web3 Auth) in Google ADK

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 Google ADK 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.

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

Every tool call from Google ADK 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

01

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.

02

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.

03

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.

04

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.

05

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.

06

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.

07

McpToolset not found

Update: pip install --upgrade google-adk

Explore More MCP Servers

View all →