A
licenseA
qualityA
maintenanceMCP server for AI agent guardrails — validates and signs agent decisions (OAA tokens) so third parties can verify them without server access
3
1
MIT
wallet-verifier-mcp
Server Details
MCP server for verifying EUDI/Talao wallet data via OIDC4VP (pull) for AI agents.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- TalaoDAO/connectors
- GitHub Stars
- 0
- Server Listing
- Wallet4Agent MCP Server
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
B3.4/5.0
Tool DescriptionsB
Average 3.4/5 across 1 of 1 tools scored.
Server CoherenceB
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 toolcreate_accountBInspect
Create aan account for a human or a company. This tool will generate a decentralized identifier(DID) and a data wallet.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| profile | No | Identity ecosystem profile or regulation | DIIP V3 |
| did_method | No | Optional DID Method, did:web (DNS based) by default or did:cheqd (blockchain based) | did:cheqd |
| account_type | No | Human or Company as a the owner of the Agents | human |
| notification_email | Yes | Email used for notification and authentication. Email must be confirmed to make the account active |
Tool Definition Quality
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP 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).8MIT
- Alicense-qualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.MIT
- FlicenseAqualityBmaintenanceMock identity-management MCP server for decentralized identity that allows minting DIDs, issuing signed Verifiable Credentials, and verifying them.8
Try in Browser
Your Connectors
Sign in to create a connector for this server.