com.wallet-connectors/wallet-verifier-mcp
REMOTE · WALLET-CONNECTORS.COM · SCANNED SEP 24
MCP server for verifying EUDI/Talao wallet data via OIDC4VP (pull) for AI agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 159 tokens (~79/item across 2 items; 1 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the com.wallet-connectors/wallet-verifier-mcp server?
com.wallet-connectors/wallet-verifier-mcp is a hosted endpoint at https://wallet-connectors.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · wallet-connectors.com
claude mcp add --transport http com-wallet-connectors-wallet-verifier-mcp 'https://wallet-connectors.com/mcp'
{
"mcpServers": {
"com-wallet-connectors-wallet-verifier-mcp": {
"url": "https://wallet-connectors.com/mcp"
}
}
} {
"servers": {
"com-wallet-connectors-wallet-verifier-mcp": {
"type": "http",
"url": "https://wallet-connectors.com/mcp"
}
}
} [mcp_servers.com-wallet-connectors-wallet-verifier-mcp] url = "https://wallet-connectors.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-wallet-connectors-wallet-verifier-mcp": {
"type": "remote",
"url": "https://wallet-connectors.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-wallet-connectors-wallet-verifier-mcp --url 'https://wallet-connectors.com/mcp' --transport streamable-http
mcp_servers:
com-wallet-connectors-wallet-verifier-mcp:
url: "https://wallet-connectors.com/mcp" {
"McpServers": {
"com-wallet-connectors-wallet-verifier-mcp": {
"Transport": "http",
"Url": "https://wallet-connectors.com/mcp"
}
}
} assistant mcp add com-wallet-connectors-wallet-verifier-mcp -t streamable-http -u 'https://wallet-connectors.com/mcp'
{
"mcpServers": {
"com-wallet-connectors-wallet-verifier-mcp": {
"type": "http",
"url": "https://wallet-connectors.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 78
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://wallet-connectors.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wallet-connectors.com | CN=YE1,O=Let's Encrypt,C=US | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 50af75fa0c18e14c07668af78af6c0007ad |
| SANs: wallet-connectors.com, wallet4agent.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of wallet-connectors.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| wallet-connectors.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wallet-connectors.com/mcp | Verified | 200 | |
| http (plaintext) | http://wallet-connectors.com/mcp | HTTPS enforced | 301 | https://wallet-connectors.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_account ~116
Create aan account for a human or a company. This tool will generate a decentralized identifier(DID) and a data wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| account_type | string | – | Human or Company as a the owner of the Agents |
| did_method | string | – | Optional DID Method, did:web (DNS based) by default or did:cheqd (blockchain based) |
| notification_email | string | yes | Email used for notification and authentication. Email must be confirmed to make the account active |
| profile | string | – | Identity ecosystem profile or regulation |
No output schema declared.
No examples provided.
What is the com.wallet-connectors/wallet-verifier-mcp server?
com.wallet-connectors/wallet-verifier-mcp is listed in the public MCP registry as com.wallet-connectors/wallet-verifier-mcp. MCP server for verifying EUDI/Talao wallet data via OIDC4VP (pull) for AI agents. This page covers its hosted endpoint (https://wallet-connectors.com/mcp).
Is the com.wallet-connectors/wallet-verifier-mcp server safe to use?
com.wallet-connectors/wallet-verifier-mcp scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.wallet-connectors/wallet-verifier-mcp server expose?
com.wallet-connectors/wallet-verifier-mcp exposes 1 tool: create_account. Their descriptions and schemas cost roughly 116 tokens of context every time the server is loaded.
Does the com.wallet-connectors/wallet-verifier-mcp server require authentication?
No. We connected to com.wallet-connectors/wallet-verifier-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.wallet-connectors/wallet-verifier-mcp server still maintained?
com.wallet-connectors/wallet-verifier-mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.