Skip to content

MetaMask Embedded Wallets (Web3Auth) MCP server

io.github.Web3Auth/mcp-serverWeb3Authstreamable-httpv2.0.0Scanned

Helps AI coding agents integrate MetaMask Embedded Wallets (Web3Auth) SDKs.

5 tools: 5 only read.

Tools: 0 delete, 0 irreversible, 0 write, 5 read.
  • Reads private data · 3
  • Reads text others write · 5
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the MetaMask Embedded Wallets (Web3Auth) MCP server can do

The MetaMask Embedded Wallets (Web3Auth) MCP server is published by the GitHub account Web3Auth. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

3 tools read private data (search_docs, get_doc and get_sdk_reference); 5 tools bring in text other people can write (search_docs, get_doc, get_example and 2 more); 1 tool can send data out of your system (get_doc). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 2.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Only reads 5Show 5 read-only tools
  • get_docFetch the full content of a MetaMask Embedded Wallets documentation page by URL.Reads private dataReads text others writeCan send data outNo findings

    Why it is in this group

    • The name "get_doc" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_doc" says "get" and "doc": it reads documents.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Fetch the full content of a MetaMask Embedded Wallets documentation page by URL. Sources: Algolia, llms.txt, GitHub MDX.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • get_exampleFetch complete source code of a Web3Auth integration example from GitHub.Reads text others writeNo findings

    Why it is in this group

    • The name "get_example" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Fetch complete source code of a Web3Auth integration example from GitHub.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • get_sdk_referenceFetch SDK source code (types, interfaces, hooks) from open-source Web3Auth repos.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_sdk_reference" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "repo": it reads repositories.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Fetch SDK source code (types, interfaces, hooks) from open-source Web3Auth repos.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • search_communitySearch or fetch posts from the MetaMask Embedded Wallets community forum (builder.metamask.io).Reads text others writeNo findings

    Why it is in this group

    • The name "search_community" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "search" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Search or fetch posts from the MetaMask Embedded Wallets community forum (builder.metamask.io).

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • search_docsSearch MetaMask Embedded Wallets documentation (Algolia) and example projects.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "search_docs" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_docs" says "search" and "doc": it reads documents.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Search MetaMask Embedded Wallets documentation (Algolia) and example projects. Returns doc page links with snippets and matching examples.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

15 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__web3auth__get_doc"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:01 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 2.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http web3auth https://mcp.web3auth.io
claude mcp add --transport http web3auth https://mcp.web3auth.io

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__web3auth__search_docs",
      "mcp__web3auth__get_example",
      "mcp__web3auth__get_sdk_reference",
      "mcp__web3auth__search_community"
    ],
    "ask": [
      "mcp__web3auth__get_doc"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as web3auth. Review it before you use it.

Capability tags behind 5 rules
  • mcp__web3auth__search_docs private-data, untrusted-input
  • mcp__web3auth__get_doc private-data, untrusted-input, outbound
  • mcp__web3auth__get_example untrusted-input
  • mcp__web3auth__get_sdk_reference private-data, untrusted-input
  • mcp__web3auth__search_community untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Web3Auth/mcp-server/verify?hash=f32bc7e08944765a5ebb3ea846e0864f1b000aaf00a86107ae0bcd17f8627938" | jq -e '.changed == false'

Pinned hash f32bc7e08944, from Nov 16, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Web3Auth/mcp-server/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Web3Auth/mcp-server
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Web3Auth/mcp-server.svg)](https://radar.anlyon.com/servers/io.github.Web3Auth/mcp-server)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:22 UTC.

MetaMask Embedded Wallets (Web3Auth) MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the MetaMask Embedded Wallets (Web3Auth) MCP server safe?

No scan can promise that. What its definitions show: 5 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the MetaMask Embedded Wallets (Web3Auth) MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the MetaMask Embedded Wallets (Web3Auth) MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the MetaMask Embedded Wallets (Web3Auth) MCP server have?

5 tools: 5 read. search_docs, get_doc, get_example, get_sdk_reference and search_community.

Does the MetaMask Embedded Wallets (Web3Auth) MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the MetaMask Embedded Wallets (Web3Auth) MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): get_doc.

Has the MetaMask Embedded Wallets (Web3Auth) MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.