Skip to main content
Glama

wallet-verifier-mcp

by com.wallet-connectors
OverviewDiscussionsAdmin

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over 42 days
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
TalaoDAO/connectors
GitHub Stars
0
Server Listing
Wallet4Agent MCP Server

TDQS

B3.4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap. The tool has a clearly defined purpose of creating an account.

Naming Consistency5/5

The tool name 'create_account' follows the standard verb_noun pattern, which is clear and conventional. There are no other tools to create inconsistency.

Tool Count2/5

The server has only one tool, which is too few for its apparent scope. Given the name 'wallet-verifier-mcp', one would expect verification tools beyond just account creation, making the count inadequate.

Completeness1/5

The server's purpose, as implied by its name, is wallet verification, but the only tool creates accounts. There are no verification, lookup, or management tools, leaving the surface severely incomplete.

Available Tools

1 tool
create_accountBInspect

Create aan account for a human or a company. This tool will generate a decentralized identifier(DID) and a data wallet.

ParametersJSON Schema
NameRequiredDescriptionDefault
profileNoIdentity ecosystem profile or regulationDIIP V3
did_methodNoOptional DID Method, did:web (DNS based) by default or did:cheqd (blockchain based)did:cheqd
account_typeNoHuman or Company as a the owner of the Agentshuman
notification_emailYesEmail used for notification and authentication. Email must be confirmed to make the account active

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses that the tool generates a DID and data wallet as side effects, which provides some behavioral transparency. However, it omits details such as the email confirmation requirement (mentioned only in the schema), idempotency, failure modes, or reversibility. Without annotations, the description carries a partial burden but does not fully address these aspects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured, with the primary action front-loaded in the first sentence and supporting detail in the second. Every word earns its place, despite the minor typo 'aan'. It is appropriately sized for the tool's simplicity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is incomplete for the tool's complexity. It does not mention the return value (no output schema exists), the email confirmation process, or potential failure scenarios. The schema covers parameters, but the description lacks operational context that would allow an agent to fully anticipate the tool's behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, all four parameters are already documented in the input schema. The tool description adds no additional parameter-specific meaning, so it relies on the schema. The baseline of 3 applies because the schema fully covers parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: to create an account for a human or company, and explicitly mentions it generates a decentralized identifier (DID) and a data wallet. The verb 'Create' and resource 'account' are specific, making the purpose unambiguous even without sibling tools to distinguish from.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to use this tool versus alternatives, nor any prerequisites or contextual hints. It simply states what it does, leaving the agent without information about appropriate usage scenarios or any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedcreate_account1 field changed
      • addedInput schema / properties / profile
        Added value: +{
+  "default": "DIIP V3",
+  "description": "Identity ecosystem profile or regulation",
+  "enum": [
+    "DIIP V3",
+    "EUDIW",
+    "EBSI",
+    "DIIP V5"
+  ],
+  "type": "string"
+}
  2. 1 tool update
    • First observedcreate_account

Related MCP Connectors

Related MCP Servers

  • agent-guardrail

    rudimentall1
    A
    license
    A
    quality
    A
    maintenance
    MCP server for AI agent guardrails — validates and signs agent decisions (OAA tokens) so third parties can verify them without server access
    3
    24 PyPI
    1
    MIT

  • aip-identity

    The-Nexus-Guard
    A
    license
    A
    quality
    D
    maintenance
    MCP server for AI agent identity — verify agents with Ed25519 signatures, check trust scores, sign and verify content, exchange encrypted messages. Built on the Agent Identity Protocol (AIP).
    8
    MIT

  • idm-mcp

    fcapub
    F
    license
    A
    quality
    B
    maintenance
    Mock identity-management MCP server for decentralized identity that allows minting DIDs, issuing signed Verifiable Credentials, and verifying them.
    8
    -
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources