Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://wallet-connectors.com/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http com.wallet-connectors-wallet-verifier-mcp https://wallet-connectors.com/mcpRun in a terminal.
{ "mcpServers": { "com.wallet-connectors-wallet-verifier-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://wallet-connectors.com/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
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.
MCP server for verifying EUDI/Talao wallet data via OIDC4VP (pull) for AI agents.
AI Agents increasingly take actions, access data, and collaborate.
To do this safely, they must be able to:
Wallet4Agent provides AI Agents with:
Everything is standards‑based and interoperable.
Wallet4Agent is built with three coordinated layers:
POST https://wallet4agent.com/mcpManages:
Supports:
All complex cryptographic and identity logic stays in Wallet4Agent.
Your agent simply calls MCP tools.
Each AI Agent receives a Decentralized Identifier (DID) compliant with the W3C DID Core specification.
Wallet4Agent supports two DID methods:
A DID anchored on a domain.
did:web:wallet4agent.com:<agent-id>
⭐ Characteristics:
https://wallet4agent.com/did/<agent-id>🔗 DID:web specification:
https://www.w3.org/TR/did-spec-registries/#did-method-web
A DID anchored on the Cheqd decentralized ledger.
did:cheqd:<network>:<identifier>
⭐ Characteristics:
🔗 DID:cheqd specification:
https://docs.cheqd.io/identity/
Regardless of DID method, the DID Document exposes:
DID Documents are automatically updated when:
External agents and services use the DID Document to verify signatures, credentials, and linked proofs.
Linked VP allows Wallet4Agent to publish verifiable credentials inside the DID Document as references.
Why this matters:
Supported formats:
Specification:
https://identity.foundation/linked-vp/spec/v1.0.0/
Each agent has a dedicated cloud KMS key.
Used for:
Benefits:
Developers may register additional public JWKs:
private_key_jwtWallet4Agent stores the public keys; developers retain the private keys.
Wallet4Agent supports three agent authentication flows:
Authorization: Bearer <agent_pat>
Simple and effective for development or local agents.
Agent receives:
client_id = Agent DIDclient_secretThen exchanges using:
grant_type=client_credentials
Ideal for most production requests.
Strongest method:
Useful for hardware-backed keys and enterprise infrastructures.
Wallet4Agent handles complete credential issuance flows:
Supported formats:
Agents only call MCP tools — Wallet4Agent does all protocol-level work.
Wallet4Agent supports verification of:
Agents can:
The agent never sees sensitive tokens; only derived, safe claims are returned.
Wallet4Agent stores credentials as attestations, including:
Agents can:
Published under:
/.well-known/oauth-protected-resource/mcp
Includes:
Enables automatic configuration by OAuth2 clients and gateways.
Wallet4Agent supports human-in-the-loop requirements:
{
"always_human_in_the_loop": true
}
Used for:
If you are an Agent developer, Wallet4Agent gives you:
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.
© 2026 MCP Directory.
MCP server for verifying EUDI/Talao wallet data via OIDC4VP (pull) for AI agents.
{ "mcpServers": { "com.wallet-connectors-wallet-verifier-mcp": { "url": "https://wallet-connectors.com/mcp", "headers": {} } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Wallet Verifier is reached over HTTP.
Last checked 2026-11-08. MCP server for verifying EUDI/Talao wallet data via OIDC4VP (pull) for AI agents.