Web3Auth MCP server
5 tools · Last check that passed 27 Oct 2026, 01:50 UTC
Web3Auth's own remote MCP server for MetaMask Embedded Wallets gives a coding agent search across the SDK documentation, complete example projects, SDK types and the MetaMask Builder Hub. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 5 tools
| Tool | Counted as |
|---|---|
get_example | Changes things |
get_doc | Said to only read |
get_sdk_reference | Said to only read |
search_community | Said to only read |
search_docs | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
12 of the last 12 checks passed
A check passes when the server lists its tools. Checked at https://mcp.web3auth.io/.
Recent changes
No change seen across the last 12 checks that passed.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Web3Auth's tools change.
One email when Web3Auth's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- Its get_example tool returns the complete source code of integration examples, which an agent may copy into a wallet integration. Web3Auth's MCP server README
- Builder Hub posts written by other users, documentation and example code come back to the agent as text, and text an agent reads can carry instructions for it. OWASP, prompt injection
How to limit it
With Web3Auth's own settings, as its documentation describes them. Stackduke has not tested them.
- We recommend reviewing example code and SDK snippets before they go into a wallet integration, since get_example returns whole projects for the agent to work from. Web3Auth's MCP server README
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.