Verdix address risk vs Wealthville Integrations
A side-by-side look at the Verdix address risk and Wealthville Integrations MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
V
Verdix address riskFinance & Fintech · Remote HTTP/SSECheck an EVM address on Base before sending funds: safe/caution/danger. Pays per call via x402.37FairAuth: not declaredVerdict: choose Verdix address risk for finance & fintech work over a hosted endpoint; choose Wealthville Integrations for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
VChoose Verdix address risk when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
Choose Wealthville Integrations when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | V Verdix address risk | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 37/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Paid service | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Verdix address risk | View Wealthville Integrations |
Tools & capabilities
Verdix address risk tools
No tool names declared yet. Check the project README from the listing page.
Wealthville Integrations tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Verdix address risk
{
"mcpServers": {
"verdix-address-risk": {
"url": "https://api.verdixapi.com"
}
}
}
Wealthville Integrations
{
"mcpServers": {
"amitesh-m-wealthville-integrations": {
"command": "npx",
"args": [
"-y",
"@wealthville/mcp-server"
]
}
}
}
Frequently asked questions
Verdix address risk is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. Wealthville Integrations belongs to Finance & Fintech and uses a local stdio subprocess. Pick Verdix address risk for finance & fintech work and Wealthville Integrations for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Verdix address risk is listed as a paid service. Wealthville Integrations is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add verdix-address-risk and amitesh-m-wealthville-integrations as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Verdix address risk has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Wealthville Integrations has 49/100 (Fair) with 3 views, 0 installs and 0 GitHub stars.