Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Wallet Verifier MCP

✓ wallet-connectors.com

by TalaoDAOversion 1.1.0i★ 0iRuns in the cloudOfficial site ↗
Registry namecom.wallet-connectors/wallet-verifier-mcp

How to install

What it does

MCP server for verifying EUDI/Talao wallet data via OIDC4VP (pull) for AI agents.

  • Connects Runs in the cloud
  • Account or key No key needed
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness3/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score3/100

Quality: Passed 1/4 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Passed 1/4 checks · Runs on your computer

We hid some of the commands

Connect by URL: the server address did not answer when we checked

No install path has passed yet. See the maker’s instructions or pick another server in this category · Maker’s install instructions · Others in this category

First: which AI do you use?

Pick your app and the steps appear below.

Claude cannot connect Wallet Verifier MCP yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

ChatGPT cannot connect Wallet Verifier MCP yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

What you can do instead

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Claude Code cannot connect Wallet Verifier MCP yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

Cursor cannot connect Wallet Verifier MCP yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

VS Code cannot connect Wallet Verifier MCP yet

No install path has passed yet. See the maker’s instructions or pick another server in this category

No install path has passed yet. See the maker’s instructions or pick another server in this category

Stuck? Ask people who use Wallet Verifier MCP💬 Discussion →

At a glance

Downloads per weeki
Not on npm/PyPI
Verified domain
✓ wallet-connectors.com
Licencei
Apache-2.0
Connection
Runs in the cloud
Transport
streamable-http
Latest versioni
1.1.0
Categoryi
Other
Published to registryi
Oct 18, 2025
Code last changedi
Mar 10, 2026
Last checked
Nov 16, 2026
Maker
TalaoDAO
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

All apps, with pros and cons →

Related guides

What it can do

The server did not answer when we last checked, so we could not read its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ! Caution

    Maker matches the repo

    The publisher (wallet-connectors.com) is not the repo owner (TalaoDAO); someone else may have listed it

  • ! Caution

    Still maintained

    Code last changed 8 months ago, more than 6 months ago

  • ✓ Pass

    Has a licence

    Uses Apache-2.0

  • ✕ Fail

    Endpoint responds

    Did not respond within 6 seconds when we checked

  • – Not applicable

    Sign-in with OAuth

    Did not respond within 6 seconds when we checked

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/wallet-connectors-wallet-verifier-mcp.svg)](https://mcp.popnx.com/en/servers/wallet-connectors-wallet-verifier-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 0% of the other 20653 servers in this category
  • Published to the registry more recently than 0% of the other 20653 servers in this category
  • Basic checks equal to or better than 5% of the other 20653 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Wallet Verifier MCP safe?

It passed 1 of 4 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed 8 months ago, and the latest version (1.1.0) reached the registry 13 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Wallet Verifier MCP
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks1/44/44/44/41/44/4
LicenseApache-2.0AGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

🏗️ Wallet4Agent — Technical Stack Overview

For developers building trusted AI Agents able to interact with persons, companies, services, and other agents

Wallet4Agent provides the trust layer that AI Agents need to operate safely in the real world. This document explains the technical components, standards, and identity mechanisms behind the platform.


1. 🎯 Purpose of Wallet4Agent

AI Agents increasingly take actions, access data, and collaborate. To do this safely, they must be able to:

  • 🆔 Prove who they are
  • 👤 Prove who owns or controls them
  • 📄 Hold verifiable credentials
  • 🔐 Sign actions and data securely
  • 🔗 Trust users, companies, and other agents
  • 🪪 Authenticate to external systems without fragile API keys

Wallet4Agent provides AI Agents with:

  • A DID-based identity
  • A secure wallet for credentials
  • Cloud KMS-backed signing keys
  • Interoperability with OIDC4VCI, OIDC4VP, SD‑JWT, JSON-LD, OAuth2
  • An MCP server interface for agents

Everything is standards‑based and interoperable.


2. 🧱 Architecture Overview

Wallet4Agent is built with three coordinated layers:

2.1 🖥️ MCP Server (Model Context Protocol)

  • Single endpoint: POST https://wallet4agent.com/mcp
  • Exposes all operations as tools:
  • Identity creation
  • Credential issuance
  • Verification flows
  • Signing operations
  • Configuration

2.2 👛 Identity Wallet

Manages:

  • The Agent’s DID & DID Document
  • Stored credentials (SD‑JWT VC, VC JSON‑LD)
  • Linked Verifiable Presentations
  • Wallet metadata & service endpoints

2.3 🔐 Authorization & Verification Layer

Supports:

  • OAuth2 access tokens
  • OIDC4VCI (credential issuance)
  • OIDC4VP (presentation)
  • User verification flows
  • Agent‑to‑Agent authentication

All complex cryptographic and identity logic stays in Wallet4Agent. Your agent simply calls MCP tools.


3. 🆔 Identity Layer (DID & DID Documents)

Each AI Agent receives a Decentralized Identifier (DID) compliant with the W3C DID Core specification.

Wallet4Agent supports two DID methods:


3.1 🌐 did:web (DNS-based identity)

A DID anchored on a domain.

did:web:wallet4agent.com:<agent-id>

⭐ Characteristics:

  • Easy to resolve using HTTPS
  • DID Document lives at: https://wallet4agent.com/did/
  • Perfect for SaaS agents
  • Human-readable, infrastructure-friendly
  • Works well for corporate or platform-linked AI agents

🔗 DID:web specification: https://www.w3.org/TR/did-spec-registries/#did-method-web


3.2 ⛓️ did:cheqd (ledger-based identity)

A DID anchored on the Cheqd decentralized ledger.

did:cheqd:<network>:<identifier>

⭐ Characteristics:

  • Tamper-resistant DID Document stored on-ledger
  • Supports ledger-anchored keys, rotations, service endpoints
  • Ideal for:
  • High-assurance identity
  • Regulated environments
  • Trust registries
  • Decentralized compliance ecosystems

🔗 DID:cheqd specification: https://docs.cheqd.io/identity/


4. 📄 DID Documents

Regardless of DID method, the DID Document exposes:

  • 🔑 Public keys
  • 🔐 Authentication methods
  • 📌 Service endpoints
  • 🧾 Linked Verifiable Presentations
  • 🧬 Key types (JWK, Ed25519, etc.)

DID Documents are automatically updated when:

  • Keys rotate
  • New developer or agent keys are registered
  • Credentials are published as Linked VPs
  • Authentication methods change

External agents and services use the DID Document to verify signatures, credentials, and linked proofs.


5. 🔗 Linked Verifiable Presentations (Linked VP)

Linked VP allows Wallet4Agent to publish verifiable credentials inside the DID Document as references.

Why this matters:

  • Public credentials become discoverable
  • Third parties can verify agent capabilities
  • Useful for:
  • Corporate mandates
  • Agent capabilities
  • Service trust signals
  • Compliance proofs

Supported formats:

  • 🟦 SD‑JWT VC
  • 🟩 JWT‑VC / JWT‑VP
  • 🟪 JSON‑LD VC / VP

Specification: https://identity.foundation/linked-vp/spec/v1.0.0/


6. 🔐 Cryptography & Key Management

6.1 🗝️ Cloud KMS–backed keys (non-exportable)

Each agent has a dedicated cloud KMS key.

Used for:

  • Signing Verifiable Presentations
  • Proofs of key ownership in OIDC4VCI
  • JWTs for OAuth2 client authentication
  • Internal signature operations

Benefits:

  • Private key never leaves KMS
  • Agent identity is tied to a secure execution environment
  • High‑assurance signatures

6.2 🔑 Developer-supplied keys

Developers may register additional public JWKs:

  • For OAuth private_key_jwt
  • For agent frameworks managing their own keys
  • For corporate signing keys

Wallet4Agent stores the public keys; developers retain the private keys.


7. 🔑 Authentication Methods

Wallet4Agent supports three agent authentication flows:

7.1 🔹 Agent Personal Access Token (PAT)

Authorization: Bearer <agent_pat>

Simple and effective for development or local agents.

7.2 🔹 OAuth2 Client Credentials

Agent receives:

  • client_id = Agent DID
  • client_secret

Then exchanges using:

grant_type=client_credentials

Ideal for most production requests.

7.3 🔹 OAuth2 private_key_jwt

Strongest method:

  • Developer registers a public JWK
  • Agent signs a JWT with its private key
  • Wallet4Agent validates it using the registered public JWK

Useful for hardware-backed keys and enterprise infrastructures.


8. 🧾 Credential Issuance (OIDC4VCI)

Wallet4Agent handles complete credential issuance flows:

  • Fetch issuer metadata
  • Obtain OAuth tokens
  • Create proof of key ownership signed by the agent's KMS key
  • Request credentials
  • Store as attestations

Supported formats:

  • 🟦 SD‑JWT VC
  • 🟩 VC JSON‑LD

Agents only call MCP tools — Wallet4Agent does all protocol-level work.


9. 🧪 Verification (OIDC4VP)

Wallet4Agent supports verification of:

  • Natural persons
  • Other agents
  • Credential-based access

Agents can:

  • Start user verification
  • Poll status
  • Receive verified attributes safely
  • Authenticate peer agents

The agent never sees sensitive tokens; only derived, safe claims are returned.


10. 📦 Credential Storage & Retrieval

Wallet4Agent stores credentials as attestations, including:

  • Format
  • Issuer
  • VCT/VC type
  • Expiry
  • Encrypted payload
  • Publication status (for Linked VP)

Agents can:

  • List their credentials
  • Accept new ones
  • Access credentials of other agents (if published)

11. 🌐 OAuth Protected Resource Metadata

Published under:

/.well-known/oauth-protected-resource/mcp

Includes:

  • Supported authentication methods
  • Resource identifiers
  • Trusted authorization servers

Enables automatic configuration by OAuth2 clients and gateways.


12. 🛡️ Responsible AI Features

Wallet4Agent supports human-in-the-loop requirements:

{

"always_human_in_the_loop": true }

Used for:

  • High-risk operations
  • Sensitive credential acceptance
  • Escalation to human review

🧩 13. Summary for Developers

If you are an Agent developer, Wallet4Agent gives you:

FeatureWhat you get
🆔 Agent identityDID + DID Document
🔑 AuthenticationDev PAT, Agent PAT, OAuth2 Client Credentials, private_key_jwt
🔐 Cryptographic keysCloud KMS signatures, non‑exportable
📜 Credential issuanceFull OIDC4VCI support (SD‑JWT VC & VC JSON‑LD)
✅ Credential verificationOIDC4VP with simple MCP tools and safe derived claims
👤 Human interactionQR code → wallet → verified attributes
🤝 Inter‑agent trustAbility to inspect credentials of other agents (when authorized)
⚙️ ConfigurationAuth mode, keys, policies all manageable via MCP
🛡️ SecurityKMS, OAuth2, DID rotation & key updates, role‑separated tokens

Your AI Agent becomes a verifiable digital entity, capable of participating in decentralized and regulated digital identity ecosystems while preserving security and accountability.


Maintainer: Wallet4Agent (Web3 Digital Wallet / Talao ) For feedback or additional documentation, use the contact channels on the Wallet4Agent website.

StandardPurposeLink
DID CoreCore DID specificationhttps://www.w3.org/TR/did-core/
Linked Verifiable PresentationsPublic VCs in DID Documentshttps://identity.foundation/linked-vp/spec/v1.0.0/
OIDC4VCICredential issuancehttps://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html
OIDC4VPCredential presentationhttps://openid.net/specs/openid-4-verifiable-presentations-1_0.html
W3C Verifiable CredentialsVC Data Modelhttps://www.w3.org/TR/vc-data-model-2.0/
SD-JWT VC (IETF)Selective disclosure credential formathttps://www.ietf.org/archive/id/draft-ietf-oauth-sd-jwt-vc-12.html