Bring Web3 Authentication
to VS Code Copilot
Learn how to connect Dynamic (Web3 Auth) to VS Code Copilot 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 SubscribersCompatible with every major AI agent and IDE
Gemini
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_useranddelete_user. - Security & Compliance — Use
check_sanctionsto verify if specific wallet addresses are sanctioned across multiple chains (ETH, SOL, EVM, etc.). - Session Control — Instantly terminate active user sessions with
revoke_sessionto 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 wallet sanctions
Delete a user from an environment
Get active embedded wallet versions
Get available event types
Get token balances for a user
Get a user by ID in an environment
Get configured webhooks
Revoke an active user session
Why VS Code Copilot?
GitHub Copilot Agent mode brings Dynamic (Web3 Auth) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 8 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Dynamic (Web3 Auth) in VS Code Copilot
Dynamic (Web3 Auth) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Dynamic (Web3 Auth) to VS Code Copilot 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.
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 |
Why teams choose Vinkius for Dynamic (Web3 Auth) in VS Code Copilot
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 VS Code Copilot 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.
* 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
How Vinkius secures
Dynamic (Web3 Auth) for VS Code Copilot
Every tool call from VS Code Copilot to the Dynamic (Web3 Auth) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
NationBuilder
12 toolsOrganize communities, run campaigns, and mobilize supporters with a platform built for political and nonprofit leadership.
Correios API (REST)
2 toolsTrack Brazilian postal objects and calculate shipping prices and deadlines directly through the official Correios REST API.
Sansan
8 toolsDigitize and manage business cards via AI — browse contacts, verify details, and explore your company's network effortlessly.
Snov.io
8 toolsEquip your AI agent with direct access to Snov.io — find emails, verify addresses, automate drip campaigns, and manage prospect lists without opening the Snov dashboard.