MCP server for verifying EUDI/Talao wallet data via OIDC4VP (pull) for AI 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. 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 🔐…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
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. 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…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.