MetaMask Embedded Wallets MCP (formerly Web3Auth) gives AI coding assistants live access to Embedded Wallets documentation, SDK references, integration examples, and community troubleshooting. MetaMask Embedded Wallets is not a wallet app itself, but embedded wallet infrastructure that helps developers add non-custodial Web3 wallets to web, mobile, and gaming apps using familiar login methods like Google, GitHub, email, SMS, and other OAuth or passwordless flows. This MCP server is built for real integration work. It lets agents search docs, fetch full documentation pages, retrieve complete example code, inspect SDK types and hooks, and surface real-world implementation issues. It is especially useful for tasks like choosing the right SDK, implementing social login, understanding key derivation behavior, avoiding wallet address changes caused by auth or configuration mistakes, and debugging framework-specific issues across React, Next.js, Flutter, React Native, and other platforms. Use it when you want an AI assistant to generate or review MetaMask Embedded Wallets integrations using current source material instead of stale model memory. Pair it with the MetaMask Embedded Wallets Skill for best results: the skill teaches the assistant how to reason about architecture, authentication, SDK selection, and common pitfalls, while this MCP server provides up-to-date docs, examples, SDK references, and implementation details.

MCP readiness

B · 88/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.2/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (1988 ms).
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	31/31 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 5 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (1988 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness: Higher than 95% of peers; This listing 88 · peer median 81
Latency: Faster than 32% of peers; This listing 490 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Protocol revision −2 — Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-06-04 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/web3auth/integrate/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/web3auth/integrate/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://docs.metamask.io/embedded-wallets/build-with-ai/

Listed at (smithery)

https://docs.metamask.io/embedded-wallets/build-with-ai/